1.Who is responsible
The publisher named in the imprint is the data controller. For any question about your data, or to exercise a right, write to the contact address there.
Version in force since 27 September 2026
What we collect, why, how long we keep it, and how to get it back or have it erased.
The publisher named in the imprint is the data controller. For any question about your data, or to exercise a right, write to the contact address there.
Account: email address, name, country, currency, chosen language, password hash (we never see the password itself), and — if you enable it — a two-factor secret and the list of devices you marked as trusted.
Vehicles: make, model, year, registration plate, VIN if you give one, mileage, purchase date and price, insurance provider, monthly premium and renewal date if you enter them.
Use: fuel and charging receipts (amount, volume, station, date, mileage) and their scanned image, services logged (description, cost, garage, mileage), and the uploaded invoice or photo where you attach one.
Technical: IP address and user agent on sign-in events, kept for security; error reports; the coarse location your browser gives us when you ask for nearby fuel prices, used for that request only and not stored.
We never collect the registered keeper's name or address from a vehicle lookup. Only technical data about the vehicle is kept.
To provide the service — accounts, vehicles, forecast, reminders, exports: performance of our contract with you.
To take payment and prevent fraud: performance of the contract and our legitimate interest.
To keep the service secure — rate limiting, sign-in alerts, audit log of sensitive actions, checking a new password against known breaches: our legitimate interest in protecting your account, and our legal obligation to secure the data.
To send reminders about your vehicle: performance of the contract; you can switch each topic off in Settings → Notifications.
To measure use in aggregate so we can fix what is broken: our legitimate interest. We use no advertising or cross-site tracking.
Account and vehicle data: for as long as your account exists.
After you delete your account: erased within 30 days, except entries we must keep — invoices for accounting (10 years in France, 6 in the UK) and security logs (12 months).
Receipt and invoice images: with the entry they belong to, in encrypted storage.
Sign-in security events: 12 months.
Vehicle lookups are cached for 24 hours to avoid repeating the same request.
Supabase (database, authentication, encrypted file storage) — instance hosted in the EU (Frankfurt).
Vercel (application hosting) — served from the EU region.
Stripe (payments and invoicing) — we never receive your card number.
Google Cloud Vision (reading a receipt or registration document you scan) — the image is sent for recognition and is not used to train their models.
Resend (reminder and security emails), Upstash (rate limiting and lookup cache), Sentry (error reports, with a 10% performance sample).
We also query public authorities when you look up a vehicle — the DVLA and DVSA in the UK, the NHTSA in the US, national fuel-price services in France and Germany. We send them the identifier you typed, nothing about you.
Each of these acts on our instructions under a data-processing agreement. We do not sell your data to anyone.
You can access, correct, export and erase your data, restrict or object to a processing, and withdraw consent where we relied on it.
In the app: Settings → Profile exports everything we hold as a JSON file, and deletes your account. Notification topics are in Settings → Notifications.
You can also write to the contact address in the imprint; we answer within one month. If you are not satisfied you can complain to your supervisory authority — the CNIL in France, the ICO in the UK, or the authority of your country of residence.
Every table is protected by row-level security so one account cannot read another's data. Traffic is HTTPS only, with HSTS and a strict content-security policy. Service records are hash-chained and locked against modification at database level.
Passwords must be at least 10 characters and are checked against the Have I Been Pwned breach corpus using a k-anonymous query — your password never leaves our server. Two-factor authentication is available and recommended.
We alert you by email when we see a sign-in from a device you have not used before.
Only what the service needs to work: your session, your language, and your answer to the cookie banner. No advertising cookie, no third-party tracking pixel. Details are in the cookie policy.
Your data is stored in the European Union. Some processors are based outside it — Google Cloud Vision (US), Stripe (Ireland, with US affiliates), Resend (US), Upstash (US), Sentry (US), Vercel (US, serving from the EU).
These transfers rely on the European Commission's standard contractual clauses and, where applicable, the EU–US and UK–US Data Privacy Framework. Public data we read — MOT history, recalls, fuel prices — is sent an identifier and nothing about you.
The service is for adults. We do not knowingly collect data about anyone under 18; tell us if you believe we have and we will erase it.
We will tell you by email or in the app before a material change takes effect. The date at the top of this page is the version in force.