Privacy

What we collect

• Account data: email address, the name you give us (or “Collector”), and a random public slug.
• Shelf data: the volumes you add, whether you own or want them, reading status, optional notes, and an optional date acquired.
• Sign-in: a one-time code sent to your email, and a session cookie. If you use Sign in with Apple, Apple sends us the identifier they provide.
• Cover photos: the image is sent to the vision model for that request. We store a SHA-256 hash, the model's text, and whether the call succeeded. We do not store the image file.
• MyAnimeList, if you connect it: OAuth tokens encrypted at rest, and the list you choose to import.
• Billing, if you subscribe: Polar is the merchant. We store your plan and when it renews, not your card number.
• Security logs: rate-limit counters, and the usual server logs a host keeps.

Why

We use this data to run the shelf: sign you in, show your books, match a barcode or a cover, import a list you asked us to import, and charge for Pro if you buy it. The legal bases, where a law asks for one, are the contract (providing the account you created), consent (a public shelf, a cover scan, a MyAnimeList connection), and legitimate interests (keeping the service up and blocking abuse). We do not sell personal information, and we do not send promotional email. The messages you get are the code you asked for and mail about the account.

Who else receives it

• Plunk sends the sign-in code. They receive the destination address and the message.
• Polar handles checkout and the customer portal if billing is enabled. They receive the account identity needed to charge you.
• Vercel hosts the app and the AI Gateway. A cover scan sends the image through the Gateway to the vision model named in the app.
• MyAnimeList receives the OAuth exchange when you connect an import. We do not post to your MAL account.
• A public shelf shows your display name, covers, edition names, and counts to anyone with the link. Notes and purchase dates stay off that page.

How long we keep it

Account and shelf data stay until you delete the account. Sign-in codes expire after five minutes. Sessions last 60 days and refresh while you use the app. Rate-limit rows expire with their window. You can export the shelf to CSV first. Deleting the account removes the shelf, the sessions, and connected import tokens. Backups, if the host keeps them, age out on the host's schedule.

Your rights

You can see your shelf in the app, export it, correct an entry, turn the public page off, and delete the account from Settings. Write to hello@hondana.app for anything the app does not do itself, including a copy of account data or a question about a processor.

If you are in the EEA, the UK, or Switzerland, you can also object, restrict processing, and lodge a complaint with your supervisory authority. Where the GDPR or UK GDPR requires a legal basis, the ones above are the ones we rely on.

If you are in Canada, PIPEDA and, in Quebec, Law 25 give you access, correction, and withdrawal of consent. We will explain the decision if we refuse a request. Quebec residents can complain to the Commission d'accès à l'information.

If you are a California resident, the CCPA/CPRA gives you the right to know, delete, and correct personal information, and to opt out of sale or sharing. We do not sell personal information and we do not share it for cross-context behavioural advertising. You will not be discriminated against for exercising these rights. An authorised agent can write to the same email.

CASL: we only email you a code you requested, or a message about the account. We do not add you to a mailing list.

Children

Hondana is not directed at children under 13, and we do not knowingly create accounts for them. That is our COPPA line. Where you live, the age for consenting to an information service may be higher, including 16 in parts of the EEA. Do not sign up if you are under the age required where you live. If you believe a child has an account, email hello@hondana.app and we will delete it.

Cookies

The session cookie is what keeps you signed in. It is set by Better Auth, httpOnly, and refreshed as you use the app. We do not use a third-party advertising cookie. A short signed cache sits next to the session so every page does not re-read the database.

Changes

If this page changes in a way that matters, the date at the top changes with it. Continued use after that date means the new page applies. The terms cover the account itself.