Snap Translator Privacy Policy

App: Snap Translator (shown on your Home Screen as "Snap Camera Translator"), including its Apple Watch app, widgets and Control Center controls, share extension, Safari "translate page" action, iMessage app ("Snap Cards") and the AI Keyboard
Effective date: 10 October 2026
Last updated: 10 October 2026

This policy explains how we handle personal data. It is a plain-language description of how the app works, not legal advice.

The short version

• No account. Snap never asks for your name, email or password to translate.
• Some processing happens on your iPhone, and some on servers.
• Text recognition for Latin, Chinese, Japanese and Korean text normally runs on your device. If the on-device result is empty or clearly wrong, or the source language is set to Detect and the script cannot be identified on the device, the photo is sent to Google Cloud Vision. Photos in other writing systems (for example Cyrillic, Arabic, Hebrew or Indian scripts) are always sent to Google Cloud Vision to be read.
• Text translation runs on your device only when you have downloaded an Apple offline language pack for that language pair and either you are offline or no line of the text is longer than about 500 characters. Otherwise, and always when the source language is set to Detect or you use the Apple Watch, the text is sent to Google Cloud Translation.
• Voice recordings in Dialogs and on Apple Watch, and requests to the optional AI features, are sent through our server to AI providers.
• Do not translate sensitive documents through server-based features unless you are comfortable with that content being processed by the providers listed in this policy.
• Snap shows no ads. If you allow tracking when iOS asks, we use Meta and Branch to measure which ads bring people to Snap. If you do not allow it, they do not collect attribution data.
• Usage analytics and crash reports are your choice. In the EEA, analytics and crash reports start only after you allow them in the app. Everywhere, you can switch them off in Settings. When they are off, the app sends only a small set of anonymous events (section 3.10).
• Subscriptions are handled by Apple, with RevenueCat checking your subscription status. We never see your card details.
• Your history stays on your devices (iPhone, and recent items on your paired Apple Watch), in your device backups, and, if sync is on, in your own private iCloud storage.

1. Who we are

Snap Translator is published by:

HOPIN.IT SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ (HopIn.IT sp. z o.o.)
ul. Marsz. Józefa Piłsudskiego 74/320, 50-529 Wrocław, Poland
KRS 0001117479, NIP 8971940626, REGON 529197668

("HopIn.IT", "we", "us"). We are the controller of the personal data described in this policy. You can reach us about privacy at [email protected]. Based on our current assessment, the law does not require us to appoint a Data Protection Officer. We will reassess this if our processing changes.

UK representative. We have not appointed a representative in the UK under Article 27 UK GDPR. If you are in the UK, contact us directly at [email protected].

2. What stays on your device

These features run on your iPhone or Apple Watch and do not send your content to us:

• Reading text in Latin, Chinese, Japanese and Korean scripts from the camera, photos, scans and live camera mode, using Google ML Kit text recognition (which runs on the device) and Apple's Vision framework, except in the cases described in section 3.1. Your images and the recognized text stay on the device. The ML Kit software does, however, send Google diagnostics and usage data: device model and OS version, the app's bundle ID and version, a per-installation identifier, performance metrics and the kind of recognition events that occurred. Google handles that data under its own terms (section 5).
• Offline translation using Apple's Translation framework and language packs you download. It is used when a pack for the language pair is installed and either you are offline or no single line of the text is longer than about 500 characters. Text whose source language is set to Detect is always translated by Google Cloud.
• Reading text aloud (Apple's on-device speech voices).
• Detecting which language a text is in (Apple's Natural Language framework), and, when you choose Detect for text sent to Google Cloud Translation, by Google.
• Your translation history, dialog messages, saved photos and scans, settings and language choices. These are stored in the app's databases on your device, and in a storage area shared with the app's keyboard, share extension and Safari action on the same device. If you back up your iPhone, your history and voice recordings are included in that backup unless iCloud sync is on.
• "My details" (for example your name, passport number, date of birth and address that you choose to save for filling in forms). These are stored only in your device's Keychain, can be protected with Face ID, are never synced to iCloud Keychain and cannot be restored onto a different device, are never shared with the keyboard, and are never sent to any server or AI provider. The app fills them into forms on your device after any AI step has finished.
• Photos of forms in "Form snapshot" are read on your device; the photos themselves are not uploaded (see section 3.6 for what is sent).
• The Snap Cards iMessage app and the widgets do not send your content anywhere.
• Motion data is used only on your device to keep translated text aligned in live camera mode.

3. What we collect and why

You do not have to give us any personal data to use the on-device features. Server-based features (cloud translation, text recognition by Google Cloud Vision, voice and AI) cannot work without sending the content you choose to translate. Usage analytics and crash reports are not required for the app to work, and in the EEA they run only if you allow them.

3.1 Camera and photo translation

What happens: you take a photo, pick one from your library, share one to Snap, or scan a document. Snap reads the text and translates it.

• Text recognition. If the source language you selected uses a script the device cannot read (for example Cyrillic, Greek, Arabic, Hebrew, Indian scripts, Thai, Georgian, Armenian or Ethiopic), or the source is set to Detect and the device cannot identify the script, or the on-device result is empty or clearly wrong, Snap sends a compressed copy of the photo and, if chosen, the source language to Google Cloud Vision (through a Google Cloud Function we operate in the United States, which calls Google's service; Google may process the image in any Google location) to read it. For scanned documents in the Tools section, a page image is only sent this way after you agree in the app; once you agree, later scans are not asked again, and you can turn this off at any time in Settings. For ordinary camera and photo translation, this happens automatically when needed, without a separate prompt.
• Translation. The recognized text, the target language and (if chosen) the source language are sent to Google Cloud Translation (through a Google Cloud service we operate in the United States, which calls Google Cloud Translation; Google may process the text in any Google location), unless offline translation is used as described in section 2. When you are back online, the app may re-translate up to 20 recently stored offline translations per app launch through Google Cloud to improve their quality.

Legal basis: performance of our contract with you (providing the translation you ask for), Art. 6(1)(b) GDPR.

3.2 Typed text translation

Text you type or paste is translated on your device or sent to Google Cloud Translation as described above.

If you have a subscription and choose the AI translation engine, the text you typed and the language pair are also sent through our server to an AI model provider (see section 5) to produce a more natural translation. This only happens when you select the AI engine.

The text translator screen does not record audio.

Legal basis: contract, Art. 6(1)(b) GDPR.

3.3 Voice: Dialogs and Apple Watch

When you record speech in Dialogs on iPhone, or dictate on the Apple Watch app, the audio recording and the language code are sent through our server (hosted on Cloudflare) via OpenRouter to a speech-to-text model (Whisper large-v3, an open-weight model run by an independent hosting provider named in section 5). The resulting text is then translated as described in section 3.1. The microphone is only used while you are recording.

Your dialog messages (the transcribed text and translations) are saved in your history. The most recent recording for each language stays in the app's storage on your iPhone (and in device backups) until it is replaced by your next recording in that language or you delete the app. On Apple Watch, recordings are temporary files that watchOS clears.

Legal basis: contract, Art. 6(1)(b) GDPR.

3.4 Safari "translate page" action

When you open the Snap action from Safari's share sheet, the action reads the page on your device (its visible text, including short labels such as image descriptions, field placeholders and tooltips, and its title). Only after you tap Translate does it send that page text and the page title in batches, with your chosen target language, directly to Google Cloud Translation. The translation is then written back into the page you are viewing.

• It runs only on the page where you open it, and sends text only after you tap Translate.
• It skips scripts, code blocks, text areas, editable areas, hidden elements and anything the page marks as "do not translate".
• It does not send the page address, cookies, passwords or form contents you have typed to anyone, and it does not store the page. It remembers the target language you chose.
• Please avoid using it on pages that show sensitive personal information, such as banking or medical pages.

Legal basis: contract, Art. 6(1)(b) GDPR.

3.5 Share extension

When you share an image, PDF, RTF or text file to Snap from another app, the extension copies the file into a storage area on your device shared between Snap and its extensions, and opens Snap. The extension itself sends nothing over the internet; it records usage events that the main app later sends to our analytics if analytics is on (section 3.10). What happens next depends on the feature you use (sections 3.1, 3.6).

3.6 Tools: documents, forms and listings (AI features)

Some Tools use AI models. Before your content is sent, the app asks for your agreement in the flow.

• Explain or summarize a document, and fill in a document form: the text extracted from the document, your target language and, for forms, the purpose you choose and the form's field labels are sent through our server to an AI model provider. Your saved "My details" are not sent.
• Form snapshot: only the printed questions read from the form are sent as text; the photos and your answers stay on your device.
• Write a marketplace listing: the photos you add (reduced in size, with location data in the photo's metadata removed), any notes you type about the item, and the listing language are sent through our server to an AI model provider. The app then opens the marketplace you choose (for example Vinted, OLX or Facebook Marketplace) for you to post it yourself; we do not post anything for you.
• PDF and document translation: the document's text is translated as described in sections 2 and 3.1.

Legal basis: contract, Art. 6(1)(b) GDPR. Where the app asks for your agreement before sending, you can decline and the feature will not run.

3.7 AI Keyboard

If you add the Snap AI Keyboard and give it "Full Access", the text you choose to process (for example to translate, rewrite or correct) is sent through our server to an AI model provider when you tap an AI action. The keyboard does not send what you type otherwise, and reads your clipboard only when you use its paste action. Full Access is needed to reach the internet and to share settings with the app. If you turn on its optional history, AI results are kept on your device for 30 days; a short technical activity log (the type of action, character count and model used, not your text) is kept on your device for 24 hours.

The keyboard does not record or send usage events and never includes what you type in any analytics. It keeps only a few dates and times on your device, used to see how many people reach each step: when you first used an AI action, when Full Access was granted, when the keyboard was enabled, when you reached the free limit, and which days you were active. These markers contain no text. When you next open the Snap Translator app, it sends these dates to our analytics as step events, under the same analytics choice as the rest of the app (anonymous mode if you have not allowed analytics).

Legal basis: contract, Art. 6(1)(b) GDPR.

3.8 Widgets, Control Center and Apple Watch

Widgets and Control Center buttons only open the app at the right screen and do not send data themselves. Opening the app from a control passes the in-app link to Meta and Branch only if you have allowed tracking (section 3.12).

The Apple Watch app syncs your language pair, your recent translations (original and translated text, languages and date) and whether you have a subscription with your iPhone directly over Apple's Watch connection, and keeps a small cache on the Watch. Text you translate on the Watch is sent from the Watch to Google Cloud Translation; voice works as described in section 3.3.

3.9 iCloud

If you are signed in to iCloud and sync is on, Snap syncs your translations, dialog messages and photo translation history (including the photos) to your own private iCloud database so they appear on your other devices. Sync is on by default when you are signed in to iCloud, and you can turn it off in the app's Settings.

Snap also keeps your language pairs (if language-pair sync is on, which has its own switch in Settings) and your free-use counters (always) in iCloud key-value storage under your Apple Account.

Apple stores this data under your Apple Account; we cannot access it. Apple's privacy policy applies to iCloud.

Legal basis: contract, Art. 6(1)(b) GDPR.

3.10 Usage analytics

We use Amplitude to understand how the app is used, so we can fix problems and improve features.

Your choice.

• In the EEA (and where your region is unknown, which we treat as the EEA), the app shows a one-time "Share usage analytics?" sheet. If you tap Allow, analytics is on in full. If you tap Not now, or never answer, analytics stays in anonymous mode.
• Outside the EEA, analytics is on in full by default. You can turn it off at any time in the app's Settings with the Share usage analytics switch, which puts the app in anonymous mode. You can also change the EEA choice there. Turning analytics on applies the next time you open the app.

Full analytics. Amplitude receives:

• events such as screens viewed, app opens and sessions, buttons tapped, features used, translations succeeding or failing, paywall views, purchases (including product, price and currency) and subscription changes, together with details such as language codes, counts, durations, error categories and which engine was used, and, when you choose a next step after the AI explains a document, the kind of document the AI identified (for example "rental agreement" or "visa application");
• user properties such as app version, interface language, your camera language pair, whether onboarding is finished, what you said you want to use the app for during onboarding, how many times you opened the app, whether you have used Tools, whether the keyboard is installed, whether iCloud sync is on, and your subscription status and plan;
• your device's identifier for vendor (IDFV), an identifier Apple gives to all apps from the same developer on your device, which Amplitude uses as your device ID; app session data, device model, OS version, language, and approximate location (city, region, country) that Amplitude derives from your IP address;
• if you installed the app from an Apple Search Ads campaign, the campaign, ad group, keyword and creative set identifiers and country or region that Apple's own attribution service (AdServices) returns; and, if you arrived through a Branch link, the link's channel, campaign and feature.

Anonymous mode. Amplitude still receives a small set of events, but:

• the device ID is a random value created each time the app starts, kept only in the app's memory and never stored on your device, so it cannot link one session to the next;
• there is no user ID, and collection of IP address, city, region, country, carrier and IDFV is switched off;
• only a short list of non-personal event properties is sent, and each event is tagged as anonymous;
• the events are not linked to RevenueCat, Meta, Branch or Sentry, Apple Search Ads attribution is not collected, and Sentry crash reports are off (section 3.11).

We design our events never to include the text you translate, speak, scan or type. Events from the share extension and Safari action are queued on your device and sent by the main app.

Legal basis:

• EEA, full analytics: your consent (Art. 6(1)(a) GDPR; Art. 399 of the Polish Electronic Communications Law, which implements Art. 5(3) of Directive 2002/58/EC). You can withdraw it at any time with the "Share usage analytics" switch, as easily as you gave it.
• EEA, anonymous mode: we do not store an identifier on your device. The app creates a random ID in memory for the current launch only, and it is discarded when the app closes. We send only a small set of anonymous counts about how the app is used, on the basis of our legitimate interest in knowing whether the app works and which features are used (Art. 6(1)(f) GDPR). You can object at any time (section 8).
• Elsewhere, including the UK: our legitimate interest in maintaining and improving the app (Art. 6(1)(f) GDPR) and, in the UK, the statistical-purposes exception under PECR; you can object by turning the switch off.

Your right to object. Where we rely on legitimate interests (analytics outside the EEA, crash reports, abuse prevention), you can object at any time by turning off Share usage analytics or by emailing [email protected]. We will stop unless we have compelling legitimate grounds.

3.11 Crash and error reports

We use Sentry to receive crash reports, error reports and app log messages about errors: device model, OS and app version, technical error details, performance timings for a sample of sessions (including the addresses of the network requests timed), and your IDFV (the same identifier Amplitude uses in full mode), so we can link a crash to a session. We remove the text of buttons you tap and the addresses and query strings of web requests from breadcrumbs and error reports, because they could contain your text.

Crash reports are sent only if usage analytics is on. In the EEA that means only if you tapped Allow on the analytics sheet. If you turn off Share usage analytics, or stay in anonymous mode, Sentry is off and no crash reports are sent.

Legal basis: in the EEA, your consent (Art. 6(1)(a) GDPR and Art. 399 of the Polish Electronic Communications Law). Elsewhere, legitimate interest in keeping the app working, Art. 6(1)(f) GDPR.

3.12 Attribution and the tracking prompt

Snap shows no ads. To measure which marketing campaigns bring users to the app we use:

• Meta (Facebook) SDK: records app installs, app opens, in-app purchases and subscriptions (product, price and currency) and some in-app events (for example opening the camera) for Meta's ad measurement, and handles links from Meta ads. Meta may use this information to provide measurement services, target ads and improve its products, under the Meta Privacy Policy (https://www.facebook.com/privacy/policy). You can also control this in your Facebook settings under "Your activity off Meta technologies", and through the iOS tracking setting.
• Branch: handles links into the app and attributes installs to campaigns.
• Apple AdServices: Apple's own attribution for Apple Search Ads, used by us and by RevenueCat.

When these start: Apple's App Tracking Transparency prompt asks whether Snap may track you. The Meta and Branch SDKs collect attribution data only after you tap Allow. Before you answer, and if you tap Ask App Not to Track, Meta's automatic event logging and advertiser-identifier collection are off, and Branch only opens links into the app and collects no attribution data. Only if you tap Allow do these partners receive your device's advertising identifier (IDFA) and the data described above. You can change your choice at any time in iOS Settings, Privacy and Security, Tracking. Events from anonymous-mode analytics are never sent to Meta or Branch.

Legal basis: your consent given through the iOS tracking prompt (Art. 6(1)(a) GDPR; Art. 399 of the Polish Electronic Communications Law). Meta and Branch receive data only after you tap Allow.

3.13 Subscriptions and purchases

Purchases are processed by Apple. We use RevenueCat to check whether your subscription is active and to manage offers. RevenueCat receives an anonymous app user ID, your purchase and subscription history from Apple, your IDFV, the Apple Search Ads attribution token (AdServices), device and app information, and your IP address. RevenueCat does not receive your advertising identifier. We never receive your payment card details.

Legal basis: contract, Art. 6(1)(b) GDPR, and our legal obligations for accounting where applicable (Art. 6(1)(c)).

3.14 Feedback you send

If you send feedback in the app, we receive your rating, your message, the app version, your plan type, device model, OS version, locale, coarse country, region setting, app and device languages, time zone, and a technical log of recent app activity that is attached. That log contains steps, timings, errors and iCloud sync status. It does not include the text you translate, and the feedback carries no account or device identifier. It is delivered through our server to our internal support channel. Please do not include personal information in your message that you do not want us to see.

If you contact us by email ([email protected]), we receive your email address and whatever you write, and use them to reply.

Legal basis: legitimate interest in answering you and improving the app, Art. 6(1)(f) GDPR.

3.15 Notifications

If you allow notifications, iOS gives the app a push token, which is stored on your device and not sent to any notification service. We record in analytics whether registration succeeded. The app also schedules local reminders on your device.

3.16 Ratings

The app may ask whether you are enjoying Snap and invite you to rate it on the App Store. Your App Store review is handled by Apple.

3.17 Data we receive from others

From Apple, we learn the Apple Search Ads campaign that led to your install and your subscription status (through RevenueCat). From Branch and Meta, we learn the link or ad campaign you came from, if you allowed tracking. We do not receive your name or contact details from them.

4. Content you translate

Much of what people translate is personal: letters, forms, menus, medical leaflets, messages, ID documents. Please keep in mind:

• Anything processed on a server (see sections 3.1 to 3.8) leaves your device and is handled by the providers in section 5.
• If you do not want a document to leave your device, download an offline language pack, choose the source language yourself (not Detect), translate while offline, and avoid the AI Tools and voice features for that content. Documents in scripts other than Latin, Chinese, Japanese and Korean, and documents scanned with the source set to Detect, may need a server to be read.
• Sensitive content. If what you choose to translate contains information about your health or other sensitive matters, we process it only to give you the translation you asked for, relying on your explicit consent (Art. 9(2)(a) GDPR), given by choosing to translate it.
• We do not use your content to build advertising profiles, and we do not sell it.
• We do not use your personal data or your content to train AI models, and we instruct our AI providers not to. Google does not use content sent to Cloud Translation or Cloud Vision to train its models; it temporarily logs request metadata (such as time and size) to run the service and combat abuse.
• Our server forwards AI and voice requests to the AI provider and does not store their content. Requests go only to the providers listed in section 5. Our AI providers may not use your requests to train models; some may keep requests for a short period for abuse monitoring under their terms. Google Cloud processes translation and image requests under Google Cloud's terms for its customers.

5. Who we share data with

We use these service providers ("processors") to run the app. They may only use the data to provide their service to us, except where noted.

• Google Cloud (Google LLC / Google Ireland Ltd): text translation and language detection (Cloud Translation), reading text from photos (Cloud Vision), and hosting our translation and recognition services. Data: text to translate, page text and titles from the Safari action, photos sent for recognition, language codes, IP address. Location: our services run in the United States, and Google may process the content in any Google location. https://cloud.google.com/terms/cloud-privacy-notice
• Google (ML Kit, Firebase Installations): diagnostics and usage data from the on-device text recognition software (section 2). Google acts under its own terms. https://policies.google.com/privacy
• Cloudflare, Inc.: runs our proxy server that forwards AI, voice and feedback requests, and limits request rates by IP address. Data: request content in transit, IP address. Location: global network. https://www.cloudflare.com/privacypolicy/ and https://www.cloudflare.com/cloudflare-customer-dpa/
• OpenRouter, Inc.: routes AI and speech-to-text requests to model providers. Data: text, document text, form labels, photos for listings, audio. Location: United States. https://openrouter.ai/privacy
• AI model providers and hosting providers reached through OpenRouter. Requests go only to providers we select, such as Microsoft Azure, Amazon Web Services, Google Cloud and the hosts of the open-weight models we use, including for speech-to-text. Email [email protected] for the current list. Data: the content of the request. https://openai.com/policies/privacy-policy, https://www.microsoft.com/privacy/privacystatement, https://aws.amazon.com/privacy/, https://policies.google.com/privacy
• Amplitude, Inc.: usage analytics. Location: United States. https://amplitude.com/privacy
• Functional Software, Inc. (Sentry): crash reports, error reports and performance data. Location: United States. https://sentry.io/privacy/
• Zoho Corporation (Zoho Mail). Support email, hosted in Zoho's EU data centre (zoho.eu). Data: your email address, message and attachments. https://www.zoho.com/privacy.html
• RevenueCat, Inc.: subscription status. Location: United States. https://www.revenuecat.com/privacy and https://www.revenuecat.com/dpa

These partners act as independent controllers for some of the data they receive, under their own policies, and Meta is a joint controller with us as described below:

• Meta Platforms Ireland Ltd / Meta Platforms, Inc.: ad measurement, app and purchase events. For collecting and sending app events through the Meta SDK, we and Meta Platforms Ireland Ltd are joint controllers under the Meta Business Tools Terms and its controller addendum; we are responsible for this notice and for your choice in the tracking prompt, and Meta is responsible for its own later use as an independent controller. You can exercise your rights against either of us. https://www.facebook.com/privacy/policy/
• Branch Metrics, Inc.: deep links and install attribution. https://legal.branch.io/saas/privacy-policy/ and https://legal.branch.io/saas/subprocessor-list/
• Apple Inc.: App Store purchases, iCloud, AdServices attribution, on-device frameworks. https://www.apple.com/legal/privacy/

Each of these providers is bound by a contract or by its published terms to protect your data at least as well as this policy describes and to use it only for the purposes listed here. Meta and Branch are also bound by their own privacy policies and by their terms with us.

We may also disclose data if required by law, to protect our rights, or as part of a merger or sale of the business, in which case this policy will continue to apply.

6. International transfers

Several providers above process data in the United States or other countries outside the European Economic Area and the UK. The safeguard we rely on for each:

• Amplitude, Branch, Sentry, Google, Meta, Microsoft and Amazon: the EU-U.S. Data Privacy Framework and its UK extension (Art. 45 GDPR), with Standard Contractual Clauses as a fallback.
• RevenueCat and OpenRouter: Standard Contractual Clauses (Commission Decision 2021/914, Art. 46(2)(c) GDPR) and the UK International Data Transfer Addendum, in their data processing addenda. We do not rely on the Data Privacy Framework for RevenueCat.
• Cloudflare: the Standard Contractual Clauses and UK Addendum in Cloudflare's customer data processing addendum.
• Hosts behind OpenRouter: the Data Privacy Framework or Standard Contractual Clauses, depending on the host.

You can get a copy of the safeguards by emailing [email protected], using the contact details in section 14.

7. How long we keep data

• On your device: history, dialogs, scans and settings stay until you delete them in the app or delete the app. The most recent voice recording per language stays until replaced. A cache of up to 500 recent translations is kept for offline use. Keyboard AI history (if enabled) is kept for 30 days and its activity log for 24 hours. "My details" stay in your Keychain until you clear them.
• Apple Watch: a small cache of your language pair and recent translations, until replaced by the next sync or you remove the Watch app.
• iCloud: until you delete the data in the app, turn off sync and remove it from iCloud, or delete your iCloud data. Language pairs and free-use counters in iCloud key-value storage stay until you remove Snap's iCloud data.
• Translation, recognition and AI requests: our services process them to return a result and do not keep the content. Cloudflare keeps request logs for up to 7 days. Google Cloud keeps technical logs for these services for a limited period.
• Analytics (Amplitude): 24 months from when they are received, then deleted automatically. Anonymous-mode events are not linked to you and are kept under the same period.
• Crash reports (Sentry): up to 90 days.
• Subscription records (RevenueCat): RevenueCat keeps subscription records for as long as we hold an account with it and up to six years afterwards.
• Feedback and support emails: as long as needed to handle your request and any follow-up, then deleted.
• Advertising and attribution partners (Meta, Branch): under their own policies.

7a. Deleting your data

Snap has no account, and we keep no user data on our own servers, so there is no account for us to close. Your data is on your device, and copies sit with the third-party providers in section 5. To delete it:

• On your device, in the app: go to Settings, Privacy, Delete my data. This wipes everything Snap stores on the device: history, dialogs, saved photos and scans, keyboard logs, the storage shared with the extensions, "My details" in the Keychain, and the widget, Apple Watch and Messages data. It also resets the analytics ID and returns the app to onboarding. Deleting the app also removes the app's and its extensions' data from the device, but "My details" stay in the iOS Keychain after the app is deleted, so use Delete my data first.
• iCloud: turn off iCloud sync in Snap's Settings, then remove Snap's data in iOS Settings, [your name], iCloud, Manage Storage (or Manage Account Storage). This also removes your language pairs and free-use counters stored in iCloud key-value storage. We cannot delete data in your iCloud for you.
• Device backups: older backups of your iPhone may still contain your history and recordings until those backups are deleted.
• Copies held by third parties (analytics, crash reports, purchase records): these are not on our servers and the in-app deletion does not remove them. Open Settings, Privacy, where the Support ID is shown (tap to copy; in anonymous mode it shows your device's vendor ID instead, because the analytics ID is random on each launch), paste it into an email to [email protected] and ask us to have them deleted. We then send the request to the provider that holds them. Anonymous-mode events cannot be linked to you, so they cannot be found or deleted individually.
• Meta and Branch: if you ask us, we will also pass your deletion request to Meta and Branch for the data their SDKs received from Snap. They respond under their own policies.
• Advertising identifier: reset it or limit tracking in iOS Settings, Privacy and Security, Tracking.
• Subscriptions: Delete my data does not cancel a subscription. Subscriptions are managed by Apple: cancel in iOS Settings, [your name], Subscriptions. Deleting the app does not cancel one either.

8. Your rights under GDPR and UK GDPR

If you are in the EEA, the UK or Switzerland, you have the right to:

• access the personal data we hold about you and get a copy;
• correct inaccurate data;
• have your data deleted;
• restrict or object to our processing, including processing based on legitimate interests;
• receive your data in a portable format;
• withdraw consent at any time (for example by changing the tracking setting in iOS or switching off Share usage analytics in the app), without affecting earlier processing;
• not be subject to decisions based solely on automated processing that significantly affect you (we do not make such decisions).

To use these rights, email [email protected], and include your Support ID if the request concerns analytics, crash or subscription records. We will answer within one month, which may be extended where the law allows.

You also have the right to complain to a data protection authority. Our lead authority is the Polish Prezes Urzędu Ochrony Danych Osobowych (UODO), ul. Stawki 2, 00-193 Warszawa, Poland, https://uodo.gov.pl. You can also complain to the authority where you live or work. In the UK, this is the Information Commissioner's Office (https://ico.org.uk).

9. US privacy rights (California and other states)

In the last 12 months we have collected these categories of personal information: identifiers (identifier for vendor, anonymous app user ID, Support ID, IP address, and, if you allow tracking, the advertising identifier); commercial information (subscription and purchase history); internet or other electronic network activity (in-app usage); geolocation (approximate, derived from IP address); audio information (voice recordings in Dialogs and on Apple Watch, processed to provide transcription); and user content (text, photos, documents and web page text you choose to translate, and feedback you send). Sources and purposes are described in section 3, and recipients in section 5.

We may also process sensitive personal information: government ID numbers, health information and message contents that may appear in photos, documents or text you choose to translate or to process with the keyboard. We use it only to provide the translation or AI result you request, and we do not keep it.

Advertising measurement and your choices. We do not sell your personal information for money. If you allow tracking, the Meta and Branch SDKs receive device and usage data, including purchase events for Meta, and your advertising identifier, to measure our ads. Some US state laws call this "sharing" or "targeted advertising". HopIn.IT is a small company based in Poland and, as far as we have assessed, the thresholds of those laws do not currently apply to us. You still get the same choices wherever you live. To stop this, tap "Ask App Not to Track" in the tracking prompt, or turn off tracking for Snap in iOS Settings, Privacy & Security, Tracking. Then Meta and Branch collect no attribution data from Snap. You can also email [email protected] with the subject "Privacy choices".

You have the right to know what we collect, to access it, to correct it, to delete it, to opt out of advertising measurement (see above), and to limit use of sensitive personal information. You can use these rights, or have an authorized agent use them for you, by emailing [email protected]. We may need to verify your request. We will not discriminate against you for using any of these rights. Residents of other US states with similar laws have comparable rights and can contact us the same way.

Appeals. If we decline your request, you can appeal by replying to our answer with the subject "Appeal". We will answer within 60 days. If you are not satisfied, you can contact your state attorney general.

Do Not Track. Our apps do not respond to web browser Do Not Track signals, because they are apps, not websites. You control tracking in iOS Settings, Privacy and Security, Tracking, and analytics in the app's Settings, Share usage analytics.

10. Subscriptions via Apple

All payments are processed by Apple under Apple's terms and privacy policy. We receive confirmation of your purchase and subscription status (through Apple and RevenueCat), never your payment details. You can manage or cancel subscriptions in your App Store account settings.

11. Children

Snap is intended for people aged 16 and over in the EEA and 13 and over in the UK and elsewhere, and we do not knowingly collect personal data from younger children. If you are younger, do not allow tracking or use AI features without a parent's permission. Snap's App Store age rating is 13+. If you believe a child has used a server-based feature and sent us personal data, contact us and we will delete what we can.

12. Security

Data sent between the app and our servers is encrypted in transit (HTTPS), and connections to our AI proxy use certificate pinning. Sensitive details you save for forms are kept in the device Keychain, are never sent to us or any AI provider, and cannot be restored onto a different device. Only authorized team members can access analytics, crash and feedback tools. No system is perfectly secure, so please do not send highly sensitive documents through server-based features unless you need to.

13. Changes to this policy

We may update this policy when the app or the law changes. We will change the "Last updated" date and, for significant changes, tell you in the app or in the App Store release notes before they take effect.

14. Contact

HopIn.IT sp. z o.o.
ul. Marsz. Józefa Piłsudskiego 74/320, 50-529 Wrocław, Poland
Email: [email protected]