Describe the service people actually use
Start with navigation, diagnostics, remote functions or other specific services, rather than a general statement about connectivity. Map the information involved and the entities responsible. Drivers, passengers and fleet operators may not have the same relationship with the service. Ask privacy and engineering specialists to validate the explanation before it becomes a customer-facing claim.
Separate useful functionality from unnecessary collection
Explain the purpose of each relevant data use and the controls available, based on the company's actual implementation. Do not imply that disabling one feature necessarily disables the entire vehicle unless that is technically accurate. The EDPB connected-vehicle guidance provides a reference for specialist assessment; communications must reflect the assessed service rather than paraphrase legal principles as proof of compliance.
Make the European responsibility visible
Identify the customer contact and escalation route. Explain the roles of the vehicle manufacturer, app provider, distributor and relevant service partners. A driver should not be sent between companies that each say another party is responsible. Where information crosses organisational or geographic boundaries, prepare a clear, validated account instead of relying on a vague claim that data is protected.
Test the explanation with realistic questions
Ask what a second-hand buyer needs to do, what happens when a rental ends and how a shared vehicle is managed. These scenarios expose gaps that a launch presentation may miss. Prepare answers for journalists about the same issues. If a question reveals an operational weakness, fix or escalate the weakness rather than simply finding more reassuring language.
Coordinate controversy response
A public allegation may concern a particular service, a market or the group as a whole. Establish the facts before generalising. Separate confirmed behaviour from speculation and explain the scope of any investigation. Headquarters and European spokespeople should share a dated factsheet, while legal and security specialists determine notification and remediation requirements where applicable.
Keep the promise current
Review public material when software, partners or functionality change. Deliverables include a service-responsibility map, driver FAQ, claim audit and response protocol. Belief System can help make these issues understandable to customers and public audiences. It does not validate data-processing legality or replace the company's privacy and security governance.
Sources and reference points
Reference sources checked on 9 October 2026. The proposed methods and hypothetical situations are Belief System analyses. Your advisers determine the rules applicable to your project.
Continue your preparation
- Launching an EV brand in Europe: why after-sales evidence should lead the Hong Kong investor's story
- A Hong Kong-listed group acquires a European automotive supplier: what should the announcement answer?
- Battery investment in Europe: explaining traceability and responsibility for a Hong Kong-listed group
Discuss your European expansion
Public affairs · Media relations · Reputation & crisis management · GEO & AI visibility