This policy describes the information Booklgy collects, how it is used, and the choices you have. Booklgy is a personal book-library app for iPhone and Android. We try to keep this policy short and honest.
What we collect
When you use Booklgy we store:
- Your email address. Used to sign you in via a one-time code sent to your inbox. It is also saved on your owner entry in your household (see below), where the other members of your household can see it. Booklgy never asks you to create a password.
- Your library data. The books you scan or enter, including title, author, ISBN, format, genre, condition, year, series, optional purchase price, your read / favorite / hated flags, and the date the book was added.
- Household and owner information. The household you create or join, the names of people in your household ("owners"), and an email for each owner. Your own sign-in email is saved on your owner entry automatically when you give your name during household setup; for anyone else it is optional. The app uses it to pick that owner as the default when that person scans.
- Your purchase record, if you buy Booklgy Home. The purchase reference the App Store or Google Play gives the app, which store it came from, your account ID, and the time. We keep it so we can unlock Home, restore it on your other devices, and stop one purchase being used by more than one account.
- Camera access. When you scan a barcode, the live camera feed is processed on-device to read the ISBN digits. Camera frames are never saved on your device or transmitted to any server. On Android, the barcode reader is Google's ML Kit, which sends Google some technical readings (see "Third-party services we use").
We do not collect: your contacts, location, advertising identifiers, device identifiers for tracking, photos beyond the live barcode-scan view, or payment card details. Booklgy runs no analytics of its own. The only usage figures any part of the app sends are those of Google's barcode reader on Android, described below.
How we use your information
- Your email is used to sign you in, and to match you to your owner entry so the app picks you as the owner when you scan. Members of your household can see it on that entry.
- Your library and household data is used to display, sync, and share your books across the devices that are members of your household.
- Your purchase record is used only to unlock and restore Booklgy Home.
- We do not sell or rent your information, and we do not share it with anyone for marketing or advertising.
- We do not use advertising tools, and we don't use your device's advertising ID. We run no analytics of our own. On Android, Google's barcode reader sends Google its own diagnostics; see "Third-party services we use".
Third-party services we use
To resolve a book's title, author, and summary from a scanned ISBN or a manual lookup, Booklgy sends a query to one or more of these public catalog services:
- Google Books API (
googleapis.com/books/v1) - Hardcover (
api.hardcover.app) - Open Library (
openlibrary.org) - Wikipedia (
en.wikipedia.org)
Each query contains only the lookup value (ISBN, title, or author) and public API keys where applicable. A query is about one book at a time, and the app repeats some of them later by itself to fill in a missing summary or cover. These services receive no account email, no other personal information, and nothing else from your library: no owner names, prices, or read / favorite / hated flags.
We also use these services to run Booklgy:
- Supabase (supabase.com) is our backend database and sign-in provider. It stores the data described in "What we collect" above, encrypted in transit (HTTPS) and at rest. See Supabase's policy.
- Resend (resend.com) sends the emails that carry your one-time sign-in code. It receives your email address and the message so it can deliver it. See Resend's policy.
- hCaptcha (hcaptcha.com, run by Intuition Machines, Inc.). Before sending a sign-in code, the app may ask you to complete an hCaptcha check, which tells people apart from automated sign-ups. hCaptcha receives technical information about your device and connection, such as your IP address, and how you interact with the check itself, such as taps. It may also set its own cookie inside that check. See hCaptcha's policy.
- Expo (expo.dev) delivers app updates. When the app starts, it asks Expo's update server whether a newer version is available. That request carries which kind of phone you have (iPhone or Android), the app's version details, and a random code that identifies this installation of the app, not you or your phone. If the update system itself failed the last time the app started, the request also carries a short technical error message. It does not include your email or anything from your library. See Expo's policy.
- Google ML Kit (Android only; developers.google.com/ml-kit) is the barcode reader inside the Android app. It reads the barcode on your phone, and camera pictures never leave it. For Google's own diagnostics and usage analytics, it sends Google technical details: your phone's make, model and system version, the app's name and version, a random code for this installation of the app (not meant to identify you or your phone), how long each reading takes, the picture's size and format, and error codes. It does not include your email or anything from your library. On iPhone the barcode is read by other code, which sends nothing. See Google's ML Kit data page and Google's privacy policy.
- Apple (App Store and TestFlight) and Google (Google Play) distribute the app and handle payment if you buy Booklgy Home. We never see your card or payment details. Each keeps its own record of your purchase under its own policy, and may give us crash diagnostics from people who have chosen to share them in their phone's settings. See Apple's privacy policy and Google's privacy policy.
How your data is stored and secured
- On your device. Library data is stored in a local SQLite database inside the app's private storage, protected by your phone's built-in storage encryption. Your sign-in token is stored in the iOS Keychain on iPhone, or encrypted with the Android Keystore on Android (hardware-backed where available).
- On our backend (Supabase). Library data and household membership are stored in PostgreSQL with Row-Level Security policies that limit each row's visibility and writability to members of the associated household. All connections use HTTPS / TLS.
- No bespoke encryption beyond standard OS and HTTPS facilities. This means the app qualifies for the U.S. export-compliance "exempt" category and does not require an Encryption Registration Number.
Deleting your account
You can delete your Booklgy account in either of two ways:
- In the app: open Settings → Delete Account. This happens immediately and cannot be undone.
- Without the app: email support@geifon.com from the email address you use to sign in to Booklgy, with the subject "Delete my Booklgy account". You don't need to reinstall the app. We'll reply to that address to confirm, then delete the account within 30 days of your request.
What is deleted: your account and the sign-in email it holds, your household membership, your purchase record, and your Booklgy Home unlock. If you are the last member of your household, every book and owner in that household is deleted too, including your owner entry and the email on it.
What is kept:
- If other people are still in your household, the books and owners you added stay in the shared library, because they belong to the household. That includes your own owner entry, with your name and email on it. If you want that removed as well, email us at the address below.
- Copies can remain in our database provider's backups for up to 30 days, after which they are gone.
- Apple or Google keep their own record of your purchase under their own policies.
Booklgy Home is tied to your account. Deleting the account ends Home, and it can't be moved to a new account.
Your other rights and choices
- Exporting your data. Open the app → Settings → Export Library as CSV.
- Backing up your local data. Open the app → Settings → Backup Database.
- Updating or correcting. Add, edit, or remove books, owners, and household members directly in the app.
- Leaving a household. Use Delete Account, or contact us if you need to leave a household without deleting your account.
If you have a request that the app's controls don't cover, email us at the address below.
Children's privacy
Booklgy is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has used the app, email us and we will delete the account.
Changes to this policy
If we change this policy materially we will update the Effective Date above and post a notice within the app. Continued use of the app after such a change indicates acceptance of the updated policy.