The short version
Codex Reader is a reader and player for books you already own. It connects to servers you run or subscribe to, and it can keep your books in Codex Cloud, our optional subscription.
Your library, your bookmarks, and your place in every book are stored on your device. Without Codex Cloud, we do not receive your books, and there is no account with us to create.
If you subscribe to Codex Cloud, the books you upload are stored on our servers so that we can make readalouds from them and send them back to your devices. Your Codex Cloud library is tied to your App Store subscription, not to your name or email address.
Apart from your own servers, these things leave your device: crash reports, purchase records, the books you upload to Codex Cloud, reading activity you send to Hardcover if you link a Hardcover account, and (if you turn it on) reading progress synced through your own iCloud account. Each is described below.
What stays on your device
Your library, your reading and listening progress, bookmarks, highlights, reading lists, shelves, downloaded files, and every setting you choose are held in a database on your device. None of it is transmitted to us. Uninstalling the app deletes it.
Search and browsing inside the app happen locally against that database. We do not receive your searches or a record of what you read.
Features that work on the book itself on your device stay there: matching an audiobook to its ebook with on-device speech recognition, and anything done with Apple's on-device language model. The audio and text they work on are not sent to us.
Your servers and credentials
When you connect a source (Plex, Audiobookshelf, an OPDS catalog, or a Storyteller instance) the address and your credentials are stored in the iOS keychain on your device. They are sent only to that server, to authenticate you and fetch your books.
Those servers are operated by you or by whoever runs them. Their handling of your data is governed by their own policies, not this one.
Codex Cloud
Codex Cloud is an optional subscription. Nothing in this section happens unless you subscribe.
What is uploaded, and why. When you add a book to Codex Cloud, the app uploads the ebook and audiobook files you choose, with the title, author and other details inside them. We store them in your Codex Cloud library, transcribe the audiobook and align it to the ebook text to make a readaloud, and send the books and readalouds back to your devices to read, listen to and download. That is the only thing your books are used for.
Who you are to Codex Cloud. There is no sign-in. To confirm your subscription, the app sends the purchase records Apple signs for this app to our service at api.codexreader.app. From the App Store transaction identifier in them we compute a one-way code, and that code is your Codex Cloud identity: we keep the code, not the identifier. We also keep your plan, its renewal and expiry dates, an identifier the app creates for each device, the app version, and records of the subscription changes Apple and RevenueCat send us. Your IP address is used to limit repeated requests and is not stored with any of this. We never receive your name, your email address, or your Apple Account details. Your library on our servers is under a generated username with no personal details in it. The app shows a support ID on the Codex Cloud screen so that you can refer to your library if you contact us.
Where it is processed, and by whom. The service that checks your subscription and points the app at your library runs on Cloudflare. Your books are stored, transcribed and aligned on Codex Cloud servers that we run, using our own computers and hosting, storage and speech-to-text services we pay for. Those providers handle your files only to run Codex Cloud for us. Your books are kept in a library that only your subscription can open; other subscribers cannot see them. Files travel to and from Codex Cloud over encrypted connections.
What we never do with your books. We do not share your books with anyone, sell them, publish them, or use them to train anything. We do not open, read or listen to them, except when you ask us to help with a problem in your library.
How long it is kept. Your library is kept for as long as your subscription is active. When the subscription ends, your Codex Cloud library is locked: the app can no longer open it, but books you downloaded stay on your device. The library itself is kept so that it comes back if you subscribe again. If we start deleting locked libraries automatically, this policy will say so, with the waiting period, before it begins. Our server backups are replaced on a rolling schedule, so a deleted library also leaves the backups as they are replaced.
Deleting it. You can delete your Codex Cloud account in the app, whether or not you are still subscribed: Settings, Account & Purchases, Delete Account. That permanently deletes the account and every book, audiobook and readaloud stored in Codex Cloud, along with the records tied to it on our servers (your purchase records, devices, sign-in tokens and App Store notifications). We keep only a record that a deletion happened, with no way to tell who it was. Books on your device and on servers you connect are not touched. If you cannot use the app, write to the privacy address below and include the support ID from the Codex Cloud screen. Cancelling the subscription does not delete your library on its own; it locks it. Deleting your account does not cancel your subscription, which you manage in your Apple Account settings.
Hardcover
If you link a Hardcover account, the app signs in on Hardcover's own page and keeps the sign-in in the iOS keychain on your device. Your device then talks to Hardcover directly: it searches Hardcover by title and author to match your books, and sends the reading status, progress, ratings, notes, read dates and list changes you choose to track. If you turn on reading back, it also reads your place from Hardcover.
None of this passes through our servers, and we never see your Hardcover sign-in. What you send is handled under Hardcover's own privacy policy. Unlinking the account in the app stops it and removes the sign-in from your device.
iCloud sync (Codex Premium)
If you buy Codex Premium and enable sync, your reading progress is written to a private database inside your own Apple Account using Apple's CloudKit. It moves between your devices because they share your Apple Account.
That data lives in your iCloud storage. We cannot read it, and it is not sent to any server we operate. Turning sync off stops further writes; deleting the app's iCloud data in iOS Settings removes what is there.
Purchases
Purchases are processed by Apple. We never see your payment details. Codex Premium is a one-time purchase. Codex Cloud is an auto-renewing subscription. Tips in the Tip Jar are one-time purchases that unlock nothing.
To know what you have bought, we use RevenueCat, which records an anonymous identifier it generates for your install along with your purchase history, tips included, and validates your receipt with Apple. For Codex Cloud, our own service also checks the purchase records Apple signs, as described above.
None of this is tied to a name or an email address. Without Codex Cloud there is no account with us at all; with it, the account is the one-way code described above. Purchase records exist to unlock the features you paid for.
Crash reports and diagnostics
Codex Reader uses Sentry to collect crash reports and error diagnostics so that bugs can be found and fixed. A report can include the stack trace, your device model and iOS version, the app version, an install identifier, a trace of the actions leading up to the failure, the structure of the screen at the moment of the error, performance timing from a sample of sessions, and the crash, hang and power reports iOS itself produces through Apple's MetricKit.
Screenshots are deliberately never captured: they would photograph whatever book you are reading. When a network request fails, the report can carry the address it was made to, which for a self-hosted source is the address of your own server.
Some TestFlight beta builds also attach your identity to crash reports. Most builds do not. When a bug needs it, a beta build can be made that does: if you have signed in to Plex, it attaches your Plex account identifier and, where available, your email address and username; if you have not, it attaches the username from a connected Audiobookshelf or OPDS server instead. This is used only to match a crash to the beta tester who reported it. Builds released on the App Store never attach it; the difference is fixed when each build is made, not decided while the app runs.
Crash reports are on by default, and you can turn them off in Settings, About, Send crash reports. Turning them off stops reports right away, including the ones sent before the app has finished starting the next time it opens; turning them back on takes effect the next time the app opens.
Crash data is used to fix the app. It is not sold, not used for advertising, and not used to track you across other apps or websites.
Notifications
Notifications about new books and reading reminders are scheduled on your device from your own library. There is no push server, and no notification data is sent anywhere.
What we never do
We do not sell your data. We do not use it for advertising. We do not track you across other apps or websites, and the app shows no ads. We only receive your books if you upload them to Codex Cloud, and then only to make and return your own readalouds.
Children
Codex Reader is not directed at children under 13, and we do not knowingly collect information from them.
Changes
If this policy changes in a way that affects what leaves your device, the date at the top of this page will change and the revision will be described here.
November 10, 2026: added Codex Cloud (what is uploaded, why, where it is processed, how long it is kept and how to delete it), linked Hardcover accounts, on-device features, and tips. Removed the statements that we never receive your books and that there is no account with us, which are no longer true for Codex Cloud subscribers.
Contact
Questions about this policy, or a request to have data removed: [email protected]. See also the Terms of Use.