Security and data
How Getz Network protects operators’ data
In short: each operator’s data is kept separate, and owners and funders see only the read-only views granted to them for their own sites. Below: how the product isolates data, controls access, protects charger and roaming connections, and keeps records that cannot change.
Who can see a site’s data?
The operator that runs the site, through the roles it gives its own staff and contractors. An installer or maintenance contractor sees only the operator or site it is invited to, and never prices or customers. A site owner, landlord, lodge owner or funder sees only the read-only portal views granted for their sites, until the grant expires or is revoked.
Operator data is isolated in the database
Getz Network hosts many operators on one platform. Each operator’s data is separated by row-level security in the database itself, so every query runs in one operator’s context. The application’s database role cannot bypass those rules.
Access control and audit
- Sign-in to the back office uses OpenID Connect with PKCE through a central identity provider. People are invited by e-mail with a role and access to a whole operator or one site.
- Roles limit what each person can do: network admin, operations, finance, support, maintenance, installer and read-only. Sections a role cannot use are hidden.
- Audit trail: every change made through the back office is written to an audit record, and downloads of report files are audited.
- Host and investor portal: grantees have no back-office membership. Each request re-checks their grant, and revoking it ends access at once.
Charger and roaming connections
- Chargers authenticate with their own OCPP password by default. A charger can be allowed to connect without a password only by an explicit, audited setting that the back office warns about.
- Roaming credentials for Getz Hub are stored encrypted, rotated through the OCPI credentials process, and every change is audited. Without an encryption key configured, nothing is sent.
- Internal service interfaces are on separate ports bound to the local host and require their own tokens.
- Integrations without credentials fail closed: an e-mail provider or payment provider that is not configured is reported as not configured, never faked.
Records that cannot be changed
Charge records are created once per completed session and never edited. OCPP messages are kept as evidence, and late protocol messages never reopen a finished session.
Data residency and retention
| Item | Default |
|---|---|
| Data region | Confirmed in your agreement |
| Raw OCPP message payloads | 90 days |
| Raw charger telemetry | 13 months |
| Audit and financial records | 7 years |
These are the platform’s deployment defaults, not legal advice: the region and retention that apply to you are confirmed in your agreement, and the retention schedule is subject to legal sign-off. Our approach is designed around the Cyber and Data Protection Act (CDPA).
Privacy by design in roaming
Visibility is fail-closed: private sites are never published, and Getz Hub and connected apps can narrow what you publish but never widen it. The host and investor portal never shows prices or drivers’ token ids.
This website
- No analytics load until you allow them. See Cookies.
- Enquiries are forwarded to our systems as signed requests, and server logs record only the outcome of a submission, never your details.
Reporting a security issue
E-mail support@getzcharging.com and mark your message as a security report.
Security questions for your procurement team?
Send your security questionnaire, or ask about hosting, retention, recovery and support escalation, with your site assessment request, and we will answer in writing.