Security and data protection

Last updated: 28 October 2026

How Mwanzo protects your apps and your customers' data, and what companies can use to control access and releases.

For companies

• Organisations with owner, admin and developer roles, shared credits and billing details.
• Single sign-on (SAML 2.0) with Microsoft Entra ID, Google Workspace, Okta and other identity providers, and the option to require it for every member.
• Test copy before live: every app can have a test copy at its own address with its own test database. An organisation can require each version to go to the test copy first, and allow only admins to publish to live.
• Database changes as migrations: changes the AI makes to an app's database are saved as migration files and applied to the live database only when the app is published to live.
• Audit log: who published, changed settings, gave access, approved plans or changed members, with time and IP address. Entries can't be edited or deleted; owners and admins can download it as CSV.
• Your code is yours: download it or push it to your own GitHub at any time, with CI that type-checks and tests every push.

How data is protected

• Credentials you store (database connection strings, payment keys, GitHub tokens) are encrypted with AES-256-GCM and never put in your app's public code.
• HTTPS everywhere: the dashboard, the endpoints apps call, and published apps.
• Row-level security on Mwanzo's database; the server's service key never reaches a browser.
• Your app's customer data goes to the database you connect, not to Mwanzo's.
• Every build runs in its own temporary, isolated sandbox.
• Our code is scanned with Semgrep on every change before it reaches production.

Tanzania's Personal Data Protection Act

Mwanzo follows Tanzania's Personal Data Protection Act (Cap. 44, enacted as Act No. 11 of 2022) and its regulations. When your app collects your customers' data, you are the data controller and Mwanzo is your data processor: our Data Processing Agreement sets out what we do and don't do with it, how we tell you about a breach, and how data is deleted. How we handle your own account's data is in our Privacy Policy.

Subprocessors

These providers process data for Mwanzo, mainly in the United States:

• Anthropic: the AI (Claude) that plans, writes and reviews code; receives prompts and project files
• Google (Gemini): generates placeholder images from short descriptions
• E2B: temporary sandboxes that run apps while they are built
• Vercel: hosts Mwanzo and published apps (test and live copies)
• Supabase: Mwanzo's own database and sign-in, including SSO
• Resend: sign-in and service emails, and support email
• ClickPesa: mobile-money payments, through each customer's own account
• GitHub: code pushes and CI, when a customer connects their own account

Uptime and support

Paid organisations get a 99.5% monthly uptime commitment with service credits, and support response times: see our Uptime and Support Commitment.

Reporting a security problem

Email support@mwanzo.dev with "Security" in the subject. We reply within 2 business days and don't take action against good-faith research that avoids harm to users and data.