Products

Every product in the Zev ecosystem has its own compliance section here. Each section follows the same shape: overview, data inventory, processing purposes + lawful basis, data flows, third parties, security controls, access control, retention, subject rights, change log.

If you're new to the ecosystem and want the wider context (which product talks to which, how identity flows), start with the ecosystem overview and the cross-product data flows.

Catalogue

ZevID

The centralised identity provider for the ecosystem. Holds account credentials, MFA, KYC outcome, cross-product consent grants, and the Zev Credit ledger. Every other Zev product authenticates users through ZevID. Lives at accounts.zevop.com.

ZevCloud

The application deployment platform. Customers sign in with ZevID, create teams, deploy apps to managed infrastructure, and register / manage domains (both .ng as direct NIRA-accredited registrar and non-.ng via NameSilo). Lives at console.zevcloud.net.

ZevSend

The transactional-messaging API. Developer customers dispatch email (today), SMS, WhatsApp, and OTP-verify from their applications via api.zevsend.com or console.zevsend.com. Deliberately transactional only — bulk marketing is the role of the sibling product ZevCampaign, kept on a separate sending-reputation surface so transactional and marketing complaint profiles don't blur. Controller for customer account / team / domain / billing data; processor for the recipient addresses and message bodies customer applications dispatch.

---

When a product launches

When a new Zev product becomes a real data controller (or processor for one), it gets a section here under docs/products/<lowercase-clientid>/. The shape comes from docs/products/_TEMPLATE/ — copy it, fill it in, open a PR.