oye translate Privacy

Last updated: October 22, 2026

Identity and service records

Current iOS releases use verified App Store purchase/recovery information and pseudonymous account and installation identifiers. They do not ask for a name, email address, phone number, or a separate app sign-in. We keep plan, legal acceptance, app version, session, billing and aggregate usage records needed to operate Oye. Historical information supplied to earlier releases may remain in our records; you can request access or deletion.

Onboarding

We keep the languages you select and, if you choose to provide them, translation situations, age group, gender choice and how you found Oye. Optional background questions can be skipped. We use these answers to understand and improve the service.

Live audio and saved conversations

On current iOS versions, before translation starts, we explain the processing and ask for your permission. If you allow it, microphone audio is sent to Soniox Inc., our third-party AI speech provider, to create transcripts and translations. If spoken playback is enabled, translated text is also sent to Soniox to generate speech. This permission is separate from microphone access and advertising tracking permission. Declining prevents audio/text processing; you can reconsider later.

Audio and conversation text are processed by Soniox in the United States. Live audio streams and their transcripts are processed transiently without requested content storage. If a live connection fails, a short recording may be sent through the Oye Convo mobile service to Soniox's asynchronous API; temporary recordings and transcripts are deleted after processing. Soniox does not use this content to train or improve AI models. Content-free technical and usage metadata may be retained for billing, security, and reliability. Oye Convo does not ask for your location to choose a region. Android's on-device voice may be used as a connection fallback.

Soniox provides protection equivalent to the safeguards described here for this processing: encrypted transport, restricted account access, regional content processing, no model training with conversation content, and content deletion. See Soniox's privacy policy and security and privacy documentation. Saved conversations and on-device summaries remain on your device and are not shared with advertising providers.

Storage and diagnostics

Minimal pseudonymous account, purchase and usage records are stored in Google Cloud. Local account credentials use the iOS Keychain or Android Keystore. Technical diagnostic reports can include app/OS versions, device model, bounded app-state information and installation/session references. They exclude conversation content, names, emails, passwords and access tokens, and are scheduled for deletion after 30 days.

Operational analytics

Google Analytics for Firebase helps us measure app activity, verified purchases and reliability. It uses an app-instance identifier and can derive approximate geography from masked IP addresses; we do not request GPS location. Operational reporting is separate from permission to track across other companies' apps and websites.

Optional iOS advertising measurement

On iOS version 1.5.1 (build 171) and later, with your separate in-app advertising-measurement consent and Apple tracking permission, AppsFlyer and Google measure which advertisements lead to installs and outcomes. AppsFlyer may forward eligible events to Meta, Google and ChatGPT Ads, including events not attributed to their advertisements. Measurement may include IP address, pseudonymous device and advertising identifiers, app and device information, app opens, completed-translation milestones, trials, product and transaction identifiers, purchase amounts and currency. Names, emails, conversation audio, transcripts and translations are not supplied for advertising. We do not enable direct Meta SDK reporting or advanced matching with contact details.

Your advertising choices

These additional in-app controls apply to iOS version 1.5.1 (build 171) and later. Older iOS releases use Apple tracking permission and do not have the new sharing control; updating gives you the additional choice. Older releases cannot send the consent marker required for our expanded Meta conversion sharing. Meta Advanced Data Sharing remains disabled.

Advertising sharing is off until you allow it in the app and Apple tracking permission is authorized. These permissions are separate. We do not treat an earlier Apple tracking permission as acceptance of the expanded sharing disclosure. Declining either permission does not restrict translation, purchases, trials or saved transcripts. Events occurring before both permissions are granted are not queued by the app for later advertising reporting.

You can withdraw sharing permission in the app menu under Advertising measurement. This stops future reporting and clears advertising events still queued by the app; it does not delete information already delivered to providers. You can also change tracking permission in iPhone Settings > Privacy & Security > Tracking. Apple tracking denial is respected and is not replaced with another identifier. Personalized-ad consent remains disabled in our Google and AppsFlyer integrations.

Sharing and your other choices

Tap Stop to stop microphone capture and translation. On current iOS versions, you can withdraw Soniox processing permission in the app menu under Audio processing permission; withdrawal stops processing and requires a new affirmative choice before another translation. Only use translation when everyone whose voice is captured agrees. Withdrawal prevents future processing and does not undo completed translation requests.

We do not sell conversation or account data or share it with data brokers. Service providers include Soniox for live speech processing, Google Cloud for storage and operational services, Apple or Google Play for purchases, and the measurement providers described above when permitted. You may request access, correction, export or deletion of service records. Contact support with an app/account reference if available; withdrawing tracking does not delete events already delivered to a provider.

Contact

Privacy requests can be sent to support@oye.live.