Your data, in plain English
Where it lives, what is kept, what you can do with it yourself, and what we do not do. The privacy policy is the document that binds us; this is the version you can read in five minutes.
Where it lives
- The database, sign-in and files
- Supabase, in its Frankfurt, Germany region. Your records, your login and anything you upload are stored there, in a PostgreSQL database.
- The app itself
- Vercel, which serves the static files that make up the app from a global edge network so pages load fast. Your account data never passes through Vercel: every request that reads or writes it goes straight to Supabase. Like any web host, Vercel sees technical details of each request, such as your IP address.
- Payments
- Stripe. Card numbers, expiry dates and security codes are typed into Stripe’s own fields and go straight to Stripe over an encrypted connection. They never reach our servers and we never see them.
- Transactional email, such as a confirmation or an invoice you send, goes out through a Microsoft 365 business tenant we control.
What is kept
Only what the app needs to do its job.
- Your account
- Your email address and a salted hash of your password. The hashing is done by Supabase; nobody, including us, can read the password back.
- Your records
- The hours you log, your clients and projects, invoices, expenses, mileage, home office figures and the files you attach to them.
- Your plan
- Which plan you are on, the billing cycle and a Stripe customer identifier. Not your card.
- Technical details
- Browser type, device type and IP address, used to rate-limit abuse and to serve the right layout.
What you can do yourself
No email to us, no waiting.
- 01
Export everything
Account Settings has a full JSON export you run yourself, without asking us. It is structured so it can be imported back.
- 02
Delete your account
Account Settings has a Delete account action. It removes your records across every table you own and the login itself, in one step, and it is yours to run at any time.
- 03
What happens after deletion
Your data is gone from the live database at once. Copies held for disaster recovery age out within 30 days. Records the law requires us to keep, such as invoices and payment receipts under UK tax rules, are kept for the required period and no longer.
How it is protected
- Row-level security
- Every table that holds customer data has database policies that let a signed-in account read and write only its own rows. The rule is enforced by the database, not just by the app.
- Encryption in transit
- Every connection between your browser, the app and the database is encrypted.
- Passwords
- Stored only as salted hashes, with a minimum length enforced at the edge and in the app.
- Browser protections
- The site sends security headers that stop it being framed by other sites and limit what scripts can run.
What we do not do
- We do not sell your data, and there are no adverts.
- We do not run third-party analytics or advertising trackers. Public pages keep our own count of visits, which does not keep your IP address in our database; the cookie policy lists exactly what it stores.
- We do not look at your records unless you ask us to, for support, and then only at what you point us to.
- We do not hold your card details. Stripe does, and it is the controller for them.