unspent.Start now

Privacy

Last updated: [date].

The short version

We built Unspent to know as little about you as possible. No real name, ever. Your email exists only to send sign-in codes. What you answer in the intake is stored as category codes and figures, never free text. Your card details never touch us. We run no advertising trackers and no analytics cookies. What follows is the long version, because the law rightly requires it.

1. Who is responsible for your data

[Company Name Ltd], registered in England and Wales (company number [00000000]), registered office [address], is the data controller. Contact for anything in this notice: [support@yourdomain]. We are registered with the Information Commissioner's Office (registration [ZA000000]).

2. What we collect, and why

Account: your email address (to send sign-in codes and the rare service notice, such as a price change) and a pseudonymous username. Lawful basis: performance of our contract with you.

Intake and programme data: your quiz answers (stored as fixed category codes only), the figures you enter (spend, duration, goal), which programme you were assigned, task completion, and daily check-ins (held or slipped, plus optional amounts in pence). There is deliberately no free-text field anywhere in the product. Lawful basis: performance of our contract; and because this data can reveal information about your private life, we also ask for your explicit consent at signup, which you can withdraw by deleting your account.

Billing: handled by Stripe. We store your Stripe customer and subscription identifiers and subscription status, never card numbers. Stripe is an independent controller of your payment data; see stripe.com/privacy. Lawful basis: performance of contract and our legal obligations (accounting records).

Technical: our hosting provider processes IP addresses and request logs to serve pages and prevent abuse (legitimate interests: security and fraud prevention). We do not build profiles from them.

3. What we do not do

We do not sell or share your data for advertising. We do not run third-party analytics or tracking pixels. We do not send marketing emails. We do not store journal entries, messages, or any free text from you. The free calculator on this site stores nothing at all: the numbers you type stay in your browser, and a share link contains only the numbers themselves.

4. Cookies

We set only strictly necessary cookies: the session cookies that keep you signed in. Because we set no optional cookies, there is no cookie banner. Your browser's local storage is used on your own device to hold your intake answers before you join and your calculator inputs; that data never leaves your browser except when you submit it to create your programme.

5. Who processes data for us

Supabase (database and authentication), Stripe (payments), [Vercel] (hosting), and [email provider] (delivery of sign-in codes). Each acts under a data processing agreement. Some providers process data in the United States; transfers are protected by the UK Extension to the EU-US Data Privacy Framework or UK International Data Transfer Agreements / standard contractual clauses, as applicable.

6. How long we keep things

Account and programme data: until you delete your account, or after 24 months of continuous inactivity with no active subscription, whichever comes first. Billing records: 6 years, as UK tax law requires (held within Stripe and our accounting records). Server logs: rotated within 30 days.

7. Your rights

You have the right to access, correct, export, restrict, or object to our processing of your data, and to have it deleted. To delete your account and all programme data, email [support@yourdomain] from your sign-in address; we action deletion within 30 days (billing records we must keep by law are retained but no longer linked to a usable account). You can complain to the Information Commissioner's Office at ico.org.uk; we would appreciate the chance to fix things first.

8. Changes

If we change this notice materially, we will email you at least 30 days before the change takes effect. The date below always reflects the current version.