Privacy & data

What gets collected

• Your email address — it's the account. It's used to sign you in, to send you confirmation and reset codes, and to tell you when an analysis finishes. No marketing, no newsletters, no list-selling.
• The invoice images you upload — up to four pages per invoice, exactly as you shot them.
• The analysis output — the findings, amounts, and totals the reader produces from your invoice, including earlier runs if you re-analyze.
• Contact-form messages — your email, a subject, the message, and a name if you choose to give one.
• A server log line for each page request — the CDN that delivers these pages writes down every request it serves: your IP address, your browser's user-agent string, which page you asked for, the response code, the time, and which network operator you came through. This is the ordinary server log every website has. It is used for exactly two things: counting how many distinct people visit each day, and letting the firewall recognize abuse. It is not tied to your account, not sold, not shared, and never leaves our AWS account. It is deleted automatically after 30 days.

That's the whole list. There is no advertising tracking, no cross-site tracking, no third-party analytics service, and no tracking script of any kind. The visitor count is worked out from those server logs — by counting distinct addresses, on the server, after the fact — not by anything running in your browser and not by following anyone around the internet.

Being straight about the trade: counting visitors at all means keeping IP addresses for a while, and an IP address is personal data. Doing it from the server log rather than a tracking script is the smallest version of that we could find — no cookies, no JavaScript, nothing that follows you off this site, and a 30-day ceiling on how long any of it exists.

How invoice images are processed

The honest version: a photo you upload leaves our servers once — to be read.

To run the audit, your uploaded images are transmitted to a third-party AI processing provider, which reads them and returns the analysis. The image itself is what's sent, exactly as you uploaded it — which is why every upload screen on this site tells you to cover or crop the customer block first: your name, address, phone number, VIN, and invoice number aren't needed to find padding in the pricing, and the cleanest way to keep them out of the pipeline is to never photograph them.

We do not name the provider or the model — that's a deliberate product decision — but what is transmitted, and when, is exactly as described above.

Outside of that analysis step, your images are stored privately in AWS. They are never published, never shown in public case files, and never visible to other users. We don't use your images or analyses to train anything of ours.

What becomes public — and how to say no

Finished analyses join the public case files by default — that's the engine of the site: your case file helps the next person catch the same pattern. What a public case file contains: the vehicle, the findings, the amounts, and the totals. Nothing else.

Opting out is one click, twice over: uncheck the publish box when you upload, or hit "Make private" on any invoice at any time after — the case file leaves the public gallery immediately.

Never public, no matter what: your name, your email and contact details, the invoice photos themselves, your VIN and invoice number, the label you give an invoice (that's just for your own list — public case files are headed by the vehicle), and the dealership's name. Dealerships are identified by brand and metro area at most.

How long things are kept

• Invoices, images, and analyses: kept until you delete them. Nothing expires on its own, and nothing is deleted behind your back.
• Deleting an invoice deletes its uploaded pages and every analysis run on it, including any public case file.
• Deleting your account deletes everything: every invoice, every image, every analysis, and any public case files they produced.
• Contact messages are kept until they're handled, so a conversation can be finished, then closed.
• Server request logs (the IP-address ones above) are the exception to "nothing expires on its own": they are deleted automatically after 30 days, whether anyone asks or not.

Your rights, and the actual buttons

No forms to mail, no thirty-day pledges. The controls are on the site:

• Delete any invoice: Dashboard → Delete on the invoice card. Type DELETE to confirm; it's gone, pages and analyses included.
• Pull a case file from public view: Dashboard → "Make private" on the invoice. Instant.
• Delete your account: Account → Delete account. Removes the account and everything it ever uploaded.
• Everything else — erasure questions, corrections, or anything this page doesn't answer: the contact form. No account needed.

Cookies, local storage, and the one outside request

• No advertising or analytics cookies. None. The site sets no cookies at all.
• No tracking script. There is no analytics JavaScript, no tracking pixel, and no beacon on any page here. Visitor numbers are counted from the server's own request logs — see what gets collected — which is why nothing has to run in your browser to produce them.
• Sign-in tokens live in your browser's localStorage so you stay signed in between visits. Signing out clears them. They never leave your browser except to authenticate your own requests.
• Fonts: these pages load their typefaces from Google Fonts, so your browser makes a request to Google's servers (fonts.googleapis.com and fonts.gstatic.com). Like any web request, Google's servers see your IP address. It is the only third-party request the pages themselves make.

Opinions, not accusations

Every analysis on this site is an AI-generated consumer opinion about line items, comparing the numbers printed on an invoice against published specifications. A flagged line is a question to ask, not a verdict. Dealerships are never named — brand and metro area at most — and no individual employee is ever identified.

Corrections are honored: if a dealership documents that a flagged line was correct, the case file is updated to say so. That policy is the whole reason the case files are worth reading.