Jin-vani
Privacy

Privacy policy.

Effective 11 May 2026

Plain English version, no legalese. If something is unclear, open a GitHub issueand I'll clarify both the text and the practice.

Reading is anonymous by default

You can browse every text, every verse, every Foundation article, every Tirthankara page, and use search — without signing in, without an account, without any data leaving your device. This site does not run analytics scripts (no Google Analytics, no tracking pixels, no third-party trackers).

When you sign in

Sign-in is optional and exists only so your reading progress can follow you across devices. If you choose to sign in, here is exactly what is stored:

That is the complete list. No IP addresses are logged separately for analysis. No device fingerprinting. No location tracking. No reading content (other than which verse) is recorded.

Where the data lives

Authentication and per-user data are stored in Supabase, a Postgres-based platform. The database is hosted in the AWS Mumbai (ap-south-1) region. Access is restricted by Row-Level Security policies — meaning your account can only read or write its own rows; no other user can see your data, and no public client query can return another user's rows.

Sign-in emails are sent through Supabase's shared email infrastructure (the sender shows as noreply@mail.app.supabase.io) — they handle delivery, not me.

Browser storage

The site uses your browser's localStorage to remember:

No third-party cookies are set. You can clear this any time from your browser settings — the site continues to work; you just lose those local preferences.

What we do not do

Your rights

You can, at any time:

Children

The site is appropriate for readers of any age, but sign-up is intended for users 13 and over (consistent with Supabase's terms). Anyone younger can use the site fully without signing in.

Changes

If this policy changes materially, the effective date above will update and a note will be added to the site. The commit history of this page is also public on GitHub, so every change is auditable.

Contact

For anything privacy-related, the fastest channel is a GitHub issue. The repository is maintained by the same person who built the site.

This is a personal project, not an institution. The privacy commitments above reflect my own intent and the technical setup. If something I've described here doesn't match what you observe in practice, please tell me — I'll fix the practice or fix the text, whichever is wrong.