Last updated 11 November 2026
Booktrace is made by Brian Fisher Apps. This policy applies to the Booktrace apps for iPhone, iPad and Android.
Booktrace has no accounts, no login and no servers of our own. We cannot see who you are, and we do not want to.
Your library, listening sessions, playback speeds, chapter positions, notes, ratings, goals, tags and subscription status are stored locally on your phone. There is no account to sign into and no copy on a server we control, because we do not operate one. Deleting the app removes all of it, permanently and with no way for us to recover it.
When you search for a book, add one, or view an author or narrator, the app sends that query to third-party catalogue services to fetch titles, covers, runtimes, chapter lists, credits and page counts. When you edit a bookshelf, the app also looks up the list prices of the books on it for What It's Worth.
| Service | What it receives |
|---|---|
| Audible / Amazon | Your search text, or the identifier of a book you opened. When you edit a bookshelf, the identifiers of the books on it, or the title and author of a book without one, to look up list prices for What It's Worth. Used for the catalogue, covers, chapters, bibliographies and prices. |
| Audnexus | A book, author or narrator identifier, to fetch credits and biography details. |
| Open Library | The title and author of a print book or ebook in your library, to fetch its page count, or the ISBN from a barcode you scan. |
These requests carry no name, no email, no account and no advertising ID. They are ordinary catalogue lookups, and each provider handles them under its own privacy policy. They are not linked to your analytics ID or to each other.
Booktrace can discuss a book with you without spoiling it past where you have listened. That feature cannot work locally, so when you send a chat message, information leaves your device. This is the most significant disclosure on this page and we would rather be blunt about it.
Requests go to OpenRouter, which routes them to the language model that writes the reply. Each request contains:
It does not contain your name, your email, your device identifier, your analytics ID or your notes. We do not store a copy of your conversations on any server; they are kept on your device. OpenRouter and the model provider process the request under their own terms, which may include retention for a period for abuse monitoring.
If you would rather none of this leave your phone, do not use the chat tab. Every other feature in Booktrace works without it.
On booktrace.app, we ask before loading Google Analytics. If you allow it, Google Analytics records the pages you visit, general device and browser information, referral source, App Store link clicks and use of the audiobook speed calculator. We do not send book titles, listening history, notes, chat messages, names, email addresses or advertising identifiers.
Your choice is stored in your browser so we do not ask on every page. Choosing No thanks prevents the Google Analytics tag from loading. You can reset the choice by clearing site data for booktrace.app. Google processes permitted website analytics under its Privacy Policy. We disable Google signals and ad-personalization signals.
The You tab has a Send feedback form. If you use it, your message, the email address you type (only if you add one), the app version and your device model are sent to us through PostHog, so Brian can read it and reply. Nothing is sent unless you press send. Your email is used only to answer you, and is never added to a mailing list or shared. To have a message deleted, email brian@booktrace.app.
Booktrace records a small number of anonymous events so we can tell which parts of the app are useful and where people get stuck. These are processed by PostHog on servers in the United States.
| What is sent | What is not sent |
|---|---|
|
A random ID generated on first launch Which screen or tab was shown That a session was logged, a book added, a chat opened The title, author and format of each book you add Whether a permission was granted or declined Answers to onboarding questions Paywall and purchase outcomes App version and operating system Crash reports (no personal data) A rough location (country and city) that PostHog estimates from your IP address |
Narrator names, or your ratings of books Anything you typed in chat or in notes (except a chat reply you choose to report) Your listening positions or history Your name, email or phone number (except in feedback you choose to send) Your device ID or advertising ID Your precise location |
The random ID identifies an installation, not a person. It is not derived from anything about you or your device, it is not shared with anyone, and deleting the app destroys it permanently. Reinstalling produces a new one that cannot be connected to the old one.
You can report an AI reply from inside the chat. If you do, the reply, the reason you picked, anything you add and the book's title are sent to us through PostHog so we can read it. Nothing is sent unless you press send.
The camera is only used when you choose to scan a book, and you can decline the permission. Spine and cover scans are read on your phone by Google's ML Kit: the images are not sent to us or to Google. The text read from them is used to search the book catalogues listed above. Barcode scanning uses Google's code scanner in Google Play services, which hands the app only the barcode's number. A spine photo you keep, or a photo you pick as your shelf wallpaper through the system photo picker, is stored on your device and not uploaded.
ML Kit sends Google performance and diagnostic information, such as app version, device information, feature usage and a per-installation identifier, which Google uses to measure and debug the service. It does not include your images or the text read from them.
If you allow notifications, they are scheduled and delivered by your own device. On iPhone, the Live Activity that shows a session on your lock screen runs entirely on your phone. We do not operate a push server and we never receive a record of what you were alerted about or what you were listening to.
On iPhone, subscriptions are sold and processed by Apple through the App Store. On Android, they are sold and processed by Google through Google Play. We use RevenueCat to check whether a subscription is active; it receives an anonymous subscriber ID and the receipt Apple or Google issues, and returns whether the app should be unlocked. We never see your payment details, card number or billing address. Apple's handling of that information is covered by Apple's Privacy Policy, and Google's by Google's Privacy Policy.
Everything the app sends to the services named on this page, and everything those services send back, is encrypted in transit over HTTPS. We do not run servers of our own, so your library, notes and reading history stay in the app's private storage on your device. Analytics and feedback can be read only through our access to PostHog, and only to run and improve Booktrace.
Booktrace is not directed at children under 13, and we do not knowingly collect information from them. Since we collect no personal information from anyone, we hold none belonging to a child.
Depending on where you live, you may have the right to access, correct or delete personal information held about you. In practice we hold none: there is no account to look up and nothing that identifies you. If you want the anonymous usage events from your installation deleted, email us from the support page with roughly when you installed the app and what device you use, and we will find and remove them. Deleting the app also discards the random ID, so nothing new is linked to your old events.
If this policy changes in a way that affects what we collect, we will update the date at the top of this page and describe the change here.
Questions about privacy: brian@booktrace.app