Privacy

Privacy Policy

Dubashi Learn is made by Friendly Characters Limited, a company registered in England. This policy explains exactly what we collect, why, and what we do not collect.

Last updated: 18 August 2026

The short version

• You sign in with Google. We store your account identifier, and your name and email come from Google.
• We store your plan and usage counters so the app knows what you have paid for and how much you have used.
• Your learning — your review deck, your transcripts, your saved scenes — is stored on your phone, not on our servers.
• When you speak to Meera, that recording is sent to our server so she can understand you, used for that reply, and not kept.
• We do not sell data. We show no advertising. We run no analytics or crash-reporting product in this app.

What we store on our servers

All of it is tied to your account identifier, and all of it is listed here — there is nothing else.

• Your account. The identifier Google gives us when you sign in, plus the name, email address and profile picture your Google account provides.
• Your language pairs. Which language you are learning and through which, and any other pairs you have added.
• Learning preferences. The goal you chose when you started, and — for languages that change words by whether you speak as male or female — the grammatical form you told us to use, so the coach speaks about you correctly. You can change it any time, and it is deleted with your account.
• Usage counters. How many messages you have exchanged with Meera this month, and totals used for your allowance. These are counts, not content.
• Your plan. Whether you have a subscription, which one, when it renews or expires, and the purchase token Google Play gives us so we can verify and reconcile it.
• Course requests. If you ask for a language pair that does not exist yet, we record the request so we can build it and tell you when it is ready.
• Content reports. If you flag a lesson as wrong, we store which lesson, which pair, the reason you picked and any note you added.

What stays on your phone

These never reach our servers at all. If you uninstall the app without exporting them first, they are gone — we cannot recover them for you, because we never had them.

• Your review deck and every Dialogue Prompt in it
• Your scene transcripts and any situations you created
• Which lessons you have completed, and your practice history
• Recordings of Meera's voice saved for replay
• Your settings, and your microphone and recording consents

Your voice

Two different things happen depending on where you are in the app, and the app tells you which before you first use the microphone.

• Drills and review. Your speech is processed by your phone's own Google speech service — on the device where an offline language pack exists, otherwise through that service online. It never reaches our servers.
• Conversations with Meera. Each turn's recording IS sent to our server so she can understand what you said, in either language. It is used to produce that one reply and is not stored. Your first name travels with the request so Meera can say it, and is likewise not kept.

Who else is involved

• Google. Sign-in, our database and servers, hosting, and the AI models that produce Meera's understanding and her voice. Your conversation turns are processed by Google's Gemini models on our behalf, under our Google Cloud agreement.
• Google Play. If you subscribe, Google Play is the merchant. They handle the payment; we never see your card details.

There is no one else. We use no advertising network, no analytics product, and no third-party tracking of any kind.

Where your data is held

Our servers and database run in Google Cloud's europe-west2 region (London). Some Google services may process data in other regions on our behalf under standard contractual clauses.

How long we keep it

• Account data is kept while your account exists.
• Delete your account and it enters a 30-day grace period, after which it is permanently removed — how to delete your account.
• After deletion we keep seven records, and they are not all the same kind of thing — the full list, and why each one exists.

  Three with our link to you removed. The record of any purchase, so a refund can still be reconciled with Google Play; and, if a course was still being built for you when the deletion ran, that build's record, so the build can finish and the queue keeps working for everyone else. In both, the identifier that pointed at your account is replaced with a marker that points at nobody. Google Play keeps its own record of any purchase, which is what makes a refund possible — so what changes is that we stop holding the link, not that the purchase becomes untraceable. And any report you sent us about something the coach said: we keep the report and a copy of what she said, because her replies are generated as you talk and that is the only copy, so it is the only way to look into it.

  Four still filed under your account identifier — the internal id we generated when you signed up, never your name or email, both of which are deleted. A marker recording that the account was deleted, which stops a subscription renewal quietly recreating an account you asked us to remove. The deletion request itself — when you asked, when it was carried out, and whether the account had a subscription at the time. Any content report you made, because it is how the course gets fixed for everyone else: we remove your identifier from inside the report, but the report is filed under a reference that still contains it, so we do not describe it as fully anonymous, and if you typed a note in your own words we keep what you typed. And, if a course build we ran for you failed, the record of that failure, so we can tell whether you were owed a refund — it holds your account identifier, the language pair, whether you had a subscription and which plan, and whether a refund was due. We keep these four for security, for refunds and for audit. None can be used to contact you, and the records that connected that identifier to your name or email are gone.

• Our servers write technical logs as they run, and some lines contain your account identifier — including the line recording that a deletion finished. They hold no name, no email, and nothing you said or typed in a lesson. Google Cloud deletes them automatically 30 days after they are written.
• Voice recordings from conversations are not retained at all.

Your rights

Under UK GDPR you can ask for a copy of your data, ask us to correct it, or ask us to delete it. Two of those are built into the app: open the Me tab and use Export my data or Delete my account under Privacy. For anything else, email privacy@dubashi.com.

You also have the right to complain to the Information Commissioner's Office (ico.org.uk) if you think we have handled your data wrongly.

Children

Dubashi Learn is a general-audience app and is not directed at children. We do not knowingly collect data from anyone under 13.

Changes

If we change what we collect or why, we will update this page and change the date at the top. Where the change affects how your voice or your recordings are handled, the app asks you to agree again before you next use the microphone.

Contact

Friendly Characters Limited, registered in England.
privacy@dubashi.com