Your XPeng Logs Every Second of Your Driving. Here's How to Get It Back.

Every few seconds, while the car is awake, it writes a row. Speed. Steering angle. How hard you pressed the accelerator. Motor torque, rotor temperature, the hottest and coldest cell in the pack, charging power, tyre pressures, the odometer. Over a month that is roughly 3.6 million rows — and until recently, none of it was yours to look at.

Since 12 September 2025, the EU Data Act (Regulation 2023/2854) has required makers of connected products to give users access to the data their product generates, in a structured, machine-readable form, and to pass that data to a third party on request. XPeng switched its portal on in September 2026 — about a year after the deadline. It is not pretty and it is not obvious, but it works.

First, two different doors

People conflate these, and it matters.

GDPR Article 15 is about you. Your account, orders, app activity, service records, support tickets — whatever else XPeng holds about you as a person. You ask; they have one month to answer (extendable by two); if they stonewall you, you can complain to a supervisory authority.

The Data Act is about the car. Telemetry, in bulk, in a file you can actually compute over. It also carries the right to hand that data to a third party — and, the part most people miss, the right to take that authorisation back later.

The portal's export is the second one. If what you want is "everything XPeng knows about me", that is a GDPR request, and it goes to the same support address. Something like this is enough:

Subject: GDPR Article 15 access request — VIN <last 6 characters>

I am the registered keeper of VIN <full VIN>. Please provide a copy of all
personal data you hold about me (Article 15 GDPR) — account, app, order,
service and support records — in a commonly used electronic format
(Article 20). Please confirm receipt within one month.

What actually arrives

Log in at xpeng.com/data-act → My Data Center → Download My Vehicle Data. Pick the car, tick the categories (there are seven: vehicle, motion & dynamics, driver controls, electric powertrain, battery & charging, access & security, health & telemetry), choose 7, 14 or 30 days, and submit.

The status moves through Processing → Generating → Download. The newest data available is from yesterday (T-1), the download link expires after seven days, and there is a daily request cap — hit it and the portal tells you to come back tomorrow.

Inside the ZIP are CSVs, named like this:

DA<request-id>_dwd_opp_gdpr_veh_driving_status_di.csv
DA<request-id>_dwd_opp_gdpr_veh_driving_operation_di.csv
DA<request-id>_dwd_opp_gdpr_veh_driving_power_energy_di.csv

Each stream is capped at a million rows, so a busy month spills into _part1, _part2 and so on. Note the file without a suffix is the earliest part, which is the opposite of what you would guess.

And yes — the filenames say gdpr even though this is a Data Act request. Two regimes, one bucket, nobody at XPeng willing to rename anything.

Two things surprise everyone:

• There is no GPS in it. No coordinates, no route, no addresses. Speed and timestamps only. Where you went is the one thing the file cannot tell anyone.
• Your VIN is on every row. It is not anonymous, and it does not become anonymous if you delete a header.

XPeng's own explanatory page still says the format is .xls and the volume is "a few MB". That page is out of date. What you get is CSV, and a 30-day export is closer to 340 MB of text.

The portal also publishes a data dictionary mapping each column to a signal name — esp_vehspd for speed, eps_steeringangle, ldu_accpedalsig for the pedal, bms_celltempmaxnum_gb for the hottest cell — which saves you reverse-engineering a header row.

Enrol: bind the car first

The portal will not serve you until the vehicle is bound to your XPENG account — the same account the app uses. That binding is the enrolment. And the portal is explicit: requests involving vehicle data need the owner's authorisation and consent, and only the owner can authorise anyone else. If the car is leased, registered to a company, or sits on someone else's account, sort that out first.

Then request it, download it, and keep the ZIP somewhere private. It is a diary in spreadsheet form.

Adding a third party — the bit nobody writes about

My Data Center → Manage Third-Party Data Sharing gives you two tabs:

• To third-party — enter the third party's name and email, confirm, done. You get a confirmation email, and the recipient can then pull the data without you forwarding anything.
• To authorized driver — the same idea, for a driver already bound to the car in the XPENG app. Useful for a partner, or a small fleet.

You can review every active authorisation and withdraw it at any time; withdrawal stops future sharing. Only the owner can do either.

If the third party is a person rather than a platform — an accountant, a leasing company, a friend who does data — the portal is not the route. Send a signed letter of authorisation with a copy of your ID to [email protected], and state exactly what they may receive and for how long. Under GDPR you can also mandate someone to act for you (Article 80 covers representation in complaints); under the Data Act you are authorising a recipient. Either way: written, specific, revocable.

For developers, XPeng also runs an enterprise path. The provider is onboarded and receives an appId/appSecret; the owner authorises it; the resulting openId/accessToken/scopeCode are used against the Open API (POST https://open.xpeng.com/open/oauth2/queryData), which kicks off an asynchronous export and returns a short-lived URL. It is a sign-and-poll flow, not a live feed — the ev-monitor project already implements it if you want to see the shape of the thing.

Three ways to read the file

All three do the same first step — drop the ZIP in — and then diverge.

XPengCarData — xpengcardata.com

Hosted, with an account. Charge curves, trip logs, consumption trends, custom charts and a PDF report, plus opt-in community benchmarks that compare your car to other owners. It is the zero-setup option: no local install, works from any device, and your history follows the account. That convenience is the trade-off — it is the one of the three built around an account and a server rather than a browser tab. If you want the file to never leave your machine, use one of the other two.

XPENG Analytics — josepinto1989.github.io/xpeng-analytics

Local, MIT-licensed, and the deepest of the three. Everything happens in the browser tab; nothing is uploaded. Journeys with per-second charts and a synchronised cursor, charging sessions with AC/DC split and estimated losses, battery capacity and relative SOH estimates, tyre pressure trends, g-g diagrams, an actual-use heatmap, and a coverage calendar that shows which days are missing. You can merge several exports into one history, save a portable .xpeng backup, import GPX from your phone to put a route on a trip, and export CSV or a bilingual PDF. If you want to analyse rather than glance, this is the one.

LogbooX — logboox.app

Local too — a worker inside the page parses the file — but built around a different question: what does this file actually say about my life? It opens with a full-screen "wrapped" of the month's findings, then gives you trips, charging sessions, a driving-style view, and a plain account of what the data gives away. Its distinguishing feature is the logbook: since the export has no locations, you type origin, destination and purpose against each trip, and it exports a Fahrtenbuch as CSV, spreadsheet or PDF — genuinely useful for business mileage or a company car. An account is optional; if you take one, it can hold a copy so it outlives the browser, remind you before the 30-day window closes, publish a single trip at a link, and serve a read-only API you can point at Home Assistant.

Which one

	XPengCarData	XPENG Analytics	LogbooX
Runs	hosted, account	browser tab	browser tab (account optional)
Local-first	no	yes	yes
Best at	quick dashboards, comparisons	deep analysis, GPS overlay, PDFs	plain-language readout, logbook, API
Extras	community benchmarks	.xpeng history, GPX, battery/tyre trends	trip links, 30-day reminders, HA API
Cost	free	free, MIT	free

Handle it like a diary

No GPS does not mean anonymous. A month of timestamps, speed and charging power reveals when you leave, when you come home, where you charge, and how you drive when you are late. Add the VIN and it is you.

• Keep the ZIP off shared drives and out of chat.
• Prefer the local tools if you do not want the file on someone else's server; if you use a hosted one, read what it keeps.
• XPeng retains the raw data for up to 30 days, and the portal only ever gives you a rolling window. A month you never requested is gone. Request monthly and keep your own archive — once parsed, a month compresses to 5–15 MB.
• Give third parties the narrowest authorisation that works, and withdraw it when the job is done.

The monthly routine

First of the month: request 30 days, tick everything, download before the link expires, merge into your tool of choice, export the CSV/PDF you actually need, keep the ZIP. Ten minutes.

After a year you have something no car app will ever show you: the history of your own car, on your own disk.

Caveats

The portal is offered where the EU Data Act applies, and XPeng says availability varies by market, model and connected services — owners outside the EU/EEA should not assume it is open to them. Some models have gaps: X9 and P7+ owners reported getting a week when they asked for 30, since fixed for at least one of them. Signal coverage varies by model year and trim. And none of this is legal advice.

---

Disclosure: I maintain XPengCarData, one of the three tools above.