Your app data stays in Kenya

All customer data is stored and processed in Kenya

Your app data, managed database data, deployment data and account data are stored and processed in Kenya.

Eza Cloud is available to customers in Kenya at launch.

The DPA is accepted at signup and is publicly available before you pay.

Each app runs in its own sandbox

Every Eza Cloud app runs in its own sandbox with its own kernel.

One customer app cannot access another customer app through the Eza runtime.

Use separate organisations, projects and environments to separate client work, staging and production.

Owners and Admins use two-factor sign-in

Two-factor sign-in is required for every organisation Owner and Admin.

Members and Viewers can enable two-factor sign-in for their own accounts.

Eza accounts require a verified email address and phone number.

Data is encrypted in transit and at rest

Eza encrypts customer data in transit and at rest.

Environment variables use envelope encryption at rest.

Runtime secrets are injected when your app starts. They do not enter the build unless you mark them as build-time variables.

Secret values stay hidden in the dashboard until you reveal them. Eza records each reveal.

Daily backups for every managed database

Every managed database on every plan receives daily backups.

PostgreSQL and MongoDB-compatible databases use a daily base backup with continuous log archiving.

MySQL uses a daily full backup with binlog shipping.

Redis-compatible databases use daily snapshots with append-only files.

Backups remain available for 7 days on Hobby and Starter, and 14 days on Pro.

Self-run MongoDB is not a managed database. Eza creates daily volume snapshots kept for 7 days.

Database backups include off-site copies in Kenya. This statement does not apply to Eza Object Storage.

99.5% monthly uptime commitment

Eza Cloud has a public uptime commitment of 99.5% each calendar month.

The commitment covers eligible apps with two or more replicas.

Beta features and add-ons are not covered by uptime credits.

The credit applies automatically to your account balance.

Credits apply to the hosting plan fee. They do not apply to PayEdge, storage packs or other add-ons.

Check Eza service status

The public status page is hosted outside Eza Cloud infrastructure.

It shows current component status, incident history, scheduled maintenance and 90-day uptime history.

Scheduled maintenance has a window

Planned maintenance may run on Tuesday from 02:00 to 04:00 EAT.

Eza gives at least 48 hours’ notice before planned maintenance.

Planned maintenance may total no more than 4 hours in a calendar month.

Report a security issue

Email security@eza.co.ke with details of a suspected vulnerability or security issue.

Do not include secrets, full database exports or customer personal data in the first email.

Eza publishes security contact details at /.well-known/security.txt.

Send privacy requests by email

For account, billing and support data held by Eza, email privacy@eza.co.ke.

For personal data inside an app you host on Eza, contact the app owner first. That customer is the data controller for their app data.

Eza acts as a processor for customer-hosted data and helps customers respond to valid data requests.

Security incidents need clear communication

Eza uses the public status page for platform-wide service incidents.

Affected customers receive direct communication when an incident affects their Eza account or customer data.

Read the DPA before you sign up

The Eza Data Processing Agreement is written for Kenya’s Data Protection Act, 2019.

You can read the DPA before creating an account.

After signup, your organisation can download a signed copy from the dashboard.

Beta features are supported

Beta features are included and supported.

They are not covered by Eza uptime credits.