Privacy policy

Last updated: August 27, 2026

Bookseer has no accounts. We do not know your name, your email address, or your phone number, and we have no way to find out. This page describes the little we do receive, and what we do with it.

What we receive

• Your questionnaire answers and your language. They are what the reading is made from. They travel and are stored without your name or any contact detail. Some questions invite free writing: what you write there is stored as written, so entrust to the questionnaire only what you are willing to entrust.
• Your subscription's identifier. Every subscription carries an anonymous number from the store it was bought in: on iPhone the App Store's original transaction identifier, on Android the Google Play purchase token. We store a one-way hash of it to enforce the pause between readings and to keep your reading history together, so that your past readings return to you on a new phone after you restore your purchase. Neither store tells us who you are, and payment details never reach us.
• A device check for the free reading. To keep the free first reading to one per device, we have to recognise a device that has already taken it. On iPhone we ask Apple's DeviceCheck service to remember this: Apple stores two bits, and we never see a device identifier. Android has no such service, so the app sends us the identifier the system itself gives it, and we keep only a one-way hash of that, never the identifier.
• A count of visits, on the site and in the app. So we can see where Bookseer loses people, we count arrivals, screens and the questions someone stops at. On the website this is done by Google Analytics: it sets one first-party cookie (_ga) to tell a returning visitor from a new one, and beside it a cookieless counter runs at Cloudflare's edge. In the app it is the same counting, with no advertising identifier. What is counted is events and lengths, never the text of your answers, and never for advertising.
• Crash reports and infrastructure logs. Standard, short-lived technical records kept by our error-reporting and hosting providers.

What we do with it

• Compose your reading. Your answers are sent, without any identifier attached, to the external language-model services that help the Oracle write, under agreements that forbid them to train on this data. The current list of these providers is available on request.
• Keep your history. Delivered readings remain linked to your subscription's hashed number so they survive reinstalls and new devices, for as long as Bookseer exists.
• Improve the Oracle. We reread questionnaires and readings to make future readings better. Whoever does this sees answers and books, never an identity, because none is stored.

What we never do

We do not sell or share your data for advertising. There are no ads, no advertising identifiers, no cross-site tracking, and no data brokers. The counting described above is never joined to your answers, so no profile of you exists anywhere. Nothing leaves our systems except to the service providers described above, each doing its one job.

Deletion

If you want your readings gone, write to us. If you can present your subscription from within the app, we can find your history by its hashed number and delete it; readings that were never linked to a subscription cannot be found by anyone, including us.

Children

Bookseer is not directed at children under 13, and the questionnaire assumes an adult reader's life.

Changes

If this policy changes in a way that matters, the new version will be posted here with a new date. We will not quietly begin doing something this page says we never do.

Contact

Email: hello@bookseer.app

Individual Entrepreneur Nicoleta Climanova
Dostoevskii 16, 20
Bălți, Republic of Moldova