Charging data is not owned by whoever’s server it sits on. It is allocated by contract lines among three parties — the asset owner, the operator and the platform provider — across distinct classes: session and energy records, driver accounts and payments, and the site’s fault and configuration history. The platform holds the records physically; the contracts decide who may read, export and delete them, and what is handed over when a party leaves.
Key Takeaways
- Data rights are allocated by contract lines across owner, operator and platform — never by whose server holds the records.
- Write the export right into each contract, against the party who actually holds that class of data.
- Every data class needs an exit test: a complete, openable export proven before the arrangement ends.
- Retention and driver-data duties come from the project’s own legal review — contract lines do not rewrite the law.
The Data-Class Table
| Data class | Who needs it | The contract line to write | The exit test |
|---|---|---|---|
| Session and energy records | The owner (revenue, asset value, incentive evidence) and the operator (tariffs, billing) | Both may read and export the full history at any time, in open formats | A complete history export, delivered and opened, before the outgoing arrangement’s final invoice is paid |
| Driver accounts and payment records | The operator runs the driver relationship; the platform processes it | Whose drivers they are, and what happens to accounts and balances on a platform change | Drivers can still charge the day after migration — tested on the new platform, not promised by the old one |
| Fault and configuration history | The owner and whoever maintains the units (warranty evidence, repeat-fault patterns) | The history follows the asset, per serial number, and is exportable with the session records | A per-serial fault history arrives with the export — a unit’s past is part of its value |
| Site and tariff configuration | The operator sets it; the owner inherits its consequences | Configuration is documented and handed over as data, not rebuilt from screenshots | The incoming operator runs the site from the handover file alone |
| Aggregated and derived reports | Owners reporting upward; operators across sites | Delivered reports stay delivered; the underlying records remain exportable | Last year’s uptime figure can be recomputed from the exported records |
Why the Lines Belong in Three Contracts, Not One
The role split at a site — owner holds the assets, host controls the land, operator runs the service — sits behind our article on how commercial charging stations work; driver data appeared in that model as one seam among four. The owner’s claim on session records sits in the operating agreement, the operator’s working access in the same document. The platform’s duties — export on demand, formats, deletion after exit — sit in the platform contract, which the owner often never sees if the operator signed it. A clause in only one contract leaves a party holding a promise from someone who does not hold the data.
Two duties must not be improvised in these clauses. Personal-data obligations — what may be kept, for how long, what a driver can demand — are set by the law of the project’s jurisdiction; retention and deletion periods belong to the project’s own legal review. Payment records carry their own processor terms. Contract lines allocate rights; they do not rewrite those external duties.
The Hardware Side Contributes the Feed, Not the Filing
What a charger contributes to these records is bounded by its stated protocol — the pairing our OCPP explainer covers. The EV-AC03201T dual-connector AC station and the EV-RHDC30K-L compact DC charger state OCPP 1.6J; the EV-ACS3210E is described as OCPP-ready, a phrase to close in writing. EVDANCE operates no platform and stores no project data: records live in the project’s chosen platform, under its contracts. Questions for a planned site can go to our commercial charging team via contact us.
Frequently Asked Questions
Who owns the session data if the contracts say nothing?
Then the party holding the records holds the leverage, whatever the parties assumed. There is no default worth relying on: the export right, the formats and the exit handover must be written lines, in each contract, against the party who actually holds the data.
What export format should the contract name?
An open, machine-readable one — the test is whether your team can open and recompute the export without the platform’s tools. Name the format and a delivery window, and run a trial export early, while nothing depends on it.
Can the owner take the data when the operator changes?
Only as smoothly as the clauses allow. The owner’s right must be written against the platform as well as the operator: session history, per-serial fault records and configuration, exported complete. Where the operator signed the platform contract alone, the owner’s exit depends on a document it never saw — the gap to close at signing.
Related Reading
- OCPP Explained: What Charge Point Operators Need From EV Charger Hardware
- How Do Commercial EV Charging Stations Work?
- How to Get an EV Charging Station Franchise (and What to Check)
