LogbooX

Privacy

Last updated 2 October 2026

LogbooX reads the vehicle data XPeng gives you under the EU Data Act. The reading happens in your browser. An account is optional, and it is the only thing that causes any of your data to reach a server at all.

Who is responsible

Florian Schlittenbauer, at the address given in the imprint, is the controller within the meaning of the GDPR. Contact details are there too.

Without an account

Nothing about your vehicle reaches us. The export is parsed by code running inside the page and kept in your browser's own storage so you can reopen it; removing it is one click, and clearing site data removes everything at once. We never receive it, and there is no endpoint that would accept it.

What does reach our infrastructure is what reaching any website involves: your IP address, the page requested, the time, and your browser's user agent, processed by Cloudflare as part of delivering the site and defending it against attack. The legal basis is our legitimate interest in operating a working service (Art. 6 (1) (f) GDPR).

With an account

An account is an e-mail address. There is no password and no profile.

What we store

  • Your e-mail address, to sign you in and to send the messages you have asked for.
  • Sign-in links, stored only as a hash, valid once and for fifteen minutes. The IP address that asked for one is kept beside it for up to two days, purely to stop the form being used to send mail to other people.
  • Sessions, as a cookie holding a random value and a hash of it here, together with your browser's user-agent string and when the session was last used. Ninety days, renewed while you keep using it.
  • Exports you choose to keep in the account: the compressed signal data, the vehicle identification number and model it carries, and the trips and charging sessions worked out from it, and the time zone your browser was set to when it was copied up. Nothing is copied unless you ask for it, or switch automatic copying on.
  • Logbook entries you write against trips — where you went, why, and any comment — once you are signed in.
  • API tokens you create, stored as hashes.
  • Shared links and leaderboard places you create, described below. A shared link also keeps its time zone and a count of how often it has been opened, and nothing about who opened it.

Where it is stored

On Cloudflare's infrastructure: the database and the object storage are both Cloudflare services, created in Cloudflare's EU jurisdiction so that the data is kept in the European Union. Cloudflare Inc. acts as our processor under a data processing agreement incorporating the EU standard contractual clauses.

Legal basis

Performance of the contract you enter into by creating an account (Art. 6 (1) (b) GDPR) for everything that makes the account work. Consent (Art. 6 (1) (a)) for anything published — a shared link, a place on a leaderboard — which is why each one takes a deliberate action and can be withdrawn. Legitimate interest (Art. 6 (1) (f)) for rate limiting and for keeping the service standing up.

How long

Until you delete it. "Delete this account" on the account page removes the rows, everything stored under your account, and the files behind every link you shared. Until then, a revoked link, a revoked token, a declined offer and a place you took down stay as inactive rows. Sign-in links are pruned a day after they expire, sessions once they lapse, and an upload that was never finished is swept up once it is a day old. That clearing-out is one run a day, so each takes up to a day longer.

What is published, and only when you say so

Shared links make one trip, one charging session or a whole export readable by anyone holding the link. They carry the model of the car and never the vehicle identification number. You can revoke one at any time. It stops working within a few minutes, since a copy may be cached for up to five minutes.

Leaderboard places show a name you choose, the model of the car, the figure itself and the numbers beside it, under the month it counts for. They never show your e-mail address, your vehicle identification number, your odometer or the exact time anything happened. Nothing appears there automatically: the app tells you privately when something of yours would rank, and only you can put it up. You can take it down again at any time, including after a month has closed.

Badges. A place in the top three of a settled board has a public badge image at its own address, showing the name you chose, the board, the figure and the period. Anyone who has the address can load it, and it can be embedded on other sites. It disappears within minutes of the place being taken down or the account deleted. A copy that a third-party site has already downloaded is outside our control.

E-mail

We send sign-in links, and — only if you leave them switched on — reminders to request your next export, messages when something of yours would rank on a board or has won a medal, and a summary at the end of a year. Reminders have a switch of their own on the account page. Board and medal messages and the yearly summary share another. Every message other than a sign-in link carries its own unsubscribe link, which does not expire, and a List-Unsubscribe header. There are no tracking pixels and no click tracking; the messages are plain text with a plain HTML twin. Two pictures are loaded from logboox.app when your mail program shows them: our logo, which is the same file for everyone, and, in a message about a medal, the badge, from the same public address as everyone else. We do not record who loads either. Mail is delivered through Cloudflare's e-mail service.

Cookies

Two, both strictly necessary, so there is no consent banner to click through (§ 25 (2) TDDDG):

  • lbx_session — your sign-in, set only once you sign in. HttpOnly, ninety days.
  • sidebar_state — whether the dashboard sidebar is open. A week.

There is no analytics, no advertising, no third-party embed and no external font: everything the page loads comes from this site.

Your rights

  • Access and portability. The API serves everything in your account as JSON, and "Back up" writes every export you keep as a single archive.
  • Rectification. Logbook entries can be edited at any time, and your name once a day.
  • Erasure. "Delete this account" removes everything. Individual exports, links and places can be removed on their own.
  • Objection and restriction, under Art. 21 and Art. 18 GDPR.
  • Complaint. You may complain to a supervisory authority, in particular the one where you live. For this service that is Bayerisches Landesamt für Datenschutzaufsicht.

Write to the address in the imprint to exercise any of these.

Changes

This notice changes when the service does. The date at the top says when it last did; material changes to what an account stores will be said in the app rather than only here.