PeachStamp

Privacy

What we hold, and who else sees it.

Last updated 27 September 2026

A car's registration, its service history and where it has been repaired are personal data, and some of it identifies a valuable object sitting on a driveway. We treat it that way.

The short version

  • Your garage is private unless you deliberately publish it.
  • Anonymous page analytics only. No advertising, no third-party tracking, and no analytics cookies - which is why this site still asks you to accept nothing.
  • Data is stored in the United Kingdom (London region).
  • We never sell your data, and there is nobody to sell it to.

Who is responsible

PeachStamp is the data controller for the information described here. Contact: hello@peachstamp.com. We are registered with the Information Commissioner's Office as a data controller, registration number ZC236246. If you are unhappy with how we handle your data you can complain to the ICO at ico.org.uk, though we would rather you told us first.

If you are signed out, we hold nothing

You can use most of the product without an account. When you do, your garage, records and uploaded files are stored in your own browser and are never sent to us. Clearing your browser data deletes them, and we cannot recover them because we never had them.

What we store when you have an account

  • Account - your email address, and a display name and handle if you choose one. Sign-in is by emailed link; we never store a password.
  • Vehicles - registration, nickname, the dates you owned it, visibility settings.
  • Service records - date, mileage, cost, supplier, and your description of the work.
  • Documents - the invoices and photographs you upload, their fingerprints, and any timestamp obtained for them.
  • Reviews - anything you write about a car you have driven.
  • Custody and handovers - which periods of a vehicle's life belong to which account, so records can pass to a buyer without exposing anything outside the relevant period.

Our lawful basis is performance of the contract between us for everything needed to run your garage, and legitimate interests for keeping the service secure and preventing fraudulent records. Where you publish a garage or hand a vehicle over, that is your instruction.

Other people's details in the paperwork you upload

An invoice names the garage that did the work and, usually, the person who paid for it. When you upload a seller's service history to check a car you are thinking of buying, those details come with it, and the seller has not been asked.

We hold them on the basis of legitimate interests: the seller provided that paperwork so that a buyer could check the car, and reading it for that purpose is exactly what it was given for. What we do with it is narrow. It is used only to produce your summary or report, it is visible only to you, we never publish it, we never contact anyone named in it, and it is never used to build a record of a person across cars.

If you are named on paperwork somebody uploaded and would rather it was not held, email hello@peachstamp.com with the registration. We will remove the documents that identify you within one month, unless the uploader has since become the vehicle's keeper, in which case they are that keeper's own records of their own car and the ordinary rules above apply.

Paperwork uploaded for a car the uploader never adds to their garage is deleted automatically after 90 days, files and all. See “How long we keep it”.

Who else sees it

We use a small number of processors, and no advertising companies.

  • Supabase - database, file storage and authentication, hosted in the UK (London, eu-west-2).
  • Vercel - application hosting, served from London, and the cookieless page analytics described below.
  • Anthropic - when you ask us to read an invoice, or generate a buyer's report, the relevant document contents and vehicle details are sent to Anthropic's API to be processed and returned. This happens only when you trigger it. Anthropic does not use API data to train its models, and holds what is sent for a limited period for abuse monitoring, currently up to 30 days, before deleting it.
  • Resend - sends the sign-in link when you ask for one. They receive your email address and the message itself, and nothing else. Delivery is handled in the EU (Ireland).
  • Stripe - takes the payment when you buy a report. You enter your card details on Stripe's own page, not ours, so we never receive or store them. They receive the registration the report is for and your email address, and send you the receipt.
  • Timestamp authorities (freetsa.org, DigiCert) - see below.
  • DVSA - we request MOT history by registration. We send them a registration; we send them nothing about you.

Timestamping sends a number, not a document

When a document is sealed, the only thing that leaves for a timestamp authority is a 32-byte fingerprint. They never receive the document, its filename, the vehicle, or anything about you - they attest that some fingerprint existed at a time, which is all they need to know.

What becomes public, and only if you choose

Garages are private by default. If you publish one, the page shows the vehicles, their history summary and any reviews you wrote - and you can mask the registration so only part of it is shown. Masking is applied before the data leaves our database, not hidden in the page. We never publish your email address, your documents, or the costs you recorded.

A published garage can be indexed by search engines. Making it private again removes the page, but a search engine may hold a cached copy for a while.

Handing a vehicle to a buyer

A handover gives the buyer the records covering your ownership period only. They do not see your other vehicles, your account, your email address, or anything recorded after the handover date. The link that grants this is unguessable and single-purpose.

Cookies

One cookie, used to keep you signed in. There are no analytics, advertising or tracking cookies, which is why this site does not ask you to accept anything.

Analytics

We count page views using Vercel Web Analytics, so we can see which pages are read and which are ignored. It sets no cookies and does not build a profile of you, follow you between sites, or record anything that identifies you - no name, no email, no IP address stored, no device fingerprint. What we get is a count of visits per page and the rough country and referrer they came from.

We also keep our own count of the steps a visit goes through: a page opened, a registration looked up, a free summary run, a checkout started. It records the registration and what the summary showed, because the only question worth asking before launch is how many people who look up a car go on to buy a report. It stores no IP address, no browser or device details, and nothing that identifies you. For the first page of a visit it also records where the visit came from: a short label such as “instagram” or “google”, and the name of the site that linked here, if there was one. Never the page you were on there, and nothing about your device. The steps of one visit are held together by a random number kept in your browser tab, which is not a cookie, is not derived from anything about you or your device, and is gone when you close the tab. If you arrive on a partner's link, the same tab also remembers which partner, so their discount can be applied when you pay; that too is gone when you close the tab. These records are deleted after 90 days.

This is a deliberate trade. Conventional analytics would tell us far more and would require a cookie, and a cookie for analytics needs your consent - meaning a banner on every first visit. We would rather know less and ask you for nothing.

Buyer's reports

A report you run is stored so it can be read again from its link - a report you cannot get back to is not much use the day after you needed it. The link contains an unguessable id and is the only way to reach it; it is not listed anywhere and search engines are told not to index it. Anyone holding that link can read that report, so treat it as you would the report itself.

If you ask us to email you the link, we send it and do not keep the address. We count how many times a report has been sent, so the feature cannot be used to send mail to strangers, but the addresses themselves are not stored. Building a list pairing email addresses with the registrations of cars people are considering is not something this product needs, so we do not have one.

How long we keep it

Records for a car in your garage stay until you delete them or close your account. When you close it, we delete your account data and files. Two things may persist: records that have been handed to a buyer, which are theirs now and cover their vehicle; and a minimal record of a seal - a fingerprint and a date, with no document - where deleting it would destroy a buyer's ability to verify what they were given.

Paperwork for a car you did not buy is different. Invoices uploaded against a registration that is not in your garage are deleted 90 days after upload, the files and the records together. If you buy the car and add it to your garage inside that time, they are yours and are kept. The report itself, which holds the analysis and not the documents, is unaffected.

Your rights

You can ask for a copy of your data, correct it, delete it, take it elsewhere, or object to how we use it.

Export and deletion are both self-service, under Account. The export is a single file containing everything above, including each document's fingerprint, so a copy stays verifiable long after you have stopped using us. Deleting removes your data and your files outright - we cannot recover any of it afterwards, which is the point.

The one exception is described above: a vehicle you have handed to a buyer keeps its history, with your name removed from it. Everything else goes. For anything the app doesn't cover, email hello@peachstamp.com and we will respond within one month.

Children

The service is not intended for anyone under 18.

Changes

If we change what we collect or who processes it, we will update this page and say so in the app. We will not quietly broaden what we do with data you have already given us.