Privacy

One cookie, named parva_session. It is set when you sign in and cleared when you sign out, and it holds nothing but the secret that identifies your session. It is first-party, httpOnly — so no script on the page can read it — and sameSite=lax, so it is not sent along with requests coming from other sites. That is the only cookie Parva sets. Opening a book sets none at all.

Your browser also keeps some things on the device itself: how you like a page to look — face, size, spacing, margin, tone — the place you stopped in each book, a cached index for EPUBs so they reopen instantly, and, only if you ask for it, a whole book saved for offline reading. Those sit in this site’s local storage and in IndexedDB, under keys beginning parva., and are never sent anywhere.

When you are signed in, the things you asked to be remembered are stored against your account instead: your place in each book, your bookmarks, your highlights, your favourites, and which days you read. That is what signing in is for. Those rows are written so that only your own session can read them.

No analytics. No tracking pixels, no fingerprinting, no advertising, no third-party cookies, and nothing sold or shared with anyone. Nothing is fetched from another company’s servers while you read — the typefaces and icons ship with the app.

Each book carries a running total of how many times it has been opened, which is what the “Most read” sort uses. That number lives on the book and is not connected to any reader.

One list, of four columns: your name, your email address, when you were last seen, and when you first signed in. That is the whole of it. Reading is open to everyone, so most visitors never appear on that list at all.

It shows nothing about what you read. Positions, bookmarks and highlights are written for your session only, and the readers screen deliberately asks for none of them — putting reading history on an administrator’s desk would make this a surveillance tool instead of a catalogue. The rest of the admin area handles books, covers and read counts.

It happens only if you choose it. Selecting “Continue with Google” hands you to Google, which asks whether you want to sign in to this app. Parva never sees your Google password, and if you close that page or refuse, nothing is created and nothing is stored.

If you agree, Google passes your name and email address to Appwrite, which is where accounts for this app live. Parva copies those two fields into its own record so an administrator can see who has signed in. Your profile picture is not fetched — the initials you see in the header are drawn from your name.

Signing out clears the cookie. Clearing this site’s data in your browser removes everything held on the device: reading settings, saved positions, cached EPUB indexes and any offline books. Offline copies can also be removed one at a time, from a book’s page or from reading settings.

There is no button in the app that deletes an account. Removing one, and the rows attached to it, is an administrator’s job in Appwrite.