Privacy Policy

Placeholder. Describe what KDR Leave stores, who else sees it, and how to get it back or delete it — in plain language, and accurately.

What is collected

Account details come from Supabase Auth: an email address and the timestamps of invitation and last sign-in. No password is stored, because there is no password — sign-in is a link emailed to that address. A first name and surname are collected during onboarding and stored in the account’s user metadata.

List everything your own tables hold against a user. Be specific.

What is shared

Name every third party the data reaches and why — the host, the database, the email sender, any analytics. If there is no analytics and nothing is sold, say so plainly; it is the most reassuring sentence on the page.

Where it is stored

Name the provider and the region. A Supabase project is pinned to one region when it is created — say which.

How long it is kept

Until the account is deleted. Deleting an account removes it from Supabase Auth, and every per-user row goes with it through a cascading foreign key.

Exporting and deleting

Both are self-service, from Account Management: an export downloads everything held against the account as JSON, and deletion is immediate and permanent.

Cookies

The only cookies set are the Supabase session cookies that keep you signed in. There are no advertising or analytics cookies. Update this if you add any.

Contact

Questions about any of the above: support@example.com.

Last updated 1 August 2026.