What we keep, and why.

DUB is made and run by Sam Brownfield, based in the United Kingdom. For the purposes of UK and EU data protection law, Sam Brownfield is the controller of the personal data described here. You can reach us at sambrownfield3@gmail.com.

Without an account. You do not need an account to use DUB. When you first open it, we set a cookie holding a random device ID, and your progress is tied to that. Your learning record is stored on your phone and also copied to our server, so it can be restored later and so we can see which lessons work. That record holds:

• what you have learned and what you have said
• the choices you made while setting up, such as your interests and why you are learning
• the guide you picked
• a name, if you gave one
• your browser type
• a log of what you did in the app, such as which screens you opened and which answers you got right

Your Legend, if you fill it in. The Legend is an optional set of questions about yourself, answered so you can practise introducing yourself. Every question can be skipped. Depending on what you choose to answer, it can include:

• your name, age and nationality
• whether you are married or in a relationship
• your children's names and ages
• your work
• why you came and how long you are staying

It is stored with the rest of your learning record, on your phone and on our server. Some answers, such as who you are with, can reveal personal things about you. Only answer what you are comfortable with.

With an account. Signing in is done by an emailed link; there is no password. We keep:

• your email address
• a name, if you choose one
• your language settings
• whether you have asked for emails about new drops
• when you joined and when you were last seen

For each sign-in link we record the email address it was sent to and the IP address the request came from. For each signed-in session we record your browser type. Your account links your learning record across your devices.

The translator and the menu reader. Text you type into the translator, and photos you take with the menu reader, are sent to Anthropic, whose AI model writes the translation. We keep the text you asked about and the answer, but not the photo: for a photo we record only that a photo was read, and what it said. To enforce the daily limit we also store a scrambled code made from your IP address, created in a way we cannot reverse back into the address.

Your microphone. When you tap to say something aloud, your browser listens once and turns what you said into text, which DUB compares with the line on your phone. DUB does not receive, record or store the audio or the words you said; we only log whether it was close. Speech recognition is done by your browser or phone, not by us, and depending on the device, Apple or Google may process the audio on their own servers under their own privacy policies.

Your camera. It is used only while the menu reader is open, and only the photo you choose to take is sent, as described above.

A profile photo, if you add one, stays on your phone and is never uploaded.

Payments. If you buy Pro on the web, Stripe handles the payment. We give Stripe your email address and your account ID. We keep your Stripe customer and subscription references, your plan, whether it is active, and when it renews or ends. We never see or store your card details.

Notifications. If you turn on notifications (the daily line and word of new drops), we store the address your browser gives us for sending notifications, along with your time zone (so it arrives in the morning) and which lines you have already been sent. Notifications are delivered through your browser maker's push service (for example Apple's or Google's).

Sharing, invitations and tables.

• A share card is a snapshot of lines you can say. Anybody you give the link to can see it.
• An invitation records who sent it and who accepted it, so both of you can be given the reward. We never read your contacts.
• If you take a seat at a table, the others at that table see your first name, or “Someone” if you have not given one, and nothing else about you.
• If you report or block somebody after they show you a card, we keep a record of that.

Feedback and the waitlist. If you send feedback, we keep what you wrote, any email address you chose to leave, and some context: how far you are, where you were in the app, and your device. If you join a waitlist, we keep your email address and any note you added.

Searches that find nothing. If you search the word library and get no results, we keep the search so we know what to add.

On your phone only. Your settings, the last few error reports, and your profile photo stay on your device. You can view and clear the error reports in Settings.

We use two cookies, both our own and both strictly necessary for DUB to work:

• a device cookie, which remembers your progress and lasts up to two years
• a sign-in cookie, which keeps you signed in for up to 90 days

There are no advertising or analytics cookies, ours or anybody else's.

• To provide what you asked for (contract). This covers keeping your progress, your account, signing you in, translations, payments and Pro access.
• Legitimate interests. This covers working out which lessons help and which do not, fixing problems, keeping the service secure, and stopping abuse such as overuse of the translator. We use the minimum we need for these, and none of it is used for advertising.
• Your consent. This covers your Legend answers, notifications, and emails about new drops. You can withdraw consent at any time. To remove your Legend answers, use “Start again”, close your account, or email us. Turn notifications off in your phone's settings. Untick the email box in your account.
• Legal obligation. We keep payment records where tax law requires it.

We do not sell your data or share it for advertising. These companies process it on our behalf, only to run DUB:

• Vercel: hosts the app and stores files.
• Our database provider: stores accounts and learning records.
• Anthropic: writes translations and reads menu photos.
• Stripe: takes payments for Pro on the web.
• Resend: sends sign-in emails.

Your browser maker (for example Apple or Google) delivers notifications and may process speech recognition; it does so under its own privacy policy. If you get DUB from Apple's App Store, Apple also handles the download and any purchase made through Apple, under Apple's privacy policy.

Some of these companies are based in, or store data in, the United States. Where data leaves the UK or the European Economic Area, it is protected by the safeguards the law requires, such as adequacy decisions or standard contractual clauses.

• Sign-in links stop working after 20 minutes.
• Signed-in sessions end after 90 days.
• Everything else we keep while you use DUB, until you close your account or ask us to delete it. There is currently no automatic time limit. That includes the record of sign-in link requests: your email address and the IP address each request came from.
• When you close your account, what remains is anonymous: which lessons people found hard, and how long they took. Nothing in it identifies you (see the next section).

If you want anything deleted sooner, or anything the close-account button does not cover, email sambrownfield3@gmail.com and we will do it.

You can close your account yourself, inside the app:

• Open DUB and go to your Account page.
• Scroll to the bottom and tap “Close my account”.
• Type your email address to confirm, and tap CLOSE MY ACCOUNT.

If you pay for Pro, cancel it first, using MANAGE BILLING on the same page. Closing your account does not cancel a Stripe subscription by itself.

When you close your account:

• We delete your sessions, notification sign-ups, share cards, any codes you redeemed, and any waitlist entry under your email.
• We remove your Legend, your name and your profile from your learning record, and detach that record from you.
• We replace your email address with a meaningless placeholder.
• The app clears its copy on your phone.

What stays is anonymous learning data: which lines were hard and where people stopped. Some records are not yet removed automatically when you close your account:

• your translator history and searches
• sign-in link requests
• your payment records with Stripe
• any email address you typed into a feedback message

Email sambrownfield3@gmail.com from the address on your account and we will delete these too, apart from payment records that the law requires us to keep.

Without an account, “Start again” (linked from the Account page) deletes this device's learning record from our server and forgets the device. For anything else tied to your device, email us.

Under UK and EU data protection law you can:

• get a copy of your data: DOWNLOAD MY DATA on your Account page gives you a file, and we will send you anything it does not include if you ask
• have it corrected
• have it deleted
• restrict or object to how we use it
• take it elsewhere
• withdraw consent at any time

Email sambrownfield3@gmail.com. We will answer within one month. If you are unhappy with how we have handled your data, you can complain to the UK Information Commissioner's Office (ico.org.uk) or to the data protection authority in the country where you live.

DUB is made for adults who are travelling or living abroad. It is not aimed at children, and we do not knowingly collect data from anyone under 13. If you think a child has given us their details, email sambrownfield3@gmail.com and we will delete them.

The Legend can ask about your own children. Those answers are optional, can be skipped, and are removed if you close your account.

Sign-in links and session codes are stored only in scrambled (hashed) form, so a copy of our database could not be used to sign in as you. Cookies cannot be read by scripts on the page. Stored files are private.

If what we collect or how we use it changes, this page changes with it and the date at the top moves.

Questions, requests or complaints: sambrownfield3@gmail.com. There is more help on the support page, and the rules of use are in the terms.