01Platform · Security
The parts you are right to ask about
A charging platform holds money, driver identities and remote control of physical infrastructure. This page states how each is handled — and, where a certification is not yet held, says so plainly rather than implying otherwise.
Posture
Six things that matter most
Tenant isolation in the data layer
Scoping is applied where queries are built rather than remembered at each call site. One operator cannot reach another’s data through the console, the exports or the API.
Encrypted credentials
Payment gateway keys, charger credentials and roaming tokens are encrypted at rest and held per tenant — your merchant account, your keys.
No card data on the platform
Card details are handled entirely by RBI-authorised payment aggregators. zevOS stores the gateway reference and status, nothing more.
Audited actions
Tariff changes, remote commands, refunds, permission changes and settlement approvals are recorded with who did them and when.
Indian data residency
Operational data is hosted on Indian cloud infrastructure, with residency and retention terms that can be fixed contractually.
Your data stays yours
Sessions, drivers, meter values, payments and settlements are exportable in full through the console and the API, at any time, without asking.
Data handling
Where your data lives and who can reach it
The short version: it is yours, it stays in India, and you can take all of it out at any moment without asking.
- Hosting
- Indian cloud regions; residency fixable contractually
- Transport
- TLS everywhere, including charger WebSocket connections
- Credentials at rest
- Gateway keys, charger credentials and roaming tokens encrypted
- Card data
- Never stored — handled entirely by the payment aggregator
- Tenant isolation
- Applied in the data-access layer, not per query
- Authorisation
- Server-side on every request; front-end checks are advisory only
- Audit
- Tariff changes, remote commands, refunds, permissions and settlement approvals
- Backups
- Regular encrypted backups with tested restore
- Export
- Full data export through the console and API, at any time
Practices
How the system is built and operated
Least privilege by role
Staff hold roles rather than assembled permission sets, and station groups restrict them to their own territory — enforced on data, exports and commands alike, not by hiding menu items.
Financial actions separated
Refunds, settlement approval and payout marking are permissioned separately from operational actions, so an operator who can reset a charger cannot necessarily move money.
Secrets from the environment
No credentials in the codebase, no credentials in logs. Per-tenant gateway keys are encrypted and never rendered back to the interface after entry.
Rate limiting on public surfaces
The driver-facing charging flow and the public API are rate limited, because they are the surfaces a stranger can reach.
Input validated at every boundary
OCPP frames are schema-validated at the gateway; API requests are validated at the edge. A charger is never trusted, and neither is a client.
Chargers are not trusted
A charge point is an unattended device in a public place. It authenticates per identity, its messages are validated, and it cannot assert a billing outcome the platform has not verified.
Compliance
What we hold, and what we do not
Listing a certification before the audit is complete is common and dishonest. These are separated deliberately.
GST-compliant invoicing
Tax invoices and receipts with HSN/SAC classification, place-of-supply determination and sequential numbering per series.
PCI scope minimised by design
Card data never touches the platform — the payment aggregator handles it end to end, which keeps cardholder data out of scope entirely.
Role-based access control
Server-side authorisation on every request, with station-group scoping and separately permissioned financial actions.
ISO 27001
Information security management system — implementation underway.
SOC 2 Type II
Planned once the control environment has a sufficient observation period.
If your procurement process requires one of these today, tell us early — we would rather say so than waste your evaluation cycle.
Bring your security review forward
A conversation with your security team early is cheaper for both of us than a surprise at contract stage.