Privacy policy
What Kabook keeps, where it keeps it, and who else sees it.
Effective October 13, 2026. This replaces the previous version.
Who this is from
Kabook is an app made by Gregory Schier, and provided as is. It is free to use, and may offer optional paid features. This policy describes the information it collects and how that information is used. It is not used or shared in any way this page does not describe.
Your library is on your device
The books you add, their statuses, your ratings, notes and lists, and the dates kept for them are stored on your device. Kabook works without an account and without a connection. Signed out, your library stays on your device and is not kept anywhere else.
Deleting the app deletes the library on that device.
If you make an account
An account is optional. It keeps your library the same on every device you sign in on.
- What the account holds: your email address, a password and a display name. The password is kept only as a one-way hash (Argon2id), so it cannot be read back. Signing in gives the device a session token that lasts until you sign out; only a hash of it is kept.
- With Sign in with Apple: instead of a password, the account holds Apple’s identifier for you, the email address Apple shares (which may be a private relay address), the name you give, if any, and a token from Apple, kept only so the sign-in can be revoked when the account is deleted.
- With Continue with Google: instead of a password, the account holds Google’s identifier for you, the email address Google shares, and the name you give, if any.
- Password reset: asking for a reset emails a link to the account’s address. It works once, within an hour; the server keeps only a hash of it until then.
- What syncs: while you are signed in, your library is sent to Kabook’s server and kept there: every book, its status, rating and note, your lists, and the history of changes to them. Each change carries a name for the device that made it, such as ios-3f9a12c0: the kind of device and a few random characters.
- Cover photos: a photo you choose as a book’s cover is kept on your device and, once you are signed in, uploaded to Kabook’s storage, so it shows on every device. It is deleted from the server when you remove or replace the cover, or delete the account.
- Where it is kept: Kabook’s server runs on Railway, with its Postgres database in Railway’s US East region (Virginia, United States). Cover photos are kept in Railway’s storage, also in the United States.
- Email: Kabook sends no email. Your address is how you sign in, and how an account can be told to be yours if you write in.
Signing out keeps your books on that device.
Finding books
When you search for a book, the text you type is sent to Kabook’s own book catalogue, which runs on Railway beside the account server. It is used to answer the search. Search text may be kept on its own, with nothing that identifies you, to improve search. The catalogue is built from Open Library’s public data.
Scanning a barcode reads the book’s ISBN with your device’s camera, on the device. The picture goes nowhere; the ISBN is searched for as if you had typed it.
The app also sends the catalogue the ISBNs of some of your books, to match them to the catalogue’s own (books from the old version of Kabook, for example) and to find other editions’ covers. When you choose another cover from the catalogue, Kabook tells the catalogue which cover you chose for that book, with nothing about you, so the better picture can become the default.
Book covers are loaded from Open Library (covers.openlibrary.org) and, for books that came from the old version of Kabook, from Google Books. Those services see your device’s IP address and which cover was asked for, as any website you visit does. Their own privacy policies apply: the Internet Archive’s, which runs Open Library, and Google’s.
Analytics
Kabook collects analytics about how the app is used, through an analytics service it runs itself. It records what you do in the app, such as the features you use and when it is opened, along with the app version, the type of device and its operating system version, and an approximate location (such as the country) worked out from the IP address. It does not record what is in your library: never book titles, notes, list names or what you search for. This is used to understand and improve Kabook. It is not sold, used for advertising or shared with advertisers.
When you are signed in, the analytics is linked to your account’s identifier, and nothing else about you, such as your name or email address, so Kabook can count people rather than devices and help when you ask for support. When you are not signed in, it uses a random identifier for the app on your device instead. Once your account is deleted, its analytics can no longer be connected to you.
You can turn analytics off in the app’s Settings, with Share usage data. Nothing more is then collected for it, and what has not yet been sent is discarded.
Kabook has no ads, and does not track you across other companies’ apps or websites.
Crash reports
Kabook collects crash reports and diagnostics when something goes wrong, or the app stops responding: what went wrong and where in the app, what the app was doing just before (such as coming to the front and the screens it showed), the app version, the device model, its operating system version and its state (such as free memory and storage), and the time. Each launch is also counted, with a random identifier for the app on your device, so Kabook knows how often it crashes. Crash reports are not linked to your account and carry nothing of your library. They are collected through Sentry, which processes them on Kabook’s behalf, and are used only to find and fix problems.
If you have allowed your iPhone or iPad to share analytics with app developers, Apple may pass on crash reports for Kabook, and Google may do the same for an Android device that shares usage and diagnostics. Those are Apple’s and Google’s settings, under their own policies.
Purchases
If you buy a paid feature, Apple or Google takes the payment, through the App Store or Google Play, under its own terms and privacy policy. Kabook, and a subscription service that keeps track of purchases on its behalf if one is used, receive what was bought, the price, when, whether it is still active, and an identifier to match it to your account or device. They never receive your card details.
Writing to Kabook
Messages you send to Kabook, and the address they come from, are kept to answer them.
This website
This website sets no cookies and has no ads. Railway, which hosts it, sees the requests made to it, as any host does.
What you type into the search on the home page is sent to Kabook’s book catalogue to answer it, and is not kept. The covers it shows load from Open Library, as in the app.
Kabook counts visits to it with its own analytics service, the one the app uses: the pages visited, the site that linked to them, the type of browser and device, an approximate location (such as the country) worked out from the IP address, and a few clicks and taps, such as on the store badges, the theme switch and the phones, and whether the search was used (never what was typed). Nothing is kept on your device for it. A visit is told from another by a code worked out from the IP address and the browser, which changes every day, and the IP address itself is not kept. It is not linked to an account.
The old app and Firebase
The first version of Kabook, from 2020, kept accounts and libraries on Google Firebase and used Google Analytics for Firebase and Firebase Crashlytics. That backend is being retired, and existing accounts are carried across to Kabook’s own server.
- When the new app is installed over the old one, it reads the old app’s sign-in from your device, fetches that account’s books and lists from Firebase once, and adds them to your library.
- If the old account had an email address, the app then sends the old sign-in to Kabook’s server. The server checks it with Google and signs you in to the Kabook account for that email, making one if there is none, and the account keeps a link to the old one. You can then set a password. An old account with no email address comes across to your device only. Nothing is written to Firebase.
- Until the new app replaces it on Google Play, the Android version is still the old app, and the old app’s use of Firebase, Google Analytics for Firebase, Firebase Crashlytics and Google Play Services still applies to it: Google Play Services, Google Analytics for Firebase, Firebase Crashlytics.
Deleting your account
To delete your account, open Settings in the app, choose Delete account and confirm it: with your password, or by signing in with Apple or Google again if that is how you sign in. The account goes for good, with its sessions on every device, the copy of your library kept for it on the server, its cover photos and its history, and its links to Apple, Google and the old app. If it signs in with Apple, Apple is told to revoke the sign-in too. Your books stay on your device.
You can also write to hello@kabook.app from the address on the account to have it deleted, to ask what is kept for it, or for a copy.
How long it is kept
Information is kept only as long as it is needed for the reason it was collected, then deleted or made anonymous. An account, and the copy of its library on the server, are kept until the account is deleted.
Who else sees it
These providers help run Kabook, and process information only to provide their service:
- Railway hosts Kabook’s servers, its database and storage, the book catalogue and this website, in the United States.
- Cloudflare runs this website’s domain name, and may deliver the website.
- Apple runs Sign in with Apple, takes payments in the App Store, and passes on the crash reports you choose to share.
- Google runs Sign in with Google, takes payments on Google Play and handles Kabook’s email. It also runs Firebase, where the old app’s accounts are, and Google Books, which serves the covers of books from the old app.
- Resend sends Kabook’s own email, such as a password reset link, from mail.kabook.app, in the United States.
- Open Library (the Internet Archive) serves book covers, and its public data is what the catalogue is built from.
- Sentry receives the app’s crash reports, as described above, in the United States.
- Kabook’s feedback service receives what you send with the app’s Send feedback form: the message, the email address you give, any screenshots you attach, the app version and the platform, and emails you any reply.
- An analytics, crash-reporting or subscription provider, if Kabook uses one, processes only what this page describes, on Kabook’s behalf.
Apple and Google also distribute the app, under their own privacy policies. Kabook does not sell personal information or share it for advertising. It may disclose information if the law requires it.
Security
Connections to Kabook’s servers are encrypted, and passwords and session tokens are kept only as hashes. No way of sending or storing information over the internet is completely secure, though, so its absolute security cannot be guaranteed.
Links to other sites
This site and the app link to other sites, which are not run by Kabook and have their own privacy policies. It is worth reading them; Kabook has no control over, and takes no responsibility for, their content or what they do.
Children’s privacy
Kabook is not directed to children under 13, and does not knowingly collect personal information from them. If a child under 13 has given Kabook personal information, it will be deleted; if you are a parent or guardian and know of one, please write to hello@kabook.app.
Changes to this policy
This policy may change as Kabook does. A new version is posted on this page, with its date at the top.
Contact
With any questions about this policy, write to hello@kabook.app.