Visibility and privacy controls
Share what you choose, with whom you choose
Hub enforces the operator’s visibility choices and never widens them. A location reaches an app only when an explicit rule or a roaming agreement allows it; private and home locations stay hidden unless a specific driver token is allowed.
Visibility rules you can test: the tester shows the party asked about, the rule that decided and the outcome (here: visible, because a roaming agreement is in force). Synthetic demo data.
- Dry run: nothing changes
- Home and private locations stay hidden by default
The challenge
The fear that stops operators connecting
Mining sites, estates, corporate campuses and home chargers must not appear on public maps.
Private sites leaking
A shared network that defaults to “share everything” exposes sites that must stay private.
Precise coordinates
Even a hidden location can leak through logs, exports or error messages.
Changes not propagating
Unpublishing a site does nothing if partners keep their copy.
How it works
The precedence, in order
The first rule that applies decides. No rule means no visibility.
Step 1: Explicit deny
A deny rule for a party, or for everyone, wins over everything.
Step 2: Private and home locations
Shared only with a party holding a token the operator allowed. Nothing else can open them.
Step 3: Explicit allow
An allow rule names a party by country code and party ID, or everyone.
Step 4: Agreement, else deny
A roaming agreement in force makes a public location eligible. Otherwise the default is deny.
Interactive illustration
Data visibility controls
Change the operator’s settings and watch the visibility rules decide.
Will this app see this location?
Change the CPO’s settings and watch Hub’s visibility rules decide, in their fixed order. The first rule that applies decides.
- Explicit deny rule for this appno: continue
- Private or home locationpublic: continue
- Explicit allow rule for this appno: continue
- Roaming agreement in force for Locationsshare
- Defaultnot reached
Shared with the app
The roaming agreement covers Locations, and the location is public.
Illustration of Hub’s visibility precedence. Staff can run the same decision for a real location in the decision tester without changing anything.
Capabilities
Privacy built in
Coordinates protected everywhere
Precise coordinates of private locations are gated in OCPI payloads, logs, exports and screens.
Withdrawals
An app that may no longer see a location receives a withdrawal with coarse coordinates and its EVSEs removed.
Decision tester
Staff can test whether a party may see a location, and why, without changing anything.
Rules scoped to the owner
A policy applies to the operator that owns the location, never to another operator’s location with the same id.
Public data only in the API
The read API and feeds serve only locations published as public.
Retention defaults
Raw OCPI logs are deleted after 90 days and audit records after 7 years, as engineering defaults pending legal sign-off.
In the product
Your own data, and only yours
Each partner sees its parties, deliveries and records, and what needs attention. Captured with synthetic demonstration data.
- Partner isolation: a partner never sees another partner’s data
The partner portal: each partner sees its own data, and only its own. Synthetic demo data.
Questions
Visibility and privacy controls: questions
Does this take care of the Cyber and Data Protection Act for us?
Visibility controls support the data-minimisation principles in the Cyber and Data Protection Act, but no product can make you compliant on its own, and we do not claim any certification.
How quickly does a rule change take effect?
A queued message is re-checked against the rules when it is sent, so a change applies to everything not yet delivered. Apps that may no longer see a location receive a withdrawal. How routing re-checks.
What happens to copies that data customers hold?
Feeds receive a withdrawal when a location stops being public, and the read API stops serving it. How long a data customer may keep copies is set in its data agreement. For data customers.
Can a fleet’s drivers see our private depot?
Yes, if you allow their tokens at that location. Nobody else will see it, even with a roaming agreement in force.
Connect without giving up control
Tell us about your public and private sites. We reply by e-mail.