Privacy policy
Last updated: 21 November 2026
This policy explains what Moji ("the app", "we") collects, why, how long we keep it and what you can do about it. We collect as little as we can: the app never asks for your name, and our own database keeps no name or profile picture, and an email address only if you give one with a support request.
Moji is operated by ALTINSOY COMMERCE LTD, a company registered in England and Wales (company number 16420411), registered office 71-75 Shelton Street, Covent Garden, London WC2H 9JQ, United Kingdom. It is the controller of your personal data. Contact: support@mojitranslator.app.
What stays on your device
These never reach our servers unless you turn on sync:
- Your settings (languages, theme).
- Your library, reading history and reading progress.
- Your bookmarks and browser tabs. The pages you visit in the app's browser load directly from those sites; we do not see your browsing.
- Translated pages, kept on your device up to the storage limit you choose in Settings (the pages of the chapters you opened longest ago go first) or until you clear them. They never leave your device, even with sync on.
The web app and the browser extension
In the Moji web app (mojitranslator.app/app), files you pick are opened and prepared in your browser. Nothing is sent until you tap Translate; then only the prepared page images go to our servers, as from the app. The chapter, its pages and their translations are kept in your browser's storage and deleted 24 hours after the chapter is translated. Your library and reading progress are kept in your browser too, and travel to your other devices only if you turn on sync.
The Moji browser extension works only when you click it on a page. It then reads that page to find the chapter's images, loads those images from the site (after you allow that site once) and hands them to the Moji web app in your browser. It does not watch or report your browsing, and the addresses of the images never reach our servers. The chapter's address, title and the series' cover address go into your library as with the app. The extension has no sign-in of its own: the web app tells it whether you are signed in, with Google or Apple, and your token balance, which it keeps in your browser to show them.
Cookies and analytics on the website
The website and the web app ask before they use analytics cookies. We use them to learn how people find Moji and what they do with it, so we can improve it. They are run for us by PostHog, on servers in the European Union. The mobile apps and the browser extension have no analytics.
- If you accept, a PostHog cookie lets us see one visitor's visits as one journey: the pages you open, the links and buttons you click on our own pages, and these steps in the web app: signing in (with Google or Apple, and whether the account is new), adding a chapter (its number of pages and tokens and its languages), a chapter finishing translation (its number of pages) and a purchase (the product, its price and whether it went through). With them come the page that sent you to us and any campaign tags in the link (without the rest of its address), your browser, device type, screen size, language and an approximate location (country and city) worked out from your IP address.
- If you decline, or your browser sends Global Privacy Control or Do Not Track, nothing is stored on your device for analytics: we only count visits and pages, with an anonymous code PostHog works out on its servers that changes every day, so one day's visits are not linked to the next.
- Never sent: the titles of chapters or series, the sites you translate from, your files, pages, images or texts, your email address or your account id. There are no session recordings and no advertising cookies.
- Change your answer at any time with "Cookie settings" at the bottom of every page, or under Account, Cookies in the web app.
The site also keeps a few things in your browser that it needs to work, which need no consent: your answer to the cookie question, your theme and language, whether you closed the sign-up bar, your sign-in (Firebase) and the web app's chapters and library described above. We keep analytics data only as long as it helps us understand how the site is used, and delete yours on request.
What we process on our servers
Your account
The app starts with an anonymous guest account. If you link a Google or Apple account, Firebase Authentication (run by Google) keeps what it needs to sign you in: that account's email address and, as the provider shares them, its name and profile picture. Our database stores only an internal account id, the sign-in provider, your token balance and your purchase and translation records.
Pages you translate
When you tap Translate, the app (or the web app) sends the images of the pages you are viewing to our servers. We read the text in the speech bubbles, translate it and draw the translation into the page.
Photos you pick from your gallery and PDF files you pick are read on your device: the app sends only the page images, as above. A PDF file itself is never uploaded, and the app sees only the photos you pick, not the rest of your photo library.
- Uploaded pages are deleted as soon as they are processed, at the latest within a day.
- Translated pages are deleted from our servers after 24 hours.
- The text of the bubbles is sent to our translation providers (see below). Images are sent only to Google Cloud Vision for text recognition.
- We do not use your pages to train AI models.
We keep a record of each translation job: number of pages, status, timings, tokens charged and processing cost. It contains no images and no text.
Reported translations
If you report a bad translation and agree to share it, we keep that page's translated text, your comment and, for a page you read on a website, its web address for 30 days to improve the app, then delete them. The report, with its web address and comment, is also emailed to our support inbox. We do not keep the page's image.
Purchases
Purchases in the app are made through the App Store or Google Play and handled by RevenueCat. Purchases on the website are sold by Link (Link, LLC), Stripe's checkout service, which acts as the reseller and handles the payment, the tax and the receipt. It collects your email address, billing country and payment details under its own privacy policy. RevenueCat passes us the purchase and subscription records we need to give you your tokens. We never see your payment details and do not store your email address.
Device checks
To keep modified apps and bots away, every request carries a check from Firebase App Check (Google Play Integrity on Android, Apple App Attest on iOS). To give the free starter tokens only once per device, we use Apple DeviceCheck on iOS, which lets us set a small flag for your device without storing any device identifier ourselves. On Android, after Google Play Integrity confirms the device is genuine, we store a one-way hash of the app's Android device ID (which changes after a factory reset) together with the starter gifts it has used. We cannot turn the hash back into the ID, and we use it for nothing else: no tracking, no ads.
To give the sign-up gift only once per Google or Apple account, we store a one-way hash of the account's Google or Apple user id (a number, not your name or email) once the gift has been given. We cannot turn the hash back into the id and use it for nothing else.
Support requests
Messages you send from the app are linked to your internal account id. If you add a contact email, we use it only to answer you and delete it 90 days after the request is closed.
Crash reports and logs
If the app crashes, Firebase Crashlytics sends a crash report: the error, your device model, operating system and app version, and your internal account id. Our servers log requests with your internal account id only, never your images, text or email. Logs are deleted after 30 days.
Optional sync
If you turn on "Sync across devices" (signed-in accounts only), these are stored on our servers so your other devices can fetch them:
- your bookmarks (page address, title and icon address);
- your library: the series you translated (title, site and cover image address) and their chapters (address, title, number, language and when you last read them);
- your reading progress (chapter address and last page read).
Translated pages are never stored there: on another device a chapter is translated again. Removing a chapter or series from your library removes it from all your devices with sync on, with its translated pages. Turning sync off deletes the copy on our servers; your devices keep their own.
Who processes data for us
| Provider | Purpose | Location |
|---|---|---|
| Google Cloud | Servers, database, storage, logs, task queues | Netherlands, Belgium |
| Google Cloud Vision | Text recognition | Global |
| Google Vertex AI (Gemini) | Backup translation of bubble text | Global |
| Anthropic (Claude) | Translation of bubble text | United States |
| OpenRouter | Backup route to the same translation model when Anthropic is unavailable; it passes the bubble text to Claude hosted by Google, Microsoft Azure, Amazon or Anthropic, and keeps no copy | United States |
| PostHog | Website and web app analytics, only as described under "Cookies and analytics" | European Union (Germany) |
| Google Firebase | Sign-in, App Check, crash reports, this website | Global |
| RevenueCat | Purchases and subscriptions | United States |
| Stripe and Link (Link, LLC) | Reseller and payments for purchases on the website | Global |
| Google (Gmail), name.com | Support email and its forwarding | Global |
| Apple, Google | App stores, payments, device checks | Global |
Where data leaves the European Economic Area or the United Kingdom, our providers protect it with the European Commission's standard contractual clauses or an equivalent safeguard. We do not sell your data, show no ads and do not share it for advertising.
Why we may use your data
- To provide the service you asked for (our contract with you): your account, translations, tokens and purchases, sync and support.
- Our legitimate interests in keeping the service secure and working: device checks against abuse, crash reports and logs; and counting website visits without cookies.
- Legal obligations: purchase and accounting records.
- Your consent: analytics cookies on the website (withdraw it with "Cookie settings"), reported translations and the contact email you add to a support request. You can withdraw it by writing to us.
Your choices and rights
- Delete your account in the app (Settings, Account, Delete account) or on the account deletion page. We delete your sign-in, sync data, reported pages and support requests, and close your purchase profile at RevenueCat. Purchase and translation records are kept without anything that identifies you, as accounting law requires; the stores keep their own invoices. The hashed device ID of an Android device and the hashed Google or Apple user id stay, without any link to the account, so a new account on that device or with that sign-in gets no second starter gift.
- Clear your device data by clearing the cache in Settings or uninstalling the app.
- Depending on where you live (for example under the GDPR, UK GDPR or California law), you can ask to access, correct, export or delete your data, or object to how we use it. Write to us and include the account id shown in the app's Settings. You can also complain to your data protection authority; in the United Kingdom that is the Information Commissioner's Office (ico.org.uk).
Children
The app is for people aged 16 and over, and the app stores rate it for that age, because its browser can open any website. We do not knowingly collect data from anyone younger; if you believe a child has used the app, write to us and we will delete the account.
Changes
When this policy changes, we update the date at the top. If a change is significant, we tell you in the app.