Privacy policy
Last updated2026-10-04
Data controller
Thomas Vienne (EI) — contact@stemmapass.com. Any request about your data can be sent to this address.
What we collect
Account: email address, your name if you provide it, preferred language, units and currency, and a recovery address if you set one.
Vehicles: make, model, year, mileage, track hours, and — if you enter them — the VIN and registration plate.
Servicing: workshop invoices you photograph or type in, parts fitted, amounts. The document itself is archived in a private store, at an unguessable address, and is served to you alone.
We also keep two technical items: a fingerprint of the file (SHA-256), which lets us recognise the same document uploaded twice and confirm it has not changed since it was stored, and the company number printed on the invoice (SIRET, VAT) when the extraction reads one. Each invoice’s recording date is kept separately from the date of the work.
Track sessions: date, circuit, duration, distance, lap count, best lap time and speeds, the weather and notes you enter, and the day’s setup if you record it — tyre pressures, damper clicks, track condition, remarks. If you tell us which columns an unrecognised file uses, you can have them remembered for your next imports: only their headers and roles are kept.
When you import a GPS file, we also derive: the average position of the trace, which identifies the circuit and stays attached to the session; a summary of each lap (time, distance, speeds, number of braking events); how hard you brake and corner, which feeds the wear calculation; and, when the file carries engine data (OBD), peak and average rpm, the share of time at full throttle, and peak coolant and oil temperatures. The file is read on the fly to derive those figures — the trace itself, point by point, is never stored.
Circuit recognition: the average position of an imported session, together with the name you give it, feeds a shared catalogue used to recognise a circuit and suggest its name to other drivers. A name is only suggested once three distinct accounts have named the same place; no account identifier is ever shown, and your contributions are erased with your account.
Payment: StemmaPass never sees or stores card details. Stripe handles them alone and passes us only a customer identifier and the amount paid.
Workshops: if you declare a workshop, we keep its profile — name, company number, address, town, website, phone — and, if you request its verification, what the public register says about that number and the decision taken, with a reason if it is declined. A verified workshop has a public page: its name, town, website, description and the number of services it has confirmed, never a customer, a vehicle or an amount. It can take that page down at any time without losing its verification.
Feedback: when you write to us from the app — a problem, an idea, a compliment — we keep your message and the context attached automatically: the page, the language, the site version, your screen size, your browser and, if there was one, the error shown at the time. A compliment is only quoted on the site if you expressly agreed to it.
Technical errors: when a page fails, we record the error — its message, the page or route concerned, the browser, the site version — and the last account affected, so we can fix it and let you know. Addresses carrying an access token (passport, transfer, account restore) are masked before anything is recorded.
Waiting list: while subscriptions are not yet open, you can leave your email address to be told when they open, without creating an account. We then keep that address, the language of the page and the plan you were interested in — nothing else.
Purposes and legal bases
Running the service — keeping the log, computing wear, producing the passport and the PDF: performance of our contract.
Signing you in and securing access: performance of our contract.
Emailing you about wear and upcoming deadlines: performance of our contract, switchable off in your settings at any time.
Suggesting parts and scoring how complete your logbook is: performance of our contract. To tailor those suggestions we analyse what you declare about your usage — how the vehicle is used, track outings, parts already fitted and their wear. No automated decision follows: a suggestion stays a suggestion, it gates nothing, and you alone decide what you fit.
Measuring site traffic in aggregate: legitimate interest. The measurement is cookieless and cannot identify you.
Handling your feedback and fixing the site’s faults: performance of our contract for the feedback you send us; legitimate interest for technical errors recorded automatically, which are used only to repair what does not work.
Measuring how often logbooks are published: legitimate interest. Each time you switch on publication for a logbook, we note the date, the vehicle and your account — nothing of what the page shows, and nothing about who views it. This log is only used to count publications and the accounts that publish; it is shared with no one, and it is erased with your account.
Telling you when subscriptions open, if you left your address for that: consent, given by submitting the form. The address is used for that single message only, and you can withdraw it at any time by writing to contact@stemmapass.com.
Processors and transfers outside the European Union
The service relies on the following providers, acting only on our instructions:
| Provider | Purpose | Outside EU |
|---|---|---|
| Vercel | site hosting, technical logs, document storage (archived invoices, vehicle photos) and cookieless traffic measurement | Yes |
| Neon | database (accounts, vehicles, servicing) | No |
| OpenAI | reading photographed workshop invoices and, on request, suggesting the columns of an unrecognised GPS file | Yes |
| Resend | sending emails (sign-in, alerts) | No |
| Stripe | payments and billing | Yes |
| Cloudflare | domain management and mail forwarding | Yes |
| signing in with a Google account, if you use it | Yes |
Transfers outside the European Union rely on the European Commission’s standard contractual clauses.
One point deserves your attention: when you photograph a workshop invoice, the image is sent to OpenAI to extract the parts. It may contain your name, your registration plate and amounts. You can avoid this by entering the service by hand — the option sits alongside AI extraction everywhere it is offered. If you ask for it when importing an unrecognised GPS file, OpenAI also receives its column headers and their type (number, text, increasing…), with no values and no positions.
The company number read on an invoice is checked against a public register: the Annuaire des entreprises, run by the French administration, or the European Commission’s VIES service for a VAT number. Those registers are not our processors and receive no data about you: only the number of the company that issued the invoice is sent, never your identity, your vehicle or the amounts. The check only says that the company named exists and is still active; it does not attest that it issued the document.
Retention
Your data is kept for as long as your account exists.
Two shorter exceptions: your feedback is erased after twenty-four months, technical errors after ninety days.
A deleted vehicle goes to the bin and stays recoverable for thirty days, after which it is erased along with its history.
The waiting list is temporary: it closes when subscriptions open, and it is erased as soon as the message announcing the opening has gone out. It does not depend on your account: creating or deleting one leaves it unchanged.
Sign-in links expire after fifteen minutes, sessions after thirty days.
Deleting your account opens a thirty-day grace period during which you can still change your mind. After it, your vehicles, invoices, archived documents and sessions are erased for good. Billing records held by Stripe follow their own accounting obligations.
The public passport
The resale passport is published only if you switch it on, and you can switch it off at any time.
While it is on, the public page never shows your name, your email address, the VIN or your invoice amounts. It shows the service history, wear status and track sessions — without their setup, position, lap-by-lap detail or engine data.
The registration plate is the one exception: it is hidden by default and appears only if you choose to show it yourself.
The link carries an unguessable identifier: it is not indexed, but anyone you send it to can read it.
Do not confuse this with handing over a logbook: a transfer gives the buyer the vehicle and its full history — invoices, archived documents and amounts included. The links you had circulated — passport, showcase and card — stop working at that point. Remove anything you would rather not pass on before sending the invitation.
The showcase and the Paddock card
The same switch as the passport also publishes a showcase, meant for showing your vehicle to fellow enthusiasts rather than to a buyer, and a Paddock card, an image to post on a forum or in a story. It is a single decision: switching publication off takes all three down at once.
The showcase shows the vehicle (make, model, variant, year, photo), its mileage, track hours and type of use, the wear parts currently fitted, the best lap on each circuit with its date and top speed, and the number of invoices on file, the date of the oldest and how many a workshop has certified.
It never shows your name, your email address, the VIN, the registration plate, the workshop or any amount — nor the wear of parts, or the setup, position, lap-by-lap detail or engine data of your sessions.
The Paddock card carries the vehicle, up to four best laps with their circuit, track hours and the number of sessions and circuits. It bears a QR code leading to the showcase. When you paste the showcase link into a messaging app or a forum, the card is also what appears as the preview: that service fetches it in order to display it.
One important point: the passport, the showcase and the card rely on the same unguessable identifier. Anyone who gets the showcase link, or scans the card’s QR code, can therefore open the passport too. These pages are not indexed by search engines, but only share the showcase where you would accept the passport being read.
Your rights
You have rights of access, rectification, erasure, restriction, objection and portability. Write to contact@stemmapass.com; we answer within one month.
You may also lodge a complaint with the French data protection authority, the CNIL — www.cnil.fr.
Cookies
StemmaPass sets two cookies, neither of them for advertising: the session cookie, strictly necessary to keep you signed in, and the one remembering the language you picked. Both are exempt from prior consent.
In your account area, a selected copy of your garage and logbooks — wear, latest sessions and invoices, the published passport’s address — is also saved in your browser’s storage so it stays readable offline. It never leaves the device, is read by no one but you, and is erased when you sign out. This storage is strictly necessary for the offline reading you use, and exempt from consent.
Traffic and performance measurement runs on Vercel Web Analytics and Speed Insights: no cookie, no persistent identifier. It counts visits and load times, does not follow you across sites and cannot identify you.
No advertising tracker, no social button and no ad network is loaded.