What we do, and what we do not.
Everything on this page is quoted from the published documents that bind us, with the version of each. Nothing here goes further than they do, and where something is not done they say so.
Where the books are kept
5.1. Processing takes place in Amazon Web Services' Cape Town region (af-south-1), in South Africa.
5.2. Some sub-processors in Annex 3 process outside Africa. Where that involves a transfer that requires a safeguard, the safeguard is the relevant provider's standard contractual clauses or an adequacy decision, and we will tell you which on request.
From the Data Processing Agreement — for businesses, §5, version 2026-11-06.
Where the law of your market requires accounting or tax records to be held within that country, we hold them there or we tell you we cannot serve you. We do not open ThumaBooks in a market before we know which of those two it is.
From the ThumaBooks Terms, §8, version 2026-10-22.
| What | How long | Why |
|---|---|---|
| Backups | 35 days, rolling | Recovery |
From the Data Processing Agreement — for businesses, Annex 1, version 2026-11-06.
Who else processes them
| Who | What they do | Where |
|---|---|---|
| Amazon Web Services | Hosting, database, object storage, email delivery | South Africa (af-south-1); email delivery may route via other AWS regions |
| Stripe | Card payments and subscriptions | Ireland / United States |
| Twilio | One-time codes and messages by SMS and WhatsApp | United States, with regional routing |
| Maps, addresses and route estimates; push notifications to devices | United States | |
| Amazon Rekognition | Automated identity document and face checks, where enabled | South Africa (af-south-1) |
| Anthropic, PBC | Reading documents sent to ThumaBooks and writing the words of a Brief, under zero data retention: nothing is kept once the model has answered, and nothing is used to train a model (the ThumaBooks AI Policy). For ThumaTrade, writing the assistant's replies to your customers, when you have switched it on (section 3A), and, for Prospects, proposing your ideal customer and writing your draft emails (section 3B), under the same zero data retention | United States |
Smile Identity was on this list and should never have been. It was named as an identity sub-processor in Kenya and South Africa on the strength of an integration that was designed and then abandoned in favour of Amazon Rekognition, which runs in our own AWS account in South Africa. No customer's identity information has been sent to Smile Identity: no released version of the Platform has contained a client capable of sending it, and the API credential such a client would require has never existed in any Thuma environment. Removing the row is a correction of this document, not a change of supplier — see the note above about what this annex is for.
We use no advertising or analytics processor that receives your customers' details, and we do not sell or share them.
From the Data Processing Agreement — for businesses, Annex 3, version 2026-11-06.
Sub-processors. The list in Annex 3. We may add or replace one on 30 days' notice to you; if you reasonably object on data protection grounds within that time, we will work with you on an alternative and, failing one, you may terminate the affected service without penalty. Every sub-processor is bound by obligations no weaker than these.
From the Data Processing Agreement — for businesses, §3.4, version 2026-11-06.
Security
What is actually in place, written so that somebody deciding whether to trust us with their business can check it rather than take it on faith. Where something is not done, it says so — a security page that lists only strengths is a marketing page, and the omissions are what a buyer is looking for.
The short version
- Card numbers never reach us.
- Money is a ledger that cannot be edited, only added to.
- Every staff action is recorded against a person.
- Two-factor authentication is required for staff, not offered.
- We hold no security certification, and have not yet had an independent penetration test.
Where it runs
The platform runs on Amazon Web Services in Cape Town (af-south-1) — the data stays on the continent it is about. The database is Aurora PostgreSQL with encrypted storage and automated backups; files live in private object storage, reachable only through short-lived signed links, never by a public URL.
Connections
TLS 1.2 or better everywhere, including between our own services. The database refuses unencrypted connections and its certificate is verified against a pinned certificate authority bundle rather than by trusting whatever answers.
Payments
Card details never touch a Thuma server. The card fields on the ThumaPay checkout are the payment processor's own frames, served from the processor's own domain — we receive a token, never a number. That keeps our PCI DSS scope at SAQ-A, which is the lowest there is, and it means a compromise of our servers cannot expose a card.
Mobile money and cash flow through their own rails; we hold no rail credentials in the app.
Money
The ledger is append-only. Entries are never updated and never deleted: a correction is a new balancing entry, and every transaction must balance before it is accepted. This is enforced by the database, not by a convention somebody could forget — so the history of what moved cannot be quietly rewritten, by us or by anybody who reached the database.
Escrow, driver payouts, merchant remittances and service credits are all postings in that one ledger, which is why they can be reconciled against each other.
Who can do what
- Role-based access for staff, with the permissions of a role listed explicitly rather than implied by seniority.
- Scoped to markets. A person invited to work Zimbabwe cannot act on Zambia.
- Two-factor authentication is required, enrolled at first sign-in. There is no path to a console session without it.
- Every permitted action is audited — who, which permission, which route, when. The audit is written by the guard that grants access, so an action cannot be taken without producing the record.
- Customers and drivers sign in with a one-time code to their number. Sessions refresh and can be ended.
Personal information
- Identity documents are uploaded from the handset directly to private storage — they never pass through the API, and there is no endpoint that accepts a file.
- Automated identity checks are made by a named vendor; a human reviews anything the machine will not clear.
- Consent and every agreement accepted are recorded with the version and a hash of the exact wording, so what somebody agreed to can be produced years later.
- Retention periods are published in Annex 1 of the Data Processing Agreement.
Building and shipping
Every change is reviewed and has to pass an automated gate set before it can ship: type checking, the full test suite, a boot check, dependency review, and a set of repository-specific gates that fail a build for things like an unreachable screen, an unauthenticated mutating route, or a translation that went missing. Secrets live in AWS Secrets Manager and never in the repository or an image.
Dependency advisories are reviewed on a schedule. Anything accepted rather than fixed carries a written reason and the condition that would change the decision.
When something goes wrong
- Incidents are published at status.thumaexpress.com while they are happening, with updates, and they stay readable afterwards.
- Businesses on a paid plan have a service level agreement with credits that are paid automatically — see the SLA annex.
- If a breach affects a merchant's customers, we tell that merchant within 72 hours of becoming aware, with what we know at the time.
Telling us about a vulnerability
Write to security@thumaexpress.com with enough detail to reproduce it. We will acknowledge within two working days and keep you informed. We will not take legal action over research done in good faith that does not degrade service, access more data than is needed to demonstrate the issue, or expose anybody's personal information.
What we do not have
- No SOC 2 and no ISO 27001. Neither is in progress today.
- No independent penetration test yet. The intention is to commission one before the platform carries enterprise volume; until it has been done, this page will keep saying so.
- No bug bounty programme. Reports are still welcome and still answered.
This page is versioned like every other document here. If it changes, the version changes with it, and the previous version stays readable.
From the Security Overview, version 2026-08-13.
AI and your books
- A person stays in charge. AI reads, proposes, writes words and points things out. An entry is posted only by a person, or by a rule or a confidence level that a named person set and can switch off. The AI never files a return, never pays or moves money, and never decides anything about a person on its own.
- Your books never train an AI model. We do not use them to train models, and the provider of the model we use may not use them to train its own (section 6).
- You can see what the AI did. Every entry records how it was made. The AI activity view shows, for each month, what the AI read and proposed and what became of each proposal.
- Figures come from your books, never from the AI. Where the AI writes words about your figures, every figure is taken from the books. A sentence that cannot be checked against them is left out.
- We measure before we change. Every AI feature is tested against fixed test sets before any change to its model or its instructions (section 8).
From the ThumaBooks AI Policy, §1, version 2026-10-11.
What the model receives. Only what the feature needs:
| Feature | What is sent to the model |
|---|---|
| Reading a document, a statement or old books | The document you sent, and the country your books are kept in |
| Briefs | The period's figures, by name, and the names of the accounts behind the largest costs |
| Ask the books | The question, and the parts of your books the answer needs that the person asking may read: the chart of accounts, balances, the profit and loss for the period asked about, an account's entries, and what customers owe, with their names |
| Keeping tax dates current | A country's published tax dates and the public pages they come from; nothing from any business's books |
Your customer list, your other documents and your login details are never sent to the model.
Who processes it. We use Claude models provided by Anthropic, PBC (United States), under Anthropic's commercial terms, as a sub-processor.
Anthropic is listed among our sub-processors in Annex 3 of the Data Processing Agreement. Where sending a document to the United States is a transfer that the law of your market regulates, the safeguard is the one that law requires: standard contractual clauses, or another mechanism it recognises. We tell you which on request.
Never used to train a model. We do not use your books, your documents or anything derived from them to train or fine-tune any model. Anthropic's commercial terms do not permit it to train its models on content we send through its API, and we use Anthropic under a zero data retention arrangement: what we send is not stored by Anthropic once the model has answered.
Where it is kept. Your books and the documents you send are kept in Amazon Web Services' Cape Town region (af-south-1), in South Africa, as the Data Processing Agreement says. A document or a period's figures leaves that region only for the moment the model reads it; it is not kept by the model's provider, and what the model returns is kept with your books.
How long. The original of every document is kept with your books for as long as your books are kept, so that every entry can be traced to its source. What the AI returned is kept beside it, with the model and the version of its instructions.
When your account ends, the documents and what the AI returned are deleted or returned to you, at your choice, except what the law requires us to keep, as the Data Processing Agreement says (3.7 and Annex 1). Backups age out within 35 days and are not restored to serve a request.
Never sold, never for advertising. We do not sell your data, share it for advertising, or use it to profile you.
From the ThumaBooks AI Policy, §6, version 2026-10-11.
Your books are yours
Your books are yours. You may export them at any time in a machine-readable form, and you may do so without asking us and without notice.
We process your data as described in the Privacy Policy and, where you are a business customer, the Data Processing Agreement.
We do not use your financial data to make lending decisions about you, and we do not share it with any lender, without your separate, specific and revocable consent. Consent to that is never a condition of using ThumaBooks. This sentence constrains us and not you, and it is meant to: it is written to bind any future lending proposal that would find your books convenient.
Where the law of your market requires accounting or tax records to be held within that country, we hold them there or we tell you we cannot serve you. We do not open ThumaBooks in a market before we know which of those two it is.
From the ThumaBooks Terms, §8, version 2026-10-22.
We do not delete your books because an invoice is late. A subscription that lapses becomes read-only: you keep access to everything already recorded and you can still export it.
If we discontinue ThumaBooks we will give you no less than ninety days' notice and keep export available throughout.
Statutory retention is yours to satisfy. Export your records; do not rely on us holding them for the period your law requires.
From the ThumaBooks Terms, §9, version 2026-10-22.
Status and incidents
Whether ThumaBooks is up, and any incident while it happens, is on status.thumabooks.com.
- Incidents are published at status.thumaexpress.com while they are happening, with updates, and they stay readable afterwards.
- Businesses on a paid plan have a service level agreement with credits that are paid automatically — see the SLA annex.
- If a breach affects a merchant's customers, we tell that merchant within 72 hours of becoming aware, with what we know at the time.
From the Security Overview, “When something goes wrong”, version 2026-08-13.