nobody, is the answer, and here's why that's unusual
A car's diagnostic port is chattier than people realise: the VIN identifies the vehicle uniquely, fault codes describe its condition, and live data can describe your driving. The OBD2 app market has noticed. Plenty of dongles and companion apps stream this to servers by design, and the data flows onward to insurers, fleet analytics, and the used-car pricing industry. It's a real market, and you're the product in it.
This page is the other thing. The browser opens a direct line to the adapter — a serial port over USB, or a Bluetooth LE characteristic — sends the standard commands, and decodes the replies with JavaScript that ships in the page. The site is flat files on a CDN; there is no server-side application, no telemetry endpoint, no account. Your VIN goes to your screen. Full stop.
The proof, which suits this tool especially: car parks have terrible signal. Load the page at home, walk to the car with no connection at all, and everything works — connect, read codes, watch gauges. A tool that phones home cannot do that; this one is built to be used exactly there.
Kept: nothing. No storage, no history — close the tab and the session is gone. Note your codes down yourself; that's deliberate, since the clear button warns you they're your only record.
Counted: no analytics, no ad code, no cookies from this site. The typeface used to be the one asterisk — a request to Google Fonts on each first visit — and now it isn't: it's served from here, same as everything else. Hosting shows plain visit numbers. Which car you drive and what's wrong with it is between you, your mechanic, and the ten-dollar dongle.
questions → front desk · reviewed 21 jul 2026