wanika

Trust

Security at Wanika

Your books are the record of your business. This page explains, in plain terms, how we look after them.

Hosting and backups

  • Our services and database run on servers we operate ourselves, currently in Germany (EU). As we grow we may also host with providers such as Contabo, Google Cloud or AWS in the European Union and South Africa; we’ll update this page before your data is stored anywhere else. The other outside providers we rely on are listed in our privacy policy.
  • All traffic to Wanika services is encrypted in transit with TLS and passes through Cloudflare’s network, which protects the services from attacks and outages.
  • The database is archived continuously and backed up in full every night. Backups are stored off-site with Cloudflare R2 in the EU, encrypted at rest, and kept for 30 days. That lets us restore to a point in time after an incident.
  • A further encrypted copy is kept offline, in cold storage on-site in Harare, so your books survive even the loss of a cloud provider. Cold copies are also kept for 30 days, then destroyed.
  • Backup jobs are monitored, and a missed backup raises an alert to our engineers.

Who can see your data

Within your business, you decide. Owners assign roles and can narrow a member’s access by permission, by branch, by ledger account, or to only the documents they created.

At Wanika, access is limited to people who need it for their job, and everything they do is audited:

  • Support staff can open a customer account to help with a problem. Every support session is recorded in our internal audit log — who, when and from where — and the account shows a banner for as long as the session lasts.
  • Direct access to servers and the database is limited to the engineers who work on the infrastructure, and during an incident to designated, trusted engineers. It is used only to keep the service running and to recover from incidents, and it is audited.

Audit trail

Every business has an audit trail recording who created, changed or deleted each document and when, including changes made through an agent key. Owners can review it from Settings.

Signing in

  • Wanika ID supports two-step verification with an authenticator app, with recovery codes for when you lose your phone.
  • Passwords are never stored in readable form.
  • You can see and end your active sessions from your Wanika ID account at id.wanika.online.

Agent keys and integrations

CheckBooks can give AI assistants and other tools access to your books through agent keys (MCP) or by sign-in approval (OAuth).

  • We store only a one-way hash of each key. The key is shown once, when you create it — after that, neither you nor we can read it again.
  • New keys are read-only unless you choose to allow writes.
  • Writes made through a key are checked against the permissions of the person who created it, and appear in the audit trail.
  • A read-only key can read all of your business’s records, so CheckBooks only issues keys to members who can already see everything.
  • Keys can be given an expiry date and revoked at any time from Settings.

Deletion and fiscal records

When you delete a quotation or an unfiscalised invoice, it is removed from our live database straight away; the audit trail keeps a note that it was deleted, but not its contents. Every backup copy, in Cloudflare R2 and in cold storage, expires within 30 days.

Fiscalised invoices can’t be deleted, because ZIMRA holds a signed copy — they are corrected with a credit note, as the law requires.

Monitoring and analytics

We run our own error monitoring and product analytics on our own servers, rather than sending them to third-party analytics companies. Details are in our privacy policy.

Reporting a vulnerability

If you believe you’ve found a security issue, email [email protected]. Please give us a reasonable chance to fix it before telling anyone else, and don’t access or change other customers’ data while testing. We’ll acknowledge your report and keep you updated.