What Narrandu keeps, and why

What we store

An account is an email address, a password, and a username. The password is stored only as a hash by our authentication provider; we never see it.

Stories you publish — titles, fragments, and who wrote what — are the product itself, visible to other readers by design. Covers you upload are stored as images and shown wherever the story appears.

The text of an unpublished draft never leaves your browser: it is saved locally on your device and reaches our servers only when you publish it.

Cookies

Three, all doing exactly what you asked for: a session cookie that keeps you signed in, a small cookie remembering your light-or-dark choice, and one remembering how you like to read a story (with or without author names).

No analytics, no trackers, no third-party cookies, no ads. That is why there is no consent banner — there is nothing to consent to.

Where it lives

Accounts and stories live with Supabase (authentication and database) in the EU, on AWS eu-west-1. Cover images live on Cloudflare R2, pinned to the EU jurisdiction. The app itself is served by Vercel. Like any hosting providers, they process IP addresses in ordinary server logs.

Nothing is sold, shared, or used for advertising.

Your rights

You can ask what we hold about you, have it corrected, or have your account deleted — one email to the address above is enough.

Published fragments are part of a shared story, like lines in a conversation. Deleting your account removes your profile and authorships; if you also want your fragments gone, say so and we will remove them.

If you believe your data has been mishandled, you can complain to the Romanian supervisory authority (ANSPDCP) — though we would rather hear from you first.