Privacy

What Nitor holds, and what it doesn't.

Nitor is a habit tracker in beta, built and run by one person. This page describes what the software actually does with your data today — not a policy template, and not a description of a company that doesn't exist.

What Nitor stores

Four buckets, and they behave differently. It is worth knowing which is which.

Account — Your sign-in details, on the server

Creating an account stores your email address and the credential the authentication provider derives from your password, along with a profile row recording whether you have finished onboarding. This is what lets you sign in from more than one browser.

Habits — Your habits and logs, scoped to you

As per-account storage rolls out, your habits and daily logs are written to database rows tagged with your account id. The database refuses, by policy, to return or modify a row that belongs to a different account — the check is in the database, not only in the app. Signed out, the habits you see are seeded demo data that lives in the page and is never sent anywhere.

Browser — Preferences that never leave your device

Theme, accent, density, reduce-motion, week start, day rollover, quote preferences, the companion's name, and dismissed prompts are kept in your browser's local storage. They never leave your device and do not sync between devices. Clearing your site data clears them.

Quotes — A cached quote pool

Nitor ships with a bundled set of sourced quotations and occasionally tops it up from the Nitor server, caching the result in your browser. The request asks for quotations; it does not carry your habits.

Who else is involved

Nitor is not self-contained. These are the services your data touches, and why.

Hosting — The database and authentication provider

Nitor's accounts and per-account data are held on managed infrastructure operated by Supabase. Supabase stores what is described above because it runs the database Nitor is built on.

Anti-bot — Cloudflare Turnstile on the auth forms

Sign-in, sign-up, and password reset run a Cloudflare Turnstile challenge, so your browser contacts Cloudflare when you use those forms. This exists to keep automated abuse off the sign-up path.

Email — Confirmation and reset email

Confirming an address and resetting a password send you an email. Nitor does not send marketing email, and the newsletter field in the footer is not wired to anything.

The rest of it

No tracking, no advertising, no selling

Nitor contains no analytics scripts, no advertising code, and no third-party tracking pixels. Nobody is buying your habit data: it is not for sale, and the means to sell it has never been built.

Your habits are not read to build a profile of you either. The insights you see are computed for you, from your own data.

Getting your data out

Settings exports everything Nitor holds about your habits as JSON or CSV, whenever you want, without asking anyone. That is deliberate: the ability to leave is what keeps the rest of this honest.

Deleting your account

There is no self-serve delete button in the app yet. Account deletion can be requested by email. When an account is removed, the habit and log rows attached to it are removed with it — the database is configured to cascade the deletion rather than leave orphaned rows behind.

No deletion window is quoted on this page, because it is not something that can be measured yet. Ask, and I will confirm when it is done.

What is not being claimed

This page describes only what can be pointed at in the code and the database configuration. Nitor has not been through an independent privacy or security audit, holds no compliance certification, and publishes no formal retention schedule. If a claim of that kind is not on this page, it is absent because it cannot yet be substantiated — the controls that do exist are itemised on the security page.

Questions

Ask directly: s.ahmad0147@gmail.com.

Beta — read this

Nitor is early software under active development, and how data is stored is itself changing right now as per-account persistence rolls out. Data written during the beta may be affected by that work. Keep an export of anything you would be upset to lose, and expect this page to be updated as the storage changes.