How VoxText handles your data

Audio processing

When you start a transcription, your browser uploads the recording to private Vercel Blob storage. Our server checks the file and sends audio to RelayRouter for transcription. Long recordings may be converted or divided into smaller audio sections before processing. Temporary files use generated identifiers rather than your original filename.

Temporary transcripts

VoxText may temporarily store transcript sections and the completed transcript while a task is being processed and delivered. A completed transcript is available for retrieval for up to one hour. After your browser confirms receipt, VoxText requests deletion of the temporary result. If delivery is interrupted, the result can be retrieved again within that window.

Signed-in users have Cloud transcript text automatically saved to their account when transcription completes. Edits to saved transcripts are automatically uploaded. Saved text remains available in My transcripts until you delete the record or your account. Deleting a record clears its text and filename; a minimal deletion marker prevents background retries from restoring it. Database backups may retain earlier copies until those backups expire. Original audio is not kept in your history.

Local transcript text stays on your device unless you choose Save to account. After saving, edits are uploaded automatically. Guest results are not saved to an account. Copy or download any unsaved work before clearing or leaving the page.

File deletion

VoxText requests deletion of temporary audio and processing files when a task finishes or fails. Expired results are no longer available through the result endpoint and are queued for deletion. Scheduled cleanup checks run hourly to retry failed deletions and remove abandoned files. Our operational target is to clear abandoned files within 24 hours, although service outages can delay deletion.

These rules describe the temporary files managed by VoxText. They do not establish a zero-retention guarantee for transcription providers, infrastructure logs or provider backups.

Browser cookie and usage limits

VoxText uses an essential cookie named voxtext_anon to recognize a browser for free usage limits and access to its current transcription task. The cookie contains a random signed identifier and expires after 30 days. We do not use device fingerprinting.

Network addresses are used to apply additional abuse limits. In VoxText's application storage, these addresses are represented by a keyed hash rather than stored as raw IP addresses. This is a pseudonymous identifier, not a guarantee of anonymity. Daily quota records are removed after a short reconciliation period of up to 48 hours following the end of the relevant UTC day.

Usage and reliability records

We record limited events such as upload attempts, completed uploads, transcription outcomes, file format, size and duration ranges, processing time and error codes. These records help us enforce allowances and understand failures. Audio, transcript text, original filenames, raw IP addresses and private file URLs are not included in analytics events.

Detailed application event records are retained for up to 30 days. A separate minimal measurement source with keyed pseudonyms for browser, task and receipt correlations is retained for up to 90 days, as are daily aggregate summaries. Pseudonyms permit cross-day measurement and are not anonymous data. Retention follows the original UTC event day; replay does not extend it. Temporary task metadata is retained for 48 hours after a task ends. Hosting providers may maintain separate infrastructure and security logs under their own policies.

The same random browser identifier may be used to count product events such as public page visits, upload starts, transcription outcomes, sign-up and checkout creation. These events may include a supported page category, audio format, a broad duration range, a referring hostname and limited UTM campaign labels. VoxText does not send audio, transcript text, original filenames, full referrer URLs, secrets or card details, payment credentials or raw invoices in these events. Limited verified received amounts, currency and keyed receipt/account correlations may be retained to measure payments; this does not expose the underlying account or payment record. If an optional analytics provider is configured, it receives only the supported event fields and a query-free public page URL.

Service providers

Vercel provides hosting, private file storage and background task execution. Upstash provides storage for usage limits, task metadata and operational statistics. RelayRouter receives audio and routes transcription requests to the selected model provider. These providers process data under their own terms and policies. VoxText's deletion schedule does not override their retention practices.

Your Data Rights

You may request access to and view your personal data, correction of inaccurate personal data, deletion of personal data, a copy of your data, or closure of your account. Contact support@voxtext.io to submit a request. We aim to handle requests within 30 days. We may retain data as permitted or required by law for legal, security, fraud-prevention, or accounting purposes.

Your controls

You can stop before uploading, remove a selected file, and clear a transcript from the page. Clearing a completed transcript does not restore the free allowance already used. Only upload recordings you are authorized to process. For questions about this processing, use our Contact page.