Privacy policy

Last updated: September 2026

What we store

• Account code: a random 16-character code used to log in. It is not linked to your name or email.
• Display name: optional, chosen by you, shown next to your reviews.
• Reading data: the books on your shelves, your ratings and the reviews you write.
• Theme preference: dark or light.

What we do not store

• No email addresses, passwords or phone numbers.
• No analytics, advertising or tracking cookies.
• No server-side log of your searches.

Cookies

One essential cookie (session) keeps you signed in for up to seven days. Your cookie choices are kept in your browser's local storage, not on our server.

Third parties

Google reCAPTCHA (optional)

With your consent we load Google reCAPTCHA v3 to protect sign-in and reviews from bots. Google then receives your IP address, browser details and interaction patterns under its privacy policy. You can withdraw consent at any time in cookie settings.

Book catalogues

When you search for a book to add, our server queries Open Library, Google Books, Project Gutenberg and the Internet Archive on your behalf. Your browser never contacts them directly, and only the search text is sent.

Translation

If a book's title or description is in a language other than your browser's, you can ask for a machine translation. Our server sends only that text to MyMemory (translated.net) and caches the result; your browser never contacts them.

Public profiles

Off by default. If you switch it on, your shelves, ratings and reviews are visible at a page whose address contains a random id, not your account code. Switch it off any time.

Your rights

• Access and portability: download everything we hold about you as JSON from your settings page.
• Erasure: delete your account from the settings page. This removes your shelves, ratings and reviews immediately and permanently.
• Withdraw consent: change your cookie choices at any time.

Where data lives

All data is stored on a single server operated by us. Book metadata and cover images are cached locally so they can be shown without further external requests.