Your life, your data. We are careful with both.

§ 01Who we are.

Lifr is built and operated by Alex Hewett, an individual — Lifr has not yet been incorporated as a separate legal entity. Alex is the data controller for information you give us through the Lifr apps, website, and extension.

Alex replies to every privacy email personally.

§ 02What we collect.

We try to collect as little as possible. Here's the whole list:

§ 03Why we collect it.

Two reasons, always:

• To run the product. Sync your tasks between devices, send you the emails you opted into, bill you correctly, answer support.
• To make it better. Understand which features are used, which screens break on which browsers, which categories need more rotation templates.

We do not collect data to profile you, segment you, or target ads. Lifr has no ads, and we commit in writing (below) that it never will.

§ 04Who we share with.

A small number of carefully chosen subprocessors. Each is named, linked, and listed so you can verify:

That's the full list. We do not share data with advertisers, data brokers, or "analytics partners" — because we don't have any.

§ 05How long we keep it.

• Your tasks & account: as long as your account is active.
• After deletion: your account and its data are removed from our live systems.
• Backups: we do not currently run automated backups of your data — we're building this out.
• Billing records: kept for as long as applicable tax law requires.
• Usage & login data: login/location data is kept 90 days, then deleted. Other usage events are anonymized when your account is deleted; no separate fixed retention window applies today.

§ 06Your rights.

We extend full GDPR rights to everyone who uses Lifr, not just EU residents. You can at any time:

• Access — download everything we have about you as a JSON export from Settings → Data.
• Correct — edit your account, tasks, and preferences directly in-app.
• Delete — Settings → Data → Delete my account. Two taps. No retention flow, no "wait, let's talk".
• Port — the JSON export is a standard, documented format you can import elsewhere.
• Object — reply to any email or write to privacy@lifr.global. We reply within 30 days, usually much sooner.

§ 07How we secure it.

Tasks and account data are encrypted in transit (TLS 1.3) and at rest (AES-256). Passwords are hashed with argon2id. Production access is restricted to the founder.

We run a public security contact — security@lifr.global — with a responsible disclosure policy. Valid reports get a response in 48 hours and a bounty between £100–£2,000 depending on severity.

§ 08Cookies & local storage.

Lifr uses a handful of cookies and localStorage items, all first-party, all strictly necessary:

• Session token — so you stay logged in.
• Preferences — sidebar collapsed state, plant background, sort order.
• Cloudflare Web Analytics — a cookieless, privacy-preserving page-view beacon loaded on the marketing site only. No cross-site tracking, no fingerprinting, no persistent identifiers. Data is aggregated and retained by Cloudflare per their privacy policy.

No marketing cookies, no third-party ad trackers. No consent banner is needed because Cloudflare Web Analytics doesn't use cookies or persistent tracking.

§ 09Children.

Lifr is not directed at people under 16. We don't knowingly collect data from anyone under 16. If you believe a child has signed up, email us and we'll delete the account promptly.

§ 10International transfers.

Your data is hosted on Supabase's infrastructure, in the United States. If you're in the EU or UK, this means your data is processed outside your region; by using Lifr you consent to this transfer.

§ 11AI & your tasks.

Lifr does not use your tasks, notes, or reflections to train any AI model — ours or anyone else's. No AI-assisted feature is live in the product today; task matching, scheduling, and suggestions all run on rules inside the app. Claude (Anthropic) is used to help build and maintain Lifr, and for internal tooling — never on your data. If we ever ship a user-facing AI feature, we'll update this section before it goes live, describe exactly what's sent and why, and make it clearly labeled and opt-in.

§ 12Changes to this policy.

When we change anything material, we email every user at least 30 days before the change takes effect, summarize it in the blog, and keep previous versions available on request — email privacy@lifr.global. Minor edits (typos, clarifications) are logged but not emailed.

§ 13Contact & complaints.

Email privacy@lifr.global — Alex answers. Reply time is under 72 hours, usually under 24.

If you're in the UK or EU and we haven't resolved your complaint, you can also contact the Information Commissioner's Office (ico.org.uk) or your local Data Protection Authority. We'd prefer you came to us first, but we respect your right to go straight to them.