Privacy Policy

Summary

To perform translations, the app sends submitted content (text, audio, images, or video), recent source messages from the conversation when available, selected languages, and request metadata to our backend and then to OpenAI for processing.

Our backend processes that content only while fulfilling the live request. It does not persist submitted text, context, audio, images, video, translations, or transcriptions in its application database, persistent files, application logs, or backups.

A minimal technical record containing only non-content request, delivery-status, and billing metadata may remain while your account is active as needed to prevent duplicate execution or charging and to investigate an interrupted delivery. It contains no submitted content, content fingerprints, translations, transcriptions, or replay events.

Chat history is stored locally on your device, not as a server-side cloud chat history.

We do not sell personal data and we do not use personal data for third-party advertising or tracking.

Data we collect and process

• Account data (email address when you register, and authentication records). Guest access creates an anonymous account without an email address.
• If you try guest access, a random guest credential stored in device-only Keychain, its server-side hash, app-integrity public keys and counters, and quota/security metadata. Apple App Attest and DeviceCheck help validate the app and limit repeated guest enrollment. These identifiers are used for functionality and security, not advertising tracking.
• If you choose Apple or Google sign-in, the provider's account identifier and verified email (including an Apple private relay address), plus encrypted authorization credentials needed to validate and revoke that sign-in. We do not request access to your contacts, files, or messages.
• User Content you submit for translation (text, audio, images, or video), plus recent source messages from the conversation when available, processed to fulfill your request.
• Preferences, usage, and accounting data (language preferences, request type, token usage, credit balance and ledger activity, processing cost metadata, and timestamps).
• Non-content request, delivery, and billing metadata, such as a request identifier, request type, operation and unconfirmed delivery status, timestamps, and accounting operation keys. These records prevent duplicate execution or charging and support investigation of interrupted requests.
• In-app purchase records needed to grant credits, prevent duplicate grants, resolve purchase issues, and meet accounting obligations. Apple processes your payment method; we do not receive your payment-card or bank-account details.
• Security data used for authentication and rate limiting, such as network address and hashed account or login-client signals.
• Operational telemetry stored in the application database, such as request timing, payload size, and categorical non-content error codes.
• Support communications if you contact us.

How we use data

• Provide translation and app functionality.
• Deliver live translation requests and safely reject duplicate request identifiers.
• Maintain credit balances, process consumable purchases, and provide purchase support.
• Prevent abuse, fraud, and unauthorized access.
• Support troubleshooting, service quality, and reliability.

Device-local chat history

Your saved chats and messages are stored locally on your device. They are not synced to a server-side Dialog Translator chat history.

Deleting your account from the app also clears the app's local chat data on that device.

Sharing with OpenAI and consent

To generate translations, the app shares User Content, recent source messages from the conversation when available, selected languages, and request metadata with OpenAI for processing.

Before the first transfer to OpenAI, the app requests explicit consent. If consent is not granted, content is not sent and translation does not run.

Dialog Translator configures supported OpenAI Responses API calls not to store application state. This is not Zero Data Retention: under OpenAI's default controls, abuse-monitoring logs may contain prompts, responses, and derived metadata for up to 30 days, or longer when required for safety or legal reasons. Retention varies by API endpoint. See OpenAI's API data controls.

Video calls and translated captions

In an invitation-only call, the other participant receives your original audio and video. Our servers exchange connection information between the devices, and the connection may use our relay service to forward media while the call is active. Call video is not sent to OpenAI for captions.

After both participants consent and the room creator accepts the invitation request, speech is sent through our backend to OpenAI for live transcription and translation. Captions are delivered during the call. We do not record or persist call audio, video, transcriptions or captions, and the app does not save a call transcript. Only content-free connection, security and credit/accounting metadata may remain under the retention rules below. OpenAI's endpoint-specific retention described above applies to caption processing. End the call to stop sharing call audio, video and speech for translation.

Apple and Google sign-in

When available, Apple and Google sign-in are optional alternatives to email and password. The chosen provider processes your sign-in under its own privacy policy. We exchange authorization credentials with that provider to verify your identity; your translations and chat history are not sent to it for sign-in.

Google's sign-in SDK may collect a user identifier to record sign-in permissions and an IP address, which Google may use to estimate a general location for fraud prevention. See Google's sign-in data disclosures and Google's Privacy Policy. Dialog Translator does not request device location access for sign-in.

The Google Sign-In SDK included in version 1.1.0 also declares possible collection of name, email address, phone number, coarse location, user and device identifiers, usage data and other data in its privacy manifest. It declares app functionality purposes and, for user/device identifiers, usage and other data, analytics purposes. These SDK declarations do not mean that every category is collected on every sign-in. Our App Store privacy label includes these third-party declarations; the SDK declares no tracking. The app requests only basic sign-in scopes, does not ask for your phone number, and does not request access to your contacts or device location. See the Google Sign-In 9.2.0 privacy manifest.

Provider identifiers and encrypted authorization credentials are retained while the account is active. Account deletion queues revocation with the provider. If the provider is unavailable, only the encrypted credential and the identifier needed to complete revocation remain until it succeeds; they are then removed.

Server content handling

Our backend transiently handles submitted content and generated output only for the duration of the live request. Temporary media working files use volatile storage and are discarded when processing finishes or is interrupted.

It does not persist submitted text, context, media, translations, transcriptions, or replay events, and it is not a cloud chat-sync or server-recovery service. If a connection is interrupted, the final result cannot be recovered from our server and the app may need to start a fresh request.

Only minimal non-content request, delivery-status, and accounting metadata may remain for an active account to prevent duplicate execution or charging and support an interrupted-delivery investigation. A status such as sent-but-unconfirmed does not claim that the iPhone received or saved the result.

Retention

• Account data: retained while your account is active.
• Translation preferences: retained while your account is active.
• Submitted text, context, media, generated translations, transcriptions, and replay payloads on our backend: not persistently retained; transient working data is discarded when the live request finishes or is interrupted.
• Non-content request, delivery-status, and idempotency records: retained while your account is active as needed for transaction, delivery-support, and idempotency integrity. They contain no submitted content, content fingerprint, translation, transcription, or replay payload.
• Authentication rate-limit records: normally retained for up to 7 days and then removed by scheduled cleanup. Guest/signup rate-limit records expire after two days; guest-integrity challenges expire after five minutes and are removed by cleanup.
• Guest credentials and integrity keys: kept while needed for guest access. On deletion, integrity keys and challenges are removed; a minimal credential hash and retired status may remain to prevent repeated free grants. Required credit/accounting records remain under the rules below.
• Other operational telemetry stored in the application database: normally retained for up to 30 days and then removed by scheduled cleanup.
• Credit, cost, accounting, and in-app purchase records: retained as needed for wallet accuracy, purchase support, fraud prevention, financial recordkeeping, and legal obligations.
• Support messages: retained as needed to resolve issues and maintain records.

Account deletion

Delete your registered or guest account in the app: Settings -> Account -> Delete Account. Guest deletion does not require an email address or password.

When deleted, login access is revoked, direct account identifiers are removed from active account records, stored preferences, non-content request and delivery-status records, and non-required application-database telemetry are deleted, and local chat data is cleared on that device. Scheduled cleanup also removes disposable metadata rows written later by requests that were already in flight when deletion began.

Limited credit, cost, accounting, in-app purchase, settlement, security, and support records may remain where needed for financial recordkeeping, purchase support, fraud prevention, dispute handling, or legal compliance. Persistent request and billing identifiers in those records use only non-content request and billing metadata, not fingerprints of submitted text or media.

If you cannot access the app, contact alcovp@gmail.com or use Privacy Choices.

Security

We use reasonable safeguards to protect data in transit and at rest. No transmission or storage method is 100% secure.

Children

Dialog Translator is a general-audience translation utility and is not directed to children below the minimum age permitted to use the service in their country or region.

If you believe a child provided personal data, contact alcovp@gmail.com.

Changes

We may update this policy. We will post the updated version at this URL and update the "Last updated" date.