Data practices
What happens to my message when I send it?
This page explains the current browser beta in plain language. The Privacy Policy provides the formal notice.
Current as of August 22, 2026
Text message lifecycle
- You create the message in the browser.The text remains in the composition experience until you send it.
- Veridge accepts and stores the original.Transport uses TLS. The backend records the accepted original before paid translation work so a process failure does not lose it.
- Direct OpenAI GPT-5.6 Terra receives the required text.The request includes the message text and the source and target language needed for translation, not unrelated conversation history or profile details.
- Veridge stores and delivers the translated variant.The original stays authoritative and remains available to authorized conversation participants.
- The conversation record expires.The original and translated variant are user-visible for up to 30 days unless the message is deleted sooner.
Voice message lifecycle
- You record on your device.The browser creates the recording and uploads it to private Veridge storage through a short-lived, scoped upload operation.
- ElevenLabs Scribe v2 processes the audio in batch mode with verbatim capture disabled.The recording is sent directly from private Veridge storage for the transcription request; no second staging copy is created.
- Direct OpenAI GPT-5.6 Luna cleans the transcript, then GPT-5.6 Terra translates it.The transcript required for that message is translated without sending unrelated conversation history.
- ElevenLabs v3 Conversational may create translated speech.ElevenLabs receives the translated text needed to synthesize the recipient.s audio.
- Veridge stores the conversation artifacts.The original audio, transcript, translation, and translated audio remain separate, encrypted at rest, and available only through authorized message paths.
- The conversation artifacts expire.They remain user-visible for up to 30 days unless the message is deleted sooner.
Conversation data and processing data are different
What you choose to keep
Original messages, original media, transcripts, translations, and translated audio form the conversation history. The current beta gives this content a 30-day user-visible lifetime.
What processing temporarily needs
Provider requests exist to complete a specific task. Veridge does not create a separate transcription staging copy or treat task-scoped provider processing as conversation history.
Data map
| Information | Why it is used | Current retention |
|---|---|---|
| Email address and account ID | Approve accounts, authenticate with a one-time code, identify conversation participants, and provide support. | While the account is active, then while the accepted deletion request is completed, subject to the limited exceptions below. |
| Profile name, languages, app locale, voice preference, and optional photo | Display your profile and select how messages are translated and spoken. | While the account is active or until changed or deleted. |
| Original text, voice, photos, and videos | Deliver the private message and preserve the authoritative original. | 30 days, unless the message is deleted sooner. |
| Transcripts, translations, and synthesized audio | Provide readable and playable translated variants. | 30 days, aligned with the original message. |
| Provider processing request | Complete the selected transcription, cleanup, translation, or speech task. | Veridge does not create a separate staging copy; provider retention depends on verified service terms and account controls. |
| Consent records | Record the version and time of processing permission without storing message content in the consent record. | Up to two years while the account is active; included in account deletion. |
| Technical and security records | Authenticate sessions, prevent duplicate paid work, enforce limits, diagnose failures, and protect the service. | Short-lived sessions; content-free logs are configured for 30 days. Failed queue jobs may remain up to 14 days. |
Current processors
ElevenLabs receives voice content for transcription and translated text for speech synthesis. Direct OpenAI GPT-5.6 models receive transcript or text content for cleanup and translation. Amazon Web Services provides identity, application hosting, private storage, queues, delivery, and content-free monitoring. The primary AWS workload is configured in US East (Ohio), us-east-2, but provider operations may process data elsewhere; Veridge does not make a broader data-residency promise.
What Veridge does not do with private conversations
- Does not sell private message content.
- Does not use private message content for targeted advertising or advertising profiles.
- Does not place message text, transcripts, translations, audio, email addresses, access tokens, or signed media URLs in application logs.
- Does not reuse live private messages as model-training or reusable quality data without separate, explicit consent.
- Does not claim that every provider has a universal no-retention or no-training policy. Provider terms and account-level controls must be verified before Veridge makes that promise.
Safety and device information
In iOS, open the conversation’s Safety menu to report or block a user; touch and hold a received message to report it. On the web, use conversation or message details. Manage blocked users and contact support in Settings. While blocked, neither person can contact the other or view the conversation. Unblocking restores access to unexpired history. Previously downloaded content and media links already issued for up to five minutes cannot be recalled. Reports contain account, conversation and optional message identifiers, a selected reason, timestamps and review status, not copies of message text or recordings. Reports and safety request records expire after 30 days; account deletion also removes linked reports and blocks. Blocks remain until removed or account deletion. The operator reviews reports and may restrict an abusive account. Contact support@veridge.io for support, safety follow-up or an appeal, without sending private content or sign-in codes. This is not an emergency service; contact local emergency services for immediate danger. Native authentication uses an installation identifier, device-bound sessions and app version. Optional notifications use an APNs device token and language preference; Apple delivers a generic notification. These identifiers support authentication, delivery and security, not advertising or tracking. Veridge has no advertising or tracking SDKs. The iOS app has an invite-only TestFlight release path; this is not a public App Store release.