An email address, the passages you bring and everything made from them, and what your reading did. That is all of it.

There is no advertising, no analytics, and no tracking of any kind. Nothing about you is sold, rented, or shared for anybody else’s marketing.

• Your account — an email address, and a password if you set one. Passwords are hashed by our authentication provider and are never visible to us.
• Google, if you sign in with it — your email address and basic profile. Nothing else in your Google account is reachable from here.
• The passages you bring, and everything generated from them: the sentence split, the English translation, the clause pairings, the word timings, the audio files, the pronunciations and explanations you asked for, and the difficulty rating.
• What your reading did — which sentences you have heard, what help you took on each one, and how long you listened. This is what the progress page is made of.
• Your settings — language, theme, colors, book face, text size, playback speeds, pronunciation style.
• What a run cost — tokens, characters and a monthly total, which is what makes a spending limit possible.
• Ordinary server logs kept by our host, including IP address and browser, for security and for finding out why something broke.

A few things stay on your device and never reach us at all: which book you were last reading, and the appearance settings the page uses before the server has answered.

• No analytics, no tracking scripts, no third-party cookies, no advertising network.
• The app sets two cookies: one keeps you signed in, and one remembers whether you read in light or dark so the page opens in it. There is no cookie banner because there is nothing to consent to.
• No payment details: the app takes no payment.
• Nothing is sold or rented, and nothing is shared for cross-context behavioral advertising.

To run the app: to sign you in, to keep your library yours, to generate a book you asked for and play it back, to show your progress, to stop a run spending past its limit, to keep the service secure, and to answer you when you write.

If you are in the UK or the EEA: the lawful bases are performing our contract with you for everything the app does, and our legitimate interest in keeping the service secure and working for the logs and the security checks.

Each does one job, and may not use what it sees for anything else.

• Vercel — Hosting, application delivery, and the gateway model requests travel through. It sees requests, logs, and cookieless page-view counts, and it relays sentences to the model providers below that are reached through its AI Gateway, without keeping them.
• Supabase — Database, authentication, file storage, and account email. It holds everything the app stores.
• OpenAI — Writing stories, text-to-speech, and speech-to-text. The request for a story goes to it and the story comes back; a book that chose its voices sends it each sentence, and a clip whose engine returned no word timings is transcribed by it. Under its API terms, content sent this way is not used to train its models.
• Rime — Text-to-speech in English and Spanish. Each English and Spanish sentence of a book is sent to it and the audio comes back with the timing of every word.
• Inworld — Text-to-speech in thirteen languages and the ones nothing else reads, and speech-to-text. Each sentence in a language it recorded voices for, or in one no engine did, is sent to it and the audio comes back with the timing of every word.
• Microsoft — Text-to-speech in sixty languages (Azure Speech). Each sentence in a language it has a native voice for and the two above do not is sent to it and the audio comes back with the timing of every word.
• Alibaba Cloud — Translation, clause alignment, explanations, and pronunciations (the Qwen models). Sentences of your book are sent to it, through Vercel, and the translation and explanations come back. It is reached on terms under which nothing sent is kept or used for training.
• Inngest — Background job orchestration. It is told which book and which sentences to work on; the text of the book is not sent to it.
• Google — Authentication, if you sign in with Google.

All but one are in the United States, so that is where your information is stored and processed, wherever you use the app from; the one exception processes sentences of your book in Singapore and keeps nothing. The same list is on our subprocessors page.

Beyond those, information is disclosed only where the law requires it, or where it is necessary to protect somebody’s safety or the service itself. If the service ever changes hands, it moves with it, under this policy until you are told otherwise.

• Books stay until you delete them. Deleting puts a book in the trash, where you can bring it back; emptying the trash removes the book and its audio.
• Your reading history and settings stay with the account.
• Deleting your account signs you out at once, stops anything generating, and refuses any further sign-in. It does not yet erase your books: they are kept so an admin can bring the account back. If you want everything erased for good, write to privacy@aloglot.com and we will do it.
• Server logs are kept briefly by our host and then rotate away.

Most of it you can do yourself: your settings and your email address are on the account page, a book can be deleted from your library, and the account can be deleted from settings.

For anything else — a copy of what is held about you, a correction, or complete erasure — write to privacy@aloglot.com. You will get an answer within 30 days.

Depending on where you live you may have particular rights over this information, including to see it, correct it, delete it, take it elsewhere, object to some of its uses, and complain to your data protection authority. Those requests are honoured wherever you are rather than only where the law demands it, and asking never costs you the service.

Everything travels over HTTPS. Every table is guarded by policies the database itself enforces, so a query asking for another account’s books gets nothing back rather than being politely refused by the app. Audio sits in a private store and is reachable only through short-lived signed links minted for you. Passwords are hashed, and are not stored at all for accounts that sign in with Google.

No system is perfectly secure and this policy does not promise one is. If information is ever exposed, you will be told promptly.

The app is not for anybody under 13, and information is not knowingly collected from them. If you believe a child has an account, write to privacy@aloglot.com and it will be removed.

This policy can change. If a change matters, you will be told in the app or by email before it takes effect. The date at the top says when it last changed.

Aloglot, at privacy@aloglot.com. The terms of use are the other half of this.