What data a retired pack can hold
A battery management system records voltages, temperatures, charge and discharge history, fault codes and, often, timestamps. On its own that information is largely technical, but when combined with a vehicle identification number, a fleet assignment or telematics logs it can reveal where and when a vehicle was used and by whom. Connected vehicles may also store data in separate control units or gateways that remain attached to the pack when it is removed.
This data is genuinely valuable at end of life. It helps graders understand how a pack was used, speeds up state of health assessment and supports warranty claims and failure analysis. The challenge is to preserve the useful technical history while removing, anonymising or otherwise protecting anything that identifies individuals or exposes commercially sensitive details of how a fleet operates, such as routes, depots or customer locations.
Legal obligations
Data protection frameworks such as the EU General Data Protection Regulation, India's Digital Personal Data Protection Act 2023 and various state privacy laws in the United States can apply wherever retained data relates to identifiable individuals. In most cases the fleet owner remains responsible for how that data is handled, even after the hardware has been passed to a logistics provider or recycler, unless a contract clearly allocates specific responsibilities to another party.
The EU battery passport adds a further layer. It requires defined information about relevant batteries to be recorded and made accessible to specified parties, while personal data protections continue to apply in parallel. Operators should distinguish carefully between battery performance and composition data that must be retained or shared under regulation, and personal or operational data that should be minimised, restricted or removed before the battery leaves their control.
A practical retirement policy
A good policy defines what data is extracted before retirement, where it is stored, who can access it and how long it is kept. It then states whether onboard data is wiped, overwritten or retained, and how that step is verified and recorded. Contracts with logistics providers and recyclers should say how any remaining data will be handled, who may access it and how it will be destroyed once it is no longer needed.
Recyclers can support this by accepting anonymised performance exports rather than raw logs, and by recording at intake that the agreed data-handling steps were completed for each serial number. The result is a clean handover: graders receive the technical history they need, and the fleet owner holds evidence that personal and commercially sensitive data was protected throughout the retirement process.
- Export technical history before retirement
- Remove or anonymise identifiers where possible
- Record the wipe or retention decision per serial number
- Include data-handling terms in recycling contracts
