ReadglotPrivacy Policy
This policy explains what data the Readglot app (iOS and Android) and the website readglot.com collect, why, who else processes it, and the choices you have. In short: your book files never reach our server; to translate, we send only the words you select with a little surrounding text; we don’t sell your data, show ads or track you across other companies’ apps and websites.
Who we are
Readglot is developed by Fedar Trukhan, an individual developer (“we”, “us”), who is the controller of the personal data described here. Contact: support@readglot.com.
What we collect and why
Your books
Book files you open in Readglot are stored on your device. If you turn on cloud copies, the app copies them to your own iCloud Drive (iOS) or Google Drive (Android, “Readglot” folder, access limited to files the app creates). We have no access to those copies; Apple’s or Google’s terms apply to them. We do not upload book files to our server.
Text you translate
When you ask for a translation, the app sends our server the word or phrase you selected (up to 500 characters), the sentence it’s in and the sentence before it, the book’s language and your native language. When the language of a newly added book is unknown, the app may send up to 2,000 characters of its text once to detect the language. We pass this text to an AI model provider (see “Service providers”) to produce the translation, and we do not keep the text of your request linked to you.
To save money and answer faster, translation results are kept in a shared cache that is not linked to any user or device: entries are looked up by a keyed hash of the request, sentence-level translations expire after 7 days. For each model call we log technical usage data (time, model, token counts, cost, success) linked to your account or app installation — never the text — to enforce daily limits and control costs.
Account (optional)
You can read and translate without an account. If you sign in with Apple or Google to sync between devices, we receive from Apple or Google a unique account identifier and, if provided, your email address (with Apple, possibly a private relay address) and name. We store them to run your account. For Sign in with Apple we also store an encrypted token so we can revoke Apple’s access when you delete your account.
Synced reading data
When you are signed in, we store on our server: your book list (title, author, file name, language, format and a fingerprint of the file used to recognise the same book), your reading position, bookmarks (including the short excerpt and chapter name shown in the bookmark), the words you save to your dictionaries with the sentences they came from, your native and reading languages and your time zone (used for daily limits).
App installation and security
Each installation gets a random anonymous token so the app can use free daily limits without an account. Our server and its web server logs process your IP address to deliver responses, rate-limit and protect the service; IP addresses are not stored in our database. We count phrase translations per day using a keyed hash of the request, not its text.
Subscriptions
Purchases are processed by Apple (App Store) or Google (Google Play); we never see your payment card details. To check and restore subscriptions we use Adapty, which receives purchase and subscription status data, store transaction identifiers, an app-specific profile identifier, basic device data (model, OS and app version, locale) and, if you are signed in, our account identifier. We do not ask Adapty to collect advertising identifiers.
What we don’t collect
No advertising, no advertising identifiers, no third-party analytics or crash-reporting SDKs, no location, contacts, photos or microphone. Pronunciation uses the voices built into your device. The website uses no cookies and no analytics.
Legal bases (EEA, UK and similar laws)
- Performance of a contract — translation, accounts, sync, subscriptions.
- Legitimate interests — security, abuse prevention, rate limits and cost control, keeping the service working.
- Legal obligations — e.g. tax and accounting records related to purchases (kept by Apple/Google).
Service providers
We share data only with providers that process it on our behalf to run Readglot:
| Provider | Purpose | Data |
|---|---|---|
| OpenAI (USA) | Translation and language detection | Selected text with context, languages |
| Anthropic (USA) | Backup translation when OpenAI is unavailable | Same as above |
| Hetzner Online (Germany) | Server hosting | All server-side data above |
| Cloudflare (USA, global) | DNS, website hosting, email forwarding, encrypted database backups | Website requests, support emails, encrypted backups |
| Apple, Google | Sign-in, app stores, payments; your own iCloud Drive / Google Drive | As described in their policies |
| Adapty (USA) | Subscription status and restore | As described under “Subscriptions” |
Under their API terms, OpenAI and Anthropic do not use data we send them to train their models, and keep it only for a limited period (generally up to 30 days) for safety and abuse monitoring. We do not sell or rent personal data, and we do not share it for advertising. We may disclose data if required by law or to protect our rights and users’ safety.
Some providers are outside your country, including the USA. Where required, transfers rely on safeguards such as the European Commission’s Standard Contractual Clauses or an adequacy decision, as offered by each provider.
How long we keep data
- Account and synced reading data — until you delete your account. Deleted books and bookmarks are kept as hidden sync records until the account is deleted.
- Account deletion removes your account, sign-in identities, book list, reading positions, bookmarks and dictionaries from our database immediately. Encrypted backups roll over within about 8 weeks.
- Anonymous installation data — until it is no longer used; it is not linked to you if you never sign in.
- Model usage records (no text) — kept for cost accounting; on account deletion they are unlinked from you.
- Translation cache — not linked to anyone; sentence translations expire after 7 days, phrase counters after 2 days.
- Web server logs with IP addresses — about 2 weeks.
- Support emails — as long as needed to help you, then deleted.
Your choices and rights
- Delete your account in the app: Settings › Account & more › Delete account. Books on your device and in your cloud stay until you remove them. Or see how to request deletion by email.
- Use Readglot without an account; turn off cloud copies of books; sign out at any time.
- Depending on where you live (for example under the GDPR or US state laws) you may have the right to access, correct, delete or export your data, to object to or restrict processing, and to complain to your data protection authority. Write to support@readglot.com; we answer within 30 days. We will not discriminate against you for exercising these rights.
Security
Connections use HTTPS. Tokens are stored as hashes or encrypted; backups are encrypted. No system is perfectly secure, but we limit what we keep in the first place.
Children
Readglot is not directed to children under 13 and we do not knowingly collect their data. If you are under the age required to consent to data processing in your country, use Readglot only with a parent’s or guardian’s permission. If you believe a child has given us personal data, contact us and we will delete it.
Changes
We will update this page when our practices change (for example, if we add server voices) and change the date above. Significant changes will be announced in the app.
Contact
Fedar Trukhan · support@readglot.com