Privacy policy

What we collect

Things you type into a form

This site has three forms: the repair receipt form, the shop listing form, and the contact form. Whatever you enter into one is stored in a private moderation queue that a person reads. Email is optional on the receipt form and used only to resolve a question about your submission. It is required on the contact form because otherwise we cannot reply.

Form submissions are handled by Netlify, our hosting provider, and stored in a database we control. They are not public. Individual repair receipts are never published — only aggregates, with no shop name, no submitter, and no invoice attached.

Cookies and analytics

The only cookies this site is ever involved in are the optional ones set by Google Analytics 4, which counts page views and shows us which pages get read. Analytics runs on Google's servers rather than ours, which makes it a third party to your visit, so it stays off until you press “Accept all cookies” on the notice at the bottom of the page. Ignoring the notice, turning cookies off below, or browsing with JavaScript off all produce the same result: no request is made to Google at all. There is no timer, no scroll-counts-as-yes, and no way to dismiss the notice that quietly records a yes.

If you do accept: we see aggregate traffic — page views, referrers, roughly where in the world visitors are, what device they used. Ad personalisation and Google Signals are switched off in our configuration, so the data cannot be fed into advertising audiences. We do not build profiles of individuals and have no interest in doing so. Google's handling of that data is governed by Google's privacy policy.

Nothing else on this site uses a cookie. Your theme choice and your answer to the cookie notice are kept in your browser's local storage, on your device, and are never sent anywhere — there is no login, no session and no first-party tracking cookie to explain.

If your browser sends a Global Privacy Control signal — or the older Do Not Track signal — we treat that as a no without asking, and any analytics cookie already on your device is deleted.

Advertising

There is none. No page on this site carries an ad unit, no ad network script loads, and no advertising or ad-measurement cookie is set, so there is no ad profile of you being built here and nothing to opt out of. Revenue is paid directory listings and affiliate links, both disclosed on the pages carrying them.

If that ever changes, this section changes first, and it will say which network and what it sets before a single unit ships.

Server logs

Our host records standard request logs — IP address, user agent, page requested, timestamp — as part of serving the site and defending against abuse. We do not use them for analytics.

What we do not do

• No accounts. There is nothing to sign up for, so there are no passwords to leak.
• No selling or renting personal data. Not to advertisers, not to shops, not to lead brokers. We do not sell leads at all — that is the whole business model difference between this site and most of the directories you have used.
• No sharing your details with shops. If you look up a shop and call it, that call is between you and them. We never learn about it.
• No newsletter you did not ask for. An email you gave us for one purpose is not a marketing list.
• No publishing your submission. Receipts become aggregate numbers. Nothing identifying you or the shop is published.
• No tracking before you agree to it. No third-party script, cookie, pixel, fingerprint, or session recording runs on a first visit. See CIPA below for the specifics.

California's wiretap law (CIPA) and what we do about it

California's Invasion of Privacy Act — Penal Code § 630 and the sections that follow — is an all-party consent statute. Most of the recent claims brought against websites under it come down to three provisions, so here is each one and what this site does about it.

• § 631 — reading a communication in transit. The argument is that an embedded third-party script is an uninvited party listening to what passes between you and the site. Our answer is that no third-party script runs before you allow one. There is exactly one that can be allowed, it is named above, and it is off by default.
• § 632 — recording a confidential communication. We run no session replay and no session recording of any kind. Nothing captures your keystrokes, mouse movement, scrolling, or what you type into a field before you submit it. There is no chat widget, no co-browsing tool, and no support tool that watches the page.
• § 638.51 — pen registers and trap-and-trace. This is the one about capturing routing, addressing, and signalling information rather than content. We run no device-fingerprinting script, no visitor-identification or de-anonymisation service, and nothing that resolves your IP address to a company or a person.

Two structural things back that up rather than leaving it as a promise. Every page is served with a Content Security Policy that lists the only outside origins a browser is permitted to contact from this site — everything else is refused by the browser itself, so a pixel added by mistake cannot phone home. And the build fails if a third-party origin appears anywhere in the code that is not declared in the one file that holds that list. A convention gets forgotten; a failing build does not.

Forms are the other place this comes up. What you type into the receipt, listing, and contact forms is posted to this domain and stored in a database we control. Netlify hosts it for us under contract as our service provider — the same relationship as the company that hosts the pages themselves — and no analytics or advertising service is party to the submission or sees any field of it.

How long we keep things

• Approved repair receipts — retained indefinitely as part of the dataset, because a cost trend needs history. Contact details attached to them are removed once the submission has been reviewed and folded into an aggregate.
• Rejected or duplicate submissions — kept with a review note for 12 months so that our own deduplication and rejection decisions are auditable, then deleted.
• Contact messages — kept as long as needed to resolve the matter, and corrections kept as a record of the change.
• Shop submissions — kept for as long as the listing is live, plus a record of the verification calls.

Your choices

Wherever you live, you can ask us what we hold about you, ask for it to be corrected, or ask for it to be deleted, and we will do it. There is no verification hoop and no form — email [YOUR-CONTACT-EMAIL] or use the contact form. Since we have no accounts, in practice this almost always means “delete the submission I sent you”, which we can do immediately.

Residents of California, Colorado, Connecticut, Virginia, and other states with comprehensive privacy laws, and residents of the UK and EEA, have specific statutory rights including access, correction, deletion, and opting out of targeted advertising. We honour all of them for everybody rather than gating them by geography. Targeted advertising is the one right there is nothing to exercise: we do not serve ads, so nobody is targeting you here.

Cookie consent is separate and revocable at any moment, from the cookie preferences box further up this page, which the footer of every page links to and which the cookie notice itself points at. Turning them off is one press, takes effect immediately, and deletes the cookies.

Children

This site is aimed at commercial vehicle operators and repair professionals. We do not knowingly collect anything from anyone under 13. If you believe a child has sent us something, tell us and we will delete it.

Changes

If this policy changes materially, the date at the top changes and the change is described rather than silently swapped in. We are not going to bury a new data practice in a “clarification”.