Privacy Policy

1. Data Controller

Ladaworks LLC

16192 Coastal Hwy, Lewes, DE 19958, United States

Registered Agent: Harvard Business Services, Inc.

Email: info@montrelia.com

2. Information We Collect

2.1 Account and Authentication Information

When you create or use an account, we collect:

• Email address.
• Name or profile information, if you provide it.
• Account identifiers and authentication provider information.
• Authentication session data needed to keep you signed in.

If you sign in with Google or Apple, we receive the account information made available by that provider, such as your email address, name when provided, and a unique provider identifier. We do not receive or store your Google or Apple password.

2.2 Translation and Assistant Content

When you request a translation or use the Assistant, we process the content you choose to submit, including:

• Typed text.
• Images or camera captures selected for image translation.
• Voice recordings submitted for voice translation.
• PDF files and file names submitted for document translation.
• Messages you write in the Assistant. Each request carries at most the last 10 messages of that chat (yours and its replies), with your language settings and the app language.
• Source language, target language, selected AI model or feature, request status, and related usage metadata.
• For typed text, your "About you" tone, priority and usage answers, sent as short fixed instructions with the text (see 2.3a).
• The translated output, or the Assistant's reply, returned by the AI model.
• When you use the "listen" action, the translated text you chose to play aloud, which we send to a speech-synthesis provider to generate audio. We use its language only to choose a matching voice.

Translation content is processed through our backend and AI service providers only as needed to generate the translation or the Assistant's reply and operate the Service. We do not store raw typed text, translated output, uploaded images, audio recordings, PDF files, or Assistant messages and replies on our servers, except the cached speech audio described below. Our backend translation logs are metadata-only. In this Privacy Policy, "translation content" includes Assistant messages and replies.

Every AI request goes from our backend through OpenRouter to the provider of the model. These are the models we currently use for each feature:

• Typed text: the model you choose in the app: DeepSeek (by DeepSeek, the default), ChatGPT (by OpenAI), Claude (by Anthropic) or Gemini (by Google). It receives the text, your language settings, and your "About you" tone, priority and usage answers (see 2.3a).
• Photos and camera captures: ChatGPT (by OpenAI). It receives the image and your language settings.
• PDF documents: ChatGPT (by OpenAI). It receives the PDF, its file name and your language settings.
• Assistant: ChatGPT (GPT-6 Luna, by OpenAI), the same model for everyone; there is no model choice. It receives the last messages of the chat (at most 10, your new message included), your language settings and the app language.
• Voice recordings, including Conversation: Gemini (by Google). It receives the recording and your language settings.
• Reading a translation aloud ("listen" and Conversation): a speech model: Kokoro, an open-source model run by a host that OpenRouter selects, for English, Spanish, French, Hindi, Italian, Japanese, Portuguese and Chinese, and Grok voice (by xAI) for other languages. It receives only the text to be read aloud.

None of these models receives your name or email address.

Before anything you submit, including Assistant messages, is sent to an AI model for the first time, the app asks for your agreement on its own screen, and it asks again when what we send changes. You can withdraw it at any time in the app's Settings (Privacy → AI translation). While it is off, nothing you submit is sent to an AI model, and the app asks again before it translates or sends an Assistant message.

Synthesized speech is different: to avoid paying for and generating the same audio twice, the audio file produced for a given translated text, language and voice is kept in our backend storage under a key derived from a one-way hash of that text and its settings, and the same file is served to any user who asks to hear exactly the same text. The file contains only the spoken translation; it is not linked to your account, and it cannot be used to recover who requested it.

We do not use your raw translation content for advertising. We do not operate our own model-training pipeline using your raw translation content. Our OpenRouter account is configured to exclude provider endpoints that train on request data or that publish prompts and completions to public datasets, so your submitted content is not used to train AI models. Providers may still process and briefly retain content as needed to return a result and to prevent abuse, under their own terms and privacy policies.

2.3 On-Device Data

The app stores some data locally on your device to make the Service work, including:

• Authentication session data, stored through the device secure storage where supported.
• App preferences such as theme, app language, target language, selected model, and onboarding state.
• Your translation history, saved translations and folders, and Assistant chats, scoped per signed-in user on the same device.

History, saved translations and Assistant chats are stored only on your device, never on our servers, and we do not sync or back them up. Your device's own backup (for example iCloud Backup or a backup to your computer) may include them, as it does other app data. History keeps every successful translation until you delete it (one entry or all): the languages, the mode or model used, the source text where the app has it (typed text or a speech transcript; for a PDF, its file name), and the translated output. A saved translation keeps a copy of the item and the folder you put it in. Assistant chats keep your messages and the replies. Photos, voice recordings and PDF files themselves are not stored. Deleting the app removes this data from your device.

2.3a Preferences You Tell Us ("About You")

After the introduction, the app asks four optional questions: where you mainly use translation (for example travel, work, school, daily life, or living abroad), the tone you prefer (formal, casual, or it depends), what matters most to you in a translation (exact meaning, sounding natural, or short and simple), and which language you speak and translate into. Every question can be skipped, and you can change your answers at any time in Settings → About you.

We use your language answers to set up the app's language pair. When you translate typed text, we also send your tone, priority and usage answers with it, as short fixed instructions, so the translation fits how you want to sound — for example formal or informal address. We may turn this on for some users before others. Your name and email are never sent. Your answers stay on your device until you sign in and are then stored with your account; you can change them in Settings → About you. We also record which options were chosen, without your name or email, in our product analytics so we can understand how the app is used.

2.4 Subscription and Transaction Information

If you purchase, restore, or manage a subscription, we and our subscription providers process:

• App user ID.
• Product, plan, entitlement, and subscription identifiers.
• Transaction and receipt identifiers.
• Subscription state, renewal state, cancellation, expiration, refund, or billing status.
• App Store or Google Play storefront information made available through the purchase flow.

We do not collect or store your credit card number, bank account details, or full payment method information. Payment processing is handled by Apple App Store, Google Play Store, and RevenueCat.

2.5 Technical, Usage, and Diagnostic Information

We may automatically collect technical and usage information, including:

• Device model, operating system, app version, build number, and update channel.
• IP address and request timing information used for security, rate limiting, and service operations.
• Screen views, feature usage events, subscription flow events, and translation success or failure metadata.
• Crash reports, error diagnostics, performance traces, and limited device or app context.
• Pseudonymous user or app instance identifiers used for analytics, diagnostics, authentication, and subscription synchronization.
• A device advertising identifier (such as Apple's IDFA), collected only if you grant permission through the App Tracking Transparency prompt, and used for advertising measurement and attribution as described in Section 2.8.

Crash reporting (Sentry) is set up to send as little as possible. A crash report carries the error, where in the app's code it happened, and device and app details, with a pseudonymous user ID only, never your email or name. The app sends no screenshots and no capture of the screen layout, and it removes the content of network requests. In the extra details and the trail of recent app steps attached to a report, it replaces any field whose name includes the word email, text, input, output, token, body, stack or message with "[redacted]" (numbers and yes/no values are kept), removes anything that looks like an email address, and cuts web addresses before the "?" or "#", the part that can carry one-time links. Tracing headers are added only to requests to our own backend. Sentry is configured not to store IP addresses.

Product analytics (PostHog) records what you do in the app, such as screens opened, features used and whether a translation succeeded, not what you type, translate, search for or ask the Assistant. Session recording is off. The app does not send your typed text, translations, Assistant messages, photos, recordings or documents to PostHog. As a safeguard, it replaces values under field names that point to content or credentials (such as text, translation, transcript, content, message, email, token, password, file or URL) with "[redacted]", as well as anything that looks like an email address, a sign-in token or a web address with a query; it keeps error details only as short error codes; and it sends the link that opened the app without its query part. Events also carry device and app information, such as device model, operating system, app version, and language and time zone settings. PostHog works out an approximate location from your IP address; we keep only the country and continent, and the IP address, city, postal code, coordinates, region and location-based time zone are removed before the event is stored. This applies to events recorded from 7 October 2026; events recorded before then may still include the IP address and the approximate location PostHog derived from it, and are kept and deleted as described in Section 5. With your pseudonymous account ID, PostHog also keeps your plan and subscription status, app language, the options you chose in "About you" (as option and language codes, never free text), your AppsFlyer ID, your App Tracking Transparency choice, the version of the AI consent you agreed to (or that you withdrew it), and the ad source and campaign that first brought you to the app. Our subscription provider (RevenueCat) also sends your subscription events to PostHog, together with the device identifiers it holds for your account: the vendor identifier (IDFV), the anonymous identifier the Meta SDK creates for this app, and, only if you allowed tracking, the IDFA.

2.6 Permissions and Device Features

The app may request access to device features only when needed for a feature you choose to use:

• Camera access to capture images for translation.
• Photo library access to select images for translation.
• Microphone access to record audio for voice translation.
• Speech/audio features to play translated text aloud.
• Document picker access to select PDF files for document translation.
• Notifications, asked only after you have used the app and agreed on our own explanation screen; iOS then shows its own permission dialog (Section 2.6a).

You can control these permissions through your device settings. Some features may not work if the relevant permission is denied.

2.6a Push Notifications

If you allow notifications, we store a push token for your device (issued by Apple and Expo), your app language, your time zone, the app version, and when you last opened the app. We use them to send a small number of notifications: when your free weekly translations refill, if a Premium payment needs your attention, and an occasional reminder if you have not used the app for a week or two. We record which notification was sent and whether it was delivered, so we never send the same one twice. Notifications are delivered through Expo's push service and Apple Push Notification service.

You can turn notifications off at any time in your device settings. The token is removed when you sign out, delete your account, or when Apple reports that the app was removed from the device.

2.7 Communications and Requests

If you contact us or submit an in-app request, we may collect the information you provide, such as your email address, message content, requested AI model name, and support-related details.

2.8 Advertising and Attribution Information

We may promote the app through advertising campaigns on third-party platforms such as Meta (Facebook and Instagram). To measure whether those campaigns work, we use the following:

• Apple SKAdNetwork / AdAttributionKit: Apple's privacy-preserving framework reports aggregated, delayed install and conversion information to advertising networks without identifying you individually. This operates at the operating-system level and does not require your tracking permission.
• Advertising SDK and identifiers (IDFA): We integrate the Meta SDK to measure app installs, signups, and subscription events generated by our ads. If, and only if, you allow tracking through Apple's App Tracking Transparency (ATT) prompt, we and Meta may use your device advertising identifier (IDFA) to attribute these actions to a specific campaign. If you decline the ATT prompt, we do not access the IDFA. The Meta SDK still sends app events (such as installs, app opens, sign-ups and the plan you subscribed to) with device and app information and an anonymous identifier the SDK creates for this app, and our subscription provider (RevenueCat) sends your subscription events to Meta's Conversions API with that anonymous identifier, the vendor identifier (IDFV) and your device's IP address.
• AppsFlyer (mobile measurement): We use AppsFlyer, a mobile measurement partner, to work out which ad campaign or link led to an install and to open the right screen when you arrive through one of our links. The AppsFlyer SDK waits for your answer to the ATT prompt; if you have not answered, it starts when the app goes to the background or after at most 10 minutes. It receives device and app information such as the vendor identifier (IDFV), device model, operating system and app version, IP address, install and launch times, and, only if you allowed tracking, the IDFA. Our subscription provider (RevenueCat) also sends subscription events, such as a trial start or renewal, to AppsFlyer linked to that AppsFlyer identifier, so that subscriptions can be attributed to a campaign. AppsFlyer may share attribution results with the advertising networks we work with (such as Meta). We do not send your translation content, your email address or your "About you" answers to AppsFlyer. If your device's region is in the European Economic Area, your answer to the App Tracking Transparency prompt is also passed to AppsFlyer as your consent choice for ad measurement; the screen before that prompt says so.

We use this information to measure ad performance, attribute installs and conversions, route links to the right screen, and optimize advertising spend. We do not use your translation content for advertising. You can change or withdraw tracking permission at any time in your device settings (Settings → Privacy & Security → Tracking).

3. How We Use Information

We use information for the following purposes:

4. How We Share Information

We share information only as needed to provide, secure, and operate the Service:

We share information only with providers whose own terms and data processing commitments require them to protect it to a standard at least equivalent to the one described in this Privacy Policy, and to use it only to deliver the service described in the table above rather than for their own purposes. For the AI and speech providers in particular, our OpenRouter account is configured to exclude any endpoint that trains on request data or that publishes prompts and completions to public datasets.

We may also share aggregated or de-identified information that does not reasonably identify you.

We do not sell your personal information for money, and we are not a data broker. We do not use your translation content for advertising. We do share limited advertising and attribution information with Meta to measure and optimize our own ad campaigns, as described in Section 2.8. Depending on your jurisdiction, this measurement activity may be considered "sharing" for cross-context behavioral advertising or "targeted advertising." You can opt out of identifier-based tracking by declining the App Tracking Transparency prompt or disabling tracking in your device settings; when you do, we do not access your IDFA, and the events described in Section 2.8 are sent to Meta without it.

5. Retention

We keep information only for as long as reasonably necessary for the purposes described in this Privacy Policy, unless a longer period is required or allowed by law.

• Account information is kept while your account is active, unless you delete the account or request deletion.
• "About you" answers are kept with your account until you change them or delete the account.
• Backend translation logs, including those for Assistant requests, are metadata-only and are scheduled for deletion after 45 days.
• Backend usage receipts are scheduled for deletion after 45 days.
• Backend rate-limit events are scheduled for deletion after 1 day.
• Push tokens are kept while notifications are allowed and you stay signed in on that device (Section 2.6a); records of sent notifications are scheduled for deletion after 90 days.
• History, saved translations and Assistant chats stay on your device until you delete them in the app, you delete your account in the app, app data is cleared, or the app is uninstalled. Your device's own backup may keep a copy under your backup settings.
• Raw images, audio recordings, and PDF uploads are not intentionally stored in our cloud history database after the translation request completes. Assistant messages and replies are not stored on our servers.
• Cached synthesized-speech audio (Section 2.2) is kept in our backend storage so repeated requests for the same text do not have to be generated again. It is not tied to any account and is deleted 30 days after it was created.
• Subscription and transaction records may be retained as needed for subscription administration, fraud prevention, tax, accounting, legal, and dispute-resolution purposes.
• Analytics and crash diagnostics are retained according to our operational needs and vendor retention settings.

Third-party providers may keep information according to their own policies.

6. Account Deletion

You may initiate account deletion from the app's Settings screen or by contacting info@montrelia.com.

When account deletion is completed, we delete the Supabase account and associated server-side records that are not legally required to be retained, and the subscriber record our subscription provider (RevenueCat) holds for your account. We also ask PostHog to delete the analytics profile and events linked to your account ID, and AppsFlyer to erase the attribution data linked to it; each provider completes the request on its own schedule. If you signed in with Apple, the app asks Apple once more for your confirmation and we then revoke the app's Sign in with Apple access to your Apple ID; if you close that Apple prompt, your account is still deleted. Crash reports in Sentry are not deleted one by one; they expire under the retention described in Section 5. Some records may be retained if necessary for legal, tax, accounting, security, fraud prevention, or dispute-resolution purposes.

Deleting your account does not automatically cancel an active App Store or Google Play subscription. You must cancel subscriptions through your device's App Store or Google Play account settings, or through any subscription management surface made available in the app.

When you delete your account in the app, the app also removes that account's history, saved translations and Assistant chats from that device. Account deletion does not remove local app preferences, data on other devices where you used the account, or copies in your device's own backups. You can remove local device data by clearing app data where supported by your platform or uninstalling the app.

7. Security

We use technical and organizational measures designed to protect information, including:

• TLS encryption in transit.
• Authentication through Supabase Auth.
• Device secure storage for authentication sessions where supported.
• Database row-level security and access controls.
• Service-role separation for backend-only subscription and usage operations.
• Telemetry scrubbing and minimization for analytics and crash reporting.

No method of transmission or storage is completely secure. We cannot guarantee absolute security.

8. Your Rights and Choices

Depending on your location, you may have rights to:

• Access the personal information we hold about you.
• Correct inaccurate or incomplete information.
• Delete your personal information.
• Receive a portable copy of your information.
• Object to or restrict certain processing.
• Withdraw consent where processing is based on consent.
• Appeal or complain to a privacy authority, where applicable.

To exercise rights, contact info@montrelia.com. We may need to verify your identity before responding.

You can also control some information directly:

• Use device settings to manage camera, microphone, photo, and document access.
• Allow or decline identifier-based tracking through the App Tracking Transparency prompt, and change it later in your device settings (Settings → Privacy & Security → Tracking).
• Use app settings to change preferences.
• Delete history entries (one or all), saved translations and Assistant chats in the app.
• Withdraw your agreement to sending content to AI models in the app's Settings (Privacy → AI translation).
• Use App Store or Google Play settings to manage subscriptions.
• Delete your account from the app's Settings screen.

9. U.S. State Privacy Notice

This section supplements the policy for residents of California and other U.S. states with consumer privacy laws.

We may collect the following categories of personal information:

We do not sell personal information for money. We share limited advertising and attribution information with Meta to measure and optimize our own advertising campaigns; depending on your state, this may be treated as "sharing" for cross-context behavioral advertising or "targeted advertising." You may opt out by declining the App Tracking Transparency prompt or turning off tracking in your device settings.

We do not ask you to submit sensitive personal information. However, translation content and Assistant messages may contain sensitive information if you choose to include it, for example when you ask for phrases for a doctor's visit. You are responsible for deciding what content to submit for translation or send to the Assistant.

10. International Users

We are based in the United States, and our service providers may process information in the United States and other countries. These countries may have data protection laws different from those in your country.

For users in the European Economic Area, United Kingdom, or Switzerland, our legal bases may include:

• Performance of a contract, to provide the Service you request.
• Legitimate interests, such as security, fraud prevention, diagnostics, and service improvement.
• Consent, where required for optional permissions or certain processing.
• Legal obligations, where we must retain or disclose information under applicable law.

Where required, we rely on appropriate transfer mechanisms such as Standard Contractual Clauses or other approved safeguards.

11. Children's Privacy

The Service is not directed to children under 13. We do not knowingly collect personal information from children under 13.

If you are between 13 and 18, you may use the Service only with consent from a parent or legal guardian.

If you believe a child under 13 has provided personal information to us, contact info@montrelia.com and we will take appropriate steps to delete it.

12. Third-Party Links and Services

The Service may link to third-party websites or services. Third-party services are governed by their own terms and privacy policies. We are not responsible for their privacy practices.

13. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. When we make changes, we will update the "Last Updated" date above and, where appropriate, provide notice in the app or through another reasonable method.

Your continued use of the Service after an updated Privacy Policy becomes effective means you acknowledge the updated policy.

14. Contact Us

If you have questions or requests about this Privacy Policy, contact us:

Ladaworks LLC

16192 Coastal Hwy, Lewes, DE 19958, United States

Email: info@montrelia.com

Website: https://www.montrelia.com