Last updated: 31 October 2026
This Privacy Policy explains how Translate Native processes personal data when you use the app, sign in, make purchases or contact support.
The controller responsible for processing your personal data is Sergey Okhotnikov, a self-employed developer based in Spain.
Address: Av. de Germanies 63, 46183 L’Eliana, Valencia, Spain.
Contact: support@translate-native.com
We process text you submit and the resulting translations. Images, camera input and speech are recognised on your device. For online translation, only the recognised text is sent through our servers to Amazon Bedrock; original images, camera footage and audio recordings are not uploaded through this translation flow.
Requests include the settings needed to produce the translation, such as languages, selected country or cultural context, and communication style. Selecting a country for adaptation is a translation preference and does not itself provide your precise location.
Submitted text may contain personal information about you or other people. Please include only information needed for the translation and submit other people's data only where you are entitled to do so.
You may sign in with Apple, Google or email. We process the account identifiers and authentication information necessary to create, authenticate and manage your account. Depending on your sign-in method and the information made available by that provider, this may include your email address, name and provider-specific identifier. Apple sign-in can use a private relay email address.
Our online infrastructure processes connection information, including IP addresses, to receive requests and return responses. Operational and security records are used to maintain the service, diagnose faults and prevent abuse. Processing connection information does not necessarily mean retaining it permanently.
Subscriptions and one-time token purchases are processed through Apple. We process the purchase and entitlement information necessary to verify transactions, administer subscription access and maintain token balances. We do not receive your full payment card details.
If you contact us, we process your email address, correspondence and information or attachments you choose to send. Attachments sent to support are handled through email, separately from the app's on-device recognition flow.
For online translation, text passes from your device through our AWS-based serverless infrastructure to Amazon Bedrock, which runs Amazon or Anthropic models. The translated result is returned through our servers to your device.
Anthropic develops some of the models available through Bedrock. Using those models through Bedrock does not itself mean that your requests are sent to Anthropic's own API. AWS states that model providers do not have access to customer prompts or completions within Bedrock deployment accounts.
In the configuration used by Translate Native, Amazon Bedrock processes translation requests without storing the submitted text or the resulting translations. We do not enable storage of request or response content in Bedrock. Saved translation history remains local to your device.
We do not use user data, including submitted text and translations, to train or fine-tune AI models. We do not provide user data to third parties for those purposes. Text sent to Amazon Bedrock is processed to generate the requested translation, not to train models.
Where the GDPR applies, our legal bases are:
| Purpose | Legal basis |
|---|---|
| Providing requested translations, authenticating accounts and administering purchased access or tokens | Performance of our contract, where processing is necessary for the service |
| Maintaining security, preventing abuse and resolving technical faults | Our legitimate interests in providing a secure and reliable service, balanced against your rights |
| Responding to support requests | Contract performance or our legitimate interest in responding to enquiries, as applicable |
| Meeting applicable legal obligations | Compliance with a legal obligation |
| Processing that requires consent | Your consent, which may be withdrawn without affecting earlier lawful processing |
Without information necessary to authenticate an account or perform an online translation, the corresponding function cannot be provided.
Text may reveal health information or other specially protected personal data. A general contractual basis alone does not authorise every form of processing of such data. Avoid submitting sensitive personal information unless necessary and unless the relevant processing has an applicable legal basis and, where required, a valid condition for processing specially protected data.
We do not sell your personal data.
We use service providers only as needed for the purposes described in this policy:
We may disclose information to competent authorities where legally required, or where necessary to establish, exercise or defend legal claims.
We do not use third-party advertising or tracking SDKs. Service providers still process information needed to deliver their respective functions. We require appropriate data-protection arrangements for processing carried out on our behalf.
We use separate AWS regional deployments for different geographical areas, including Europe and the United States. The location of particular processing also depends on the relevant service and inference configuration.
A regional deployment does not by itself guarantee that every service processes data exclusively within a particular country or geographical area. Where personal data is transferred outside the EEA, we must use an applicable lawful transfer mechanism, such as an adequacy decision or Standard Contractual Clauses with any necessary supplementary measures. Contact us for information about the safeguards relevant to your data.
Translation history: saved history is stored on your device rather than maintained as a cloud history by us. You can disable history saving and delete existing history in the app. Disabling future saving does not itself delete existing entries. Device backups, if used, are subject to your device and backup-service settings.
Translation text in logs: translation text is deleted from our operational logs. Amazon Bedrock does not store translation request or response content in the configuration used by Translate Native, as described in Section 3.
Account and purchase information: retained for as long as needed to operate the account, administer purchased entitlements and token balances, resolve transaction disputes and meet applicable legal obligations.
Technical and security records: retained only for as long as necessary to investigate faults, address security incidents and prevent abuse.
Support correspondence: retained for as long as needed to resolve the enquiry and address related follow-up or legal claims.
When information is no longer needed for its purpose or an applicable legal obligation, it is deleted or anonymised. Any retention after account deletion must be limited to the relevant legal obligation or claim.
You can request account deletion through our account-deletion page or by contacting support@translate-native.com. We may need to verify your identity before acting on the request.
Use the app's history controls to delete saved translations from your device. Account deletion does not itself establish that local copies or device backups have been erased.
Deleting an account does not cancel an Apple subscription. You must manage or cancel your subscription through your Apple account settings.
Relevant input features may request access to the microphone, speech recognition, camera or selected photos. You can manage these permissions in device settings. Disabling a permission may prevent the corresponding feature from working.
Where processing relies on consent, you can withdraw that consent by contacting us. Withdrawing consent does not affect earlier lawful processing and may make the affected function unavailable.
We use technical and organisational measures appropriate to the information and processing risks. No electronic system can guarantee absolute security.
Subject to applicable law and its conditions, you may request access, correction, erasure, restriction of processing or portability of your data. You may object to processing based on legitimate interests and withdraw consent where applicable.
Contact support@translate-native.com to exercise these rights. Under the GDPR, we normally respond within one month. Where a permitted extension is needed for complex or numerous requests, we will explain it within the initial period.
You may lodge a complaint with a competent supervisory authority, including the Spanish Data Protection Agency (AEPD), or the authority in your place of habitual residence, work or the alleged infringement.
Translate Native is a general-audience translation service and is not directed to young children. We do not offer independent accounts intended for young children. An App Store content rating does not determine eligibility to create an account or provide consent to personal-data processing.
We do not knowingly collect children's personal data without legally required parental authorisation. If you believe a child has provided personal data without the required authorisation, contact support@translate-native.com so we can investigate and take appropriate action, including deletion where required.
We may update this policy as our features, processing or legal obligations change. We will publish the revised version with its updated date and provide additional notice where required. Where a change requires fresh consent, we will obtain it before the relevant processing begins.
Contact: support@translate-native.com
Internal publication note — remove before publication: This text incorporates the product owner's statements, including the confirmed Bedrock configuration and the prohibition on using or sharing user data for model training. Before publication, the developer must confirm the retention criteria against the actual account/log configuration, inference routing and applicable transfer safeguards, and check that the AI-sharing permission screen and in-app account-deletion entry point meet Apple's requirements. The supplied deletion URL and HTTPS availability have not been independently verified.