Most charging contracts state that the operator owns the data. Fewer specify what that ownership entitles them to do, and fewer still are backed by an architecture that makes it exercisable.
Ownership you cannot act on is a clause rather than a property.
What data exists
Contracts frequently address the first two and are silent on the rest. Telemetry and fault history are what make a network diagnosable, and losing them at exit means starting over.
- Session and transaction records, which are the commercial substance.
- Meter readings at whatever granularity was captured.
- Driver and account records, which carry privacy obligations.
- Charger telemetry, faults and status history.
- Configuration and firmware history per unit.
- Derived analytics the platform produced from all of the above.
Ownership means little without export
The practical questions are whether you can export, in what format, how often, covering what history, and whether it is available on demand or by request.
An export that requires a support ticket and arrives as a report rather than as data is not an export. The test is whether another system could ingest it without manual work.
Derived data is the contested part
Analytics, benchmarks and models built from your sessions are frequently claimed by the platform as its own product. That may be reasonable, and it should be explicit rather than discovered.
Where a platform aggregates across customers, establish whether your data contributes, whether it is anonymised, and whether you receive anything in return.
Privacy obligations do not transfer with ownership
Driver records carry legal obligations that persist regardless of contractual ownership. Who is controller, who is processor, and what happens on a deletion request are separate questions from who owns the commercial data.
A contract that assigns ownership without addressing these leaves the obligation unallocated, which is a poor position for both parties.
What makes ownership real
The last one is not strictly about data and is what makes the rest usable. Data you own attached to hardware you cannot move is a partial position.
- A documented export format that another system can consume.
- Coverage of telemetry and fault history, not only sessions.
- Self-service access rather than request-based.
- A defined retention period and access after termination.
- Clarity on derived data and any aggregation across customers.
- The ability to repoint chargers elsewhere without vendor cooperation.
Ask before signing
These questions are inexpensive at procurement and expensive at renewal, when the alternative to accepting terms is a migration. Vendors who answer them clearly are describing a relationship they expect to be scrutinised.