Skip to main content
Getz Hub

Security

How Hub protects partner data

Per-partner credentials, isolation enforced in the database, fail-closed visibility and masked audit records: the controls built into Hub.

Built-in controls

Controls in the product today

  • Per-partner OCPI credentials

    Each partner gets its own tokens through the OCPI handshake. Registration tokens are single use, expire and are stored only as hashes.

  • Speak only for yourself

    A partner may send only as its own parties and push only objects it owns; Hub checks the sender against its token on every call.

  • Database-level isolation

    Every row is scoped to its hub and partner queries are scoped to the partner’s own parties, enforced in the database.

  • Fail-closed visibility

    Nothing is shared without a rule or agreement; private coordinates are protected in payloads, logs, exports and screens.

  • Public partner URLs only

    Partner endpoints must be public HTTPS addresses; Hub follows no redirects to them.

  • Suspension and revocation

    A suspended partner can only manage its credentials; a revoked or deactivated partner is refused, and its history is kept.

  • Hashed, scoped API keys

    Public API keys are hashed, scoped and rate-limited, and shown once when issued.

  • Masked audit records

    Audit entries record what changed, with secrets, tokens and credentials masked.

  • Staff sign-in and roles

    Hub staff sign in through an OpenID Connect identity provider with role-based permissions; drivers never sign in at Hub.

Data protection

Data protection and hosting

How does Hub approach the Cyber and Data Protection Act?

Hub is designed around data minimisation, as the Cyber and Data Protection Act (CDPA) expects: it holds what roaming needs, shares nothing without a rule, and hides private locations. We do not claim certification or an attested compliance status. Final legal and consent text is still to be signed off.

Where is data hosted?

Confirm hosting and data residency for your contract with the Hub team: ask in your enquiry and we provide the details during diligence.

How long is data kept?

These are the current engineering defaults; legal sign-off of the final periods is still open, so confirm them for your contract: raw OCPI message logs 90 days, audit records 7 years, export files 7 days. Charge records referenced by an open assurance hold are never deleted while it is open.

How do we report a security issue?

E-mail support@getzcharging.com and start the subject with “Security report”, so it is kept apart from other questions.

What happens to our access and records if we leave?

Your credentials are revoked and Hub refuses your calls from then on; routing to and from you stops. Your partner record, ended agreements and audit history are kept rather than deleted. Ask us about exporting your records during diligence.

How are OCPI credentials rotated and revoked?

Rotation runs over OCPI between your back office and Hub; the old token keeps working for a short grace window. A suspended partner can only manage its credentials, and a revoked or deactivated partner is refused. Partner onboarding.

How are data API keys controlled?

Each key carries its own scopes and rate limit, is shown once when issued, is stored only as a hash and can be edited or revoked. Keys read public data only. Charging data API.

What happens to late records when a roaming agreement ends?

Discovery and commands stop when the agreement ends. Session updates and charge records (CDRs) of sessions that started under the agreement are still delivered for 90 days after it ends; after that they are refused, with a recorded reason both partners can see.

What can we send to our procurement team?

This page and the neutrality page describe the controls in the product today. For a security questionnaire or a walkthrough with our engineers, e-mail support@getzcharging.com. Hub is operated by Vebbah (Pty) Ltd, trading as Getz Charging.

Security questions from your team?

Our engineers can walk your security team through the controls above.