Security and data
How we look after drivers’ money and data
What the platform does to protect accounts, payments and partner data, described as it is built. We do not claim certifications or independent audits we do not have.
Accounts
Drivers and staff
Phone sign-in with a one-time code
Drivers sign in with their phone number and a text-message code: no passwords to reuse or leak. Sign-in tokens are kept in the phone’s secure storage.
Back-office single sign-on
Staff sign in through the platform’s identity service (OpenID Connect), and every back-office action is checked against their role on the server.
Separate organisations
Each EMP organisation (a white-label brand’s business) has its own drivers, pricing, users and data. Fleet managers see only their own fleet.
Money
Payments and the wallet
Cards tokenised on the phone
Card details are checked and tokenised on the device; only the payment provider’s token reaches the platform.
Provider callbacks re-checked
Every payment callback is signature- or hash-checked and re-confirmed with the provider before money is credited, and credited once.
A ledger that is only added to
Wallet entries are never edited or deleted. Corrections are new, reversing entries, and balances are worked out from the entries, never stored.
Charge records never changed
Each receipt is built from the operator’s charge record, which is kept as received, so a bill can always be traced back.
Real-time authorisation
Every charging start is checked by the platform at that moment: driver, token and payment method.
Fail closed
A payment or messaging provider without credentials refuses requests with “not available yet”. There are no test shortcuts in production code.
Partners
Partner and roaming data
Open standard, one route
The platform exchanges data with charging operators only over OCPI, through Getz Hub. It never widens an operator’s visibility rules, and home chargers stay private.
Signed webhooks
Partner webhooks are signed, their secrets are stored encrypted, and failing endpoints are retried and then disabled.
Audit trail
Back-office changes to settings such as brand, pricing and unpaid-charging rules are recorded with who changed what.
Privacy law and where data lives
The platform is designed around the Cyber and Data Protection Act (CDPA): drivers give consent in the app, are asked again when terms change, and can export their data or delete their account. Privacy requests are tracked in the back office with their statutory due dates.
Where data is stored for a Zimbabwean deployment is confirmed with each partner in writing. Data residency, retention periods and the final consent text are still to be confirmed with legal counsel.
For procurement and security reviews
- Where data is stored: as described above for your market; the deployment for your organisation is confirmed in your agreement.
- Retention and deletion: drivers can export their data or delete their account in the app, and privacy requests are tracked in the back office. Retention periods are confirmed with legal counsel.
- Access: back-office staff sign in through single sign-on, every action is checked against their role on the server, and changes to brand, pricing and payment rules are recorded.
- Your questions: prospective partners can ask for a technical briefing through the partner enquiry, or send a security questionnaire through the contact page (choose “Technical or security question”).
Reporting a security issue
If you think you have found a security problem in the website or the platform, e-mail support@getzcharging.com or use the contact page (choose “Technical or security question”), and do not include personal data.
Need security detail for a partnership?
Prospective platform partners can ask for a technical briefing on data handling, access control and payments.