Keep the data story specific.

Account information

When you sign in with your email, the service stores the account identifier, email address, display name, and authentication metadata needed to create a session. Passwords are stored as one-way scrypt hashes and are never stored in plain text.

Uploaded recordings

Files are written to the configured server storage while a transcription job is queued or processed. The queue can delete the source file after completion or failure when DELETE_UPLOADS_AFTER_TRANSCRIPTION=true. Do not claim automatic deletion if your deployment changes that setting.

Transcription results

The transcript text is stored in the database alongside the job so you can return to it from your workspace. It is deleted with the job when the server retention window expires: GUEST_JOB_RETENTION_DAYS for a recording uploaded without an account and ACCOUNT_JOB_RETENTION_DAYS for one uploaded while signed in, where 0 means the record is kept until it is removed by hand. State the values your own deployment runs.

Transcription providers

The server sends audio to the provider configured by the site administrator. Provider retention, regional processing, and privacy terms also apply. Never place a provider API key in browser code.

Cookies and analytics

Authentication sessions use necessary cookies. Add analytics only when the production privacy notice and consent behavior have been reviewed for the countries you serve.

Contact

For privacy questions, contact the address listed on the Contact page.