Apogee Privacy Policy
Last updated: 11 November 2026
Apogee is a client app for self-hosted BookOrbit servers. This policy explains how Apogee handles your data.
What we collect
Nothing. The developer of Apogee does not collect, store, sell, or share any personal data, and operates no servers that receive your data.
How your data flows
Apogee talks to the BookOrbit server you choose to connect to, using the address and credentials you enter. Your library, reading and listening progress, reading sessions, highlights, and bookmarks move between your device and that server. Whoever runs that server decides how your data is stored and protected.
Apogee connects to other services only for features you turn on:
- Fanfic Updates. If you sign in to Archive of Our Own (AO3), you do so on AO3's own sign-in page, and Apogee keeps only the session AO3 gives back, on your device. It uses that session to check the works you subscribe to on AO3 and to download new chapters to your BookOrbit server. Signing out of AO3 in Settings removes it. Apogee is not affiliated with AO3 or the Organization for Transformative Works.
- Audiobook notes. Notes you add to audiobooks sync through your own private iCloud database, so they reach your other devices. Apple stores them under your Apple Account. The developer cannot see them.
- CrossPoint e-readers. If you send a book to a CrossPoint device, Apogee sends the file to that device over your local network.
On-device data
Downloaded books, cached covers, and your settings are kept on your device. Apogee also keeps a reading record on your device: your reading and listening positions, highlights (with any notes you add to them), and bookmarks, with the title, authors, and series of each book and your reading status for it, such as finished. The record is filed under your server's address and your user number on that server. It is not a mirror of your library: it can keep highlights and bookmarks after you delete them, and books after they leave your library. It stays after you sign out, and only deleting the app removes it.
Most of the app's data, including your settings, the reading record, and the records the app keeps for diagnostics, is part of your device backup in iCloud or on a computer, and returns if you restore from that backup. Downloaded books and audiobooks, voice audio, and the covers cached for browsing are not included in backups.
Deleting the app removes its data from the device, with one exception. Your server address, sign-in details, and any access tokens or custom headers you entered are kept in the device's keychain, which iOS may keep after the app is deleted. Signing out removes the sign-in details of the user you sign out. If you have saved more than one user, sign out of each. Signing out does not remove access tokens or custom headers. To remove them, sign out first, then clear them under Advanced on the sign-in screen.
Signing out and deleting data
Signing out in Settings removes your server credentials from the device. On BookOrbit 3.0 and later, a password sign-in's session is also ended on the server. Your BookOrbit account belongs to the server you connect to, and whoever runs that server can delete it. Apogee does not create accounts.
Diagnostics you choose to share
The app can build a report to help with a problem. It includes the app build, your iOS version, your device model, your server's BookOrbit version, whether the app is online, the state of syncing and downloads (counts, the numbers of the books and files involved, and recent errors), how much storage the app uses by kind of content and by its largest folders, and similar counts and error states. It classifies the kind of address your server uses, such as "Tailscale" or "public domain". It also includes any crash and hang reports that iOS has given the app, the app's daily performance figures from iOS, a trail of short records of what the app did across recent launches, and the app's own log lines from the last fifteen minutes.
The trail records events with numbers and counts, such as a book's number on your server, and short error messages. It does not record the text of your books. Log lines can include the names of your libraries. On TestFlight builds, a report made from inside a book also names the book, the chapter, and your position in it.
The host name of the server you are signed in to, and of your other saved servers, is removed from the report. An address you typed but did not sign in with may still appear in the log lines.
The app can also show the whole trail, so that you can copy it or share it as a text file, with the same host names removed.
You can read both in the app before you share them. Neither leaves your device unless you copy or share it, apart from your device backup, which includes the records they are built from. The app sends nothing on its own, and the developer receives nothing you have not sent.
Third parties
Apogee contains no third-party analytics, advertising, or tracking SDKs.
Contact
Questions? Email [email protected].
Changes to this policy
- 11 November 2026. Describes the reading record Apogee keeps on your device, which of the app's data is included in device backups, what the keychain keeps after the app is deleted, and everything a diagnostics report contains.
- 25 September 2026. Adds Fanfic Updates (Archive of Our Own), audiobook notes synced through iCloud, sending books to CrossPoint e-readers, and signing out and deleting data.
- 4 August 2026. Adds the diagnostics report and log file that you can choose to share.
- 26 July 2026. Plainer wording. No change to how Apogee handles your data.
- 15 June 2026. First published.