Key facts
- Permissions, retention and data-sharing practices differ between charging providers and jurisdictions.
- A payment receipt and a location history may be personal data when linked to an individual.
- Data minimisation and transparent notices are relevant principles under EU/UK privacy regulation, subject to local law.
Quick answer: You can evaluate a charging app’s privacy before giving it continuous access to your location. Ask whether the app needs a one-time location to show nearby chargers or requires background location to provide a particular feature. The answer depends on the operator; no single permission choice is correct for every service.
The five types of information a charging app may handle
Public charging often involves site and connector selection, payment authorisation, user account details, energy-session history and device permissions. Some apps also store map searches, vehicle identifiers or trip patterns. That information can be sensitive when linked to a person even if no single piece appears revealing on its own.
An eight-question privacy review
- Can I search for a charger without logging in?
- Can I grant location access only while using the app, rather than all the time?
- Does the app clearly explain why it requests precise rather than approximate location?
- Can I pay using a browser, terminal or single session without creating an account?
- What session history is stored, and how long?
- Which payment processors or roaming partners receive information?
- How can I download, correct or delete personal data where the law grants such rights?
- Will account deletion affect legally required invoices, warranty records or outstanding disputes?
Case study: finding a nearby charger
Imagine App A displays a charger list after the user enters a city name. App B asks for always-on precise GPS permission before displaying anything. This hypothetical difference does not by itself prove wrongdoing, but it does reveal a meaningful question: what feature requires the wider permission, and is there an alternative?
EU framework versus local requirements
The European Data Protection Board’s guidance on connected-vehicle data provides a useful reference for location, vehicle and personal data principles. Actual legal obligations depend on the controller, jurisdiction, lawful basis and collection context. A service in another country may not be subject to exactly the same requirements.
Before selling or handing over an EV
Review the vehicle owner’s account and charging-app permissions separately. Removing an app from your phone does not necessarily revoke a vehicle-linked charging contract or erase a remote account. The used-EV digital handover checklist addresses this risk.
Useful record for a privacy request
Note the provider’s legal name, app version, privacy-notice date, country of service, exact type of request and the email or account used. Do not include passwords, private access tokens or full card numbers in a routine support email.
Frequently asked questions
Do all public charging apps need constant GPS tracking?
No blanket technological requirement exists. Features, authentication and user choices vary.
Does uninstalling the app erase charging history?
Not necessarily. Review the provider’s account and retention policy.
Privacy information is general and should be checked against current provider documentation and applicable law.