Privacy, supported vehicles, portal quirks and what the numbers mean.
No. The file is parsed and analyzed by JavaScript running in your own browser tab — you can watch the network panel: no request carries your data. That's also why the tool happily works offline once the page is loaded. The optional ads on this site are ordinary web ads and have no access to your file.
Any export from the Volkswagen Group EU Data Act portal (Volkswagen, VW Commercial Vehicles, Audi, Škoda, SEAT, Cupra, Bentley). The battery analysis is calibrated for the MEB EV family — VW ID.3/4/5/7 and ID. Buzz, Cupra Born/Tavascan, Škoda Enyaq/Elroq, Audi Q4 e-tron — which share the same 96-series packs. Other vehicles still get the documented fields, ledgers and the package audit.
It's a known portal quirk: first attempts often come back nearly empty, with only a handful of snapshot fields. A real package with diagnostic history is tens of MB with hundreds of thousands of records. Request the export again — it can take two or more attempts until a complete file arrives.
VW purges the high-frequency diagnostic history after roughly two months. Request a fresh export every ~6 weeks, keep the files, and drop them all here together (or add them later via the small "add export" zone): they are merged and deduplicated into one archive whose history grows deeper than any single package — seasonal consumption and, when battery-side diagnostics are present, battery degradation trends.
Energy figures are estimated from SoC deltas and the measured (or assumed) usable pack capacity — good for trends and comparisons, not for billing. Where the car reported enough battery-current data, trips additionally get an independent ∫I·V estimate shown next to the SoC figure. Charger losses are excluded because the measurement happens at the battery. Known sensor error values (SoC 0, odometer 1048574, 0 K temperatures) are filtered out before anything is computed.
Probably not — and the Package audit tab shows it: in the export this tool was built on, VW delivered 233 of 5,140 documented data point keys, and categories its own Data Dictionary defines (warning lights, diagnostic trouble codes) were missing entirely. Under the EU Data Act (Regulation 2023/2854, Arts. 4–5) and GDPR (Arts. 15/20) you are entitled to the data — the audit tab gives you the concrete field names and numbers to cite through the portal's contact form.
It's the browser version of an open-source Python tool built by reverse-engineering a real ID.7 export against VW's own Data Dictionary V4.0. Undocumented channels (over 90% of the records!) were identified by units, value ranges and cross-checks against documented snapshot fields, and are labelled inferred throughout the dashboard.