How secure is communication through the WhatsApp API for business transactions?

Wazy talks to Meta's WhatsApp Cloud API over HTTPS (TLS), and your Meta access tokens are encrypted at rest with AES-256-GCM, on top of an encrypted database. Each user can turn on two-factor sign-in with an authenticator app. Team members get role-based access as owner, admin, agent or viewer, and each business sees only its own data.

1. Overview

Wazy handles business data for the merchants who use it, including their customers' names, phone numbers, email and delivery addresses received from WhatsApp, WooCommerce and Shopify. This page explains how we protect that data, how we prevent it from being lost or leaked, and what we do if something goes wrong. It works together with our Privacy Policy.

2. Encryption

  • In transit: every connection to wazy.africa, portal.wazy.africa and our API uses HTTPS (TLS 1.2 or newer). Calls we make to Meta, Shopify, WooCommerce stores and payment providers also use HTTPS.
  • At rest, database: our database runs with storage encryption turned on (AES-256). Every data file on disk is encrypted, including customer names, contact details, addresses and order data.
  • At rest, secrets: access tokens and keys for connected accounts (WhatsApp, Shopify, WooCommerce, payment gateways) are encrypted a second time inside the app with AES-256-GCM before they are stored.
  • Backups: every backup is encrypted with AES-256 before it is written to disk.
  • Passwords: stored only as a one-way Argon2 hash. We can't read anyone's password.
  • Encryption keys are kept apart from the code, are never committed to source control, and are only available to the people who run the servers.

3. Access control

  • Only the people who need it to run and support the Services can reach production systems or customer data. Access is personal (no shared accounts) and is removed as soon as it is no longer needed.
  • Server access is limited to named administrators. The database, cache and internal services are not reachable from the internet; only the web server is.
  • Accounts need a strong password (at least 8 characters with upper and lower case letters, a number and a symbol). Two-factor sign-in with an authenticator app is available, and accounts are locked for a while after repeated failed sign-ins.
  • Inside the app, team members get role-based access (owner, admin, agent or viewer), and each business can only see its own data.
  • Staff look at a merchant's data only to give support the merchant asked for, or to keep the Services secure.

4. Logging and monitoring

  • Sign-ins, admin actions and changes to account settings are recorded in an audit log with who did it and when.
  • Requests are rate-limited to slow down abuse and password guessing.
  • Server and application logs are kept for a limited time and are watched for errors and unusual activity.

5. Data loss prevention

Our data loss prevention strategy has two goals: data must not leave our control without permission, and data must not be lost.

5.1 Preventing leaks

  • Collect less: we request read-only access and only the data our features need. We never receive payment card details.
  • Keep it in one place: customer data stays in our production database. It is not copied to laptops, spreadsheets, email or chat tools, and it is never used for testing.
  • Separate test and production: development and testing use separate test stores and test data, never real customer data.
  • Share only what is needed: data goes only to the service providers named in our Privacy Policy, and only what each one needs.
  • Exports are controlled: exports are available only to signed-in users of the business that owns the data.
  • Secrets stay secret: passwords, tokens and keys are encrypted, never written to logs and never stored in source code.

5.2 Preventing loss

  • The database is backed up automatically every night. Backups are encrypted and kept for 7 days, then deleted.
  • Restoring from a backup is a written, tested procedure.
  • We delete data on schedule: when a merchant asks, when an app is uninstalled, or when Shopify or Meta ask us to, as set out in our Privacy Policy.

6. Security incident response policy

A security incident is any event where data we hold may have been accessed, changed, lost or shared without permission, or where our systems may have been compromised. Everyone who works on Wazy must report a suspected incident straight away.

  1. Report: anyone (staff, a merchant, a researcher) reports it to hello@wazy.africa with the subject “Security”. We acknowledge reports within 24 hours.
  2. Assess: the incident lead confirms what happened, which systems and which data are involved, and how serious it is.
  3. Contain: we stop the cause, for example by revoking keys and tokens, rotating passwords, blocking access or taking an affected service offline.
  4. Notify: if personal data was affected, we tell the affected merchants without undue delay and within 72 hours of confirming it, with what happened, what data was involved and what we are doing. If Shopify merchant or customer data is involved, we also notify Shopify, and we notify Meta for Meta data. Where the law requires it, we notify the data protection authority and help merchants notify their customers.
  5. Recover: we fix the cause, restore systems and data from clean backups if needed, and check that everything works.
  6. Review: within two weeks we write down what happened, why, and what we changed so it doesn't happen again.

We keep a record of every incident and the actions taken, and we review this policy at least once a year.

7. Reporting a security issue

If you think you have found a security problem in Wazy, email hello@wazy.africa with the subject “Security”. Please give us a chance to fix it before telling anyone else. We won't take action against anyone who reports a problem in good faith and doesn't access, change or keep other people's data.

8. Contact us

Email: hello@wazy.africa
Website: wazy.africa