Deep In

Privacy Policy

Effective: 4 July 2026 · Last updated: 14 November 2026

This Policy covers the Deep In mobile app (iOS and Android). Section 10 covers the deepin.world website.

1. Who controls your data

The data controller is DEEP IN EDPK, a company registered in Bulgaria. EIK: 208772397. Registered address: bul. Slivnitsa 188B, office 17, Oborishte district, 1202 Sofia, Bulgaria. Privacy contact: daryna@deepin.world.

2. What data we process

2.1 Account & authentication. Email; account and session identifiers. You can sign in with a one-time code sent to your email, or with Apple or Google — we never store passwords. When you sign in with Apple or Google we receive a stable identifier for your account with them and, if you allow it, your email address. Apple’s “Hide My Email” gives us a relay address (@privaterelay.appleid.com) instead of your real one.

2.1.1 The first day. The first 24 hours after you register are free. That day belongs to the device rather than to the account: it is tied to a random identifier the app generates itself and keeps in the phone’s secure storage. It cannot identify you personally and exists only to stop one device from claiming a free day over and over — which is why it stays on the device after an account is deleted. Legal basis: our legitimate interest in preventing abuse (GDPR Art. 6(1)(f)).

2.2 Profile & settings. Name (optional), avatar, native language, learning language, proficiency, motivation, daily goal, notification and player preferences, activity streaks.

2.3 Learning content. Saved words and translations, history and progress, bookmarks, videos you add by URL, AI-tutor conversations, and photos you attach to a conversation — we pass these to the model as part of the request and do not store them ourselves.

2.4 Voice. During a spoken AI conversation your audio is streamed in real time to OpenAI. We store session duration (in seconds, for plan limits) and the text transcript in your chat history; we keep no persistent raw-audio archive on our servers. When you dictate a message, the app records a short audio file and sends it to OpenAI for transcription; the file is not kept afterwards.

2.5 Subscription. Status and subscription tier and a technical purchaser identifier are provided by RevenueCat via the Apple App Store and Google Play. We never receive or store your payment card details.

2.6 Technical data & notifications. Push-notification token (with your consent), app usage data (section 9), crash reports — which carry a technical user identifier for diagnostics but none of your text — and a random device identifier the app generates itself and keeps in the phone’s secure storage. We do not use advertising identifiers ourselves; on Android Branch reads one for the referral programme (section 4). On iOS the app asks for no tracking permission and receives no advertising identifier.

3. Purposes and legal bases (GDPR Art. 6)

PurposeBasis
Account, sign-in, running the app, vocabulary, progress, translations, AI tutor, voice, transcription, subscriptionContract — Art. 6(1)(b)
Security, abuse prevention, rate-limiting, diagnosticsLegitimate interest — Art. 6(1)(f)
Push notificationsConsent — Art. 6(1)(a)
App usage data (section 9)Legitimate interest — Art. 6(1)(f), with the right to object at any time using the switch in Profile → Account
Abuse prevention (device fingerprint for the anonymous start)Legitimate interest — Art. 6(1)(f)

Where consent is the basis, you can withdraw it at any time without affecting the lawfulness of prior processing.

4. Who we share data with (processors)

We do not sell your data. We use trusted providers that act on our instructions under data processing agreements (DPAs):

5. International transfers

Some processors are located outside the European Economic Area, including in the United States (Anthropic, OpenAI, Google, RevenueCat, Cloudflare, Resend). For those transfers we rely on the Standard Contractual Clauses (SCCs) approved by the European Commission and/or adequacy decisions and Data Privacy Framework certification where applicable. Sentry processes data in the EU. The Convex database is hosted in the EU (AWS eu-west-1); Convex itself is a US company, so access by its support may occur from there.

6. How long we keep data

7. Your rights (GDPR)

You have the right to access (Art. 15), rectification (16), erasure (17), restriction of processing (18), data portability (20), objection (21), and to withdraw consent.

8. Age and children

Deep In is intended for people aged 16 and over. The app asks your age on first launch; anyone who answers under 16 is not granted access. Sixteen is the default digital-consent age under GDPR Art. 8, so no separate parental consent is required to use the app.

We do not knowingly collect data from anyone under 16. If you believe a child has provided us data, email daryna@deepin.world and we will delete it.

Because 16- and 17-year-olds may use the app, we follow the UK Age Appropriate Design Code: the app carries no advertising, does no profiling for advertising purposes, requests no location access, and ships its privacy settings at their most protective defaults.

9. Analytics in the app

The app’s usage analytics is our own: it is stored on our servers and no third-party analytics service receives it. We record which features you use, which videos you open and how much of each you watch, how many messages you send Solomia (never their text), what you do on the subscription screen, and where something in the app fails — along with your app version, platform, subscription tier and the languages you have set. We do not record conversation text, audio, photographs or screen images.

We keep these records for 90 days. You can switch the collection off at any time in Profile → Account: it stops immediately, and what was already collected goes within the same 90 days. There are no advertising trackers, no Meta/TikTok pixels, no Google Analytics and no Umami in the app. Push notifications are only turned on with your consent.

10. The deepin.world website

This section covers the deepin.world website, not the app.

10.1 Analytics without cookies. We count visits to the home page with Umami, which sets no cookies. Legal basis: our legitimate interest in knowing how the site is used (GDPR Art. 6(1)(f)).

10.2 Meta Pixel. In the EU, Norway, Iceland, Liechtenstein and the UK (including the Channel Islands, the Isle of Man and Gibraltar), a banner on the first page where the pixel runs asks whether we may use Meta cookies: until you choose “Accept”, the Meta Pixel is not loaded and our site sends nothing to Meta. The banner also asks first when your browser does not let the site store anything, since we could not remember a refusal. Elsewhere the pixel runs straight away, and you can turn it off at any time with “Cookie settings” (section 10.3). We treat a Global Privacy Control signal from your browser as a refusal everywhere: no banner appears, and the pixel stays off unless you turn it on in “Cookie settings”. The site works out your country from your IP address, via Cloudflare, and from your device’s time zone (a phone takes it from the network it is on), only to make this decision, and stores neither. If you decline, the site works just the same.

10.3 Opting out. At any time, with the button below or “Cookie settings” at the bottom of the site’s pages. Choose “Decline” and our site sends nothing more to Meta, and the _fbp and _fbc cookies are deleted from your browser. Opting out does not affect processing that took place before it, and it does not take you out of an audience you were already added to; that ends at most 180 days after your last visit. To control how Meta uses information from other websites for ads, use the ad settings in Meta’s Accounts Centre, or youronlinechoices.eu (EU) or aboutads.info/choices (US). Your choice itself is kept only in your browser (local storage), so the site does not ask on every page. A refusal holds until you change it or your browser deletes the site’s data (Safari does this on its own after seven days of use without any interaction with this site); a Global Privacy Control signal in your browser is the way to say no that does not wear off. An acceptance lasts a year, after which, in the EU, the EEA and the UK, the site asks again.

11. Security

Data is transmitted over encrypted connections (HTTPS/TLS). System access is restricted. No method is 100% secure, but we apply technical and organizational measures proportionate to the risk. In the event of a breach that risks your rights, we will notify you and the relevant authority as required by law.

12. Notice for U.S. users (CCPA/CPRA)

If you are a California resident, you have the right to know what personal information we collect, to request its deletion or correction, and not to be discriminated against for exercising these rights. We do not sell or "share" your personal information as those terms are used under the CCPA/CPRA, except that the Meta Pixel on the website (section 10), which runs by default outside the EU and the UK, counts as "sharing"; you can opt out of it at any time with Cookie settings (section 10.3), and we treat a Global Privacy Control signal as an opt-out. Requests — daryna@deepin.world.

13. Changes to this Policy

We may update this Policy. We will notify you of material changes in the app or by email and update the date at the top.

14. Contact

Privacy questions — daryna@deepin.world.