Security · Sub-processors
What we store, and who processes it.
Signed documents and signer data are stored in South Africa.
Some of it is processed elsewhere to be delivered: an email, a code, an identity check. This page names each provider, what it receives and where, so your answer under POPIA s72 is a reading rather than a guess.
Last changed 1 November 2026.
What we store
One place, in Johannesburg.
We act as your operator under a written operator agreement. You remain the responsible party.
The operator agreement- Your documents
- What you upload, your templates, and the sealed copy of every completed envelope, with its certificate of completion.
- About signers
- Name and email address, a mobile number if a code is sent to it, their answers, and the audit trail: what they did, when, and from which IP address. For an identity check, the result and the provider’s reference, not the photos.
- About your team
- Each account holder’s name, email address, organisation and role, and the organisation’s settings and brands.
- Where
- All of it is stored in Google Cloud africa-south1, Johannesburg, for as long as the account is open.
Who processes it
Every provider that receives your data.
A provider is on this list when the running product sends it customer data, or when it handles your call to us. When that changes, this page changes, and so does the date at the top.
| Provider | What it does for us | What it receives | Where |
|---|---|---|---|
| Google Cloud | Runs Vumasign: the application (Cloud Run), the database (Cloud SQL), document storage, the sealing keys (Cloud KMS) and the contact form. | Everything listed above. | Johannesburg, South Africa (africa-south1) |
| Google Identity Platform (Firebase Authentication) | Sign-in for the people on your team: password, Google and single sign-on. Signers have no account, so they are not in it. | Account holders’ names, email addresses and sign-in details. | Google’s global infrastructure. It has no region setting. |
| Google Vertex AI, running Claude by Anthropic | The AI naming assistant, which suggests names for the fields on a template. An owner or an admin can switch it off for the organisation. | Printed text from an uploaded template, after filtering. Text inside the form’s boxes, ID numbers, phone numbers, dates and email addresses are removed first, and a form whose fields already hold values is never sent. | European Union |
| Postmark | Delivers every email: invitations, reminders, email codes, completion notices, and messages from the contact form. | Names and email addresses, the message, and on completion the executed PDF as an attachment, unless it is too large to carry. | United States |
| SMSPortal | Sends mobile codes by SMS, and passes WhatsApp codes to WhatsApp. | The signer’s mobile number and the one-time code. | South Africa |
| Meta (WhatsApp Business), through SMSPortal | Delivers mobile codes on WhatsApp. | The signer’s mobile number and the one-time code. | Meta’s infrastructure, outside South Africa |
| VerifyNow | Runs an identity check, when a sender asks for one. | The signer’s ID or passport details, a live photo of the document and a live selfie. Vumasign keeps the result, not the photos. | South Africa. Images of a passport or a green ID book may be processed in the EU. |
| CloudTalk | Answers and routes support and sales calls to +27 87 550 2756: an AI voice agent that answers questions from our public documentation, takes messages and callbacks, and transfers you to a person. Its AI uses ElevenLabs (voice) and Claude by Anthropic (language), through CloudTalk. | The caller’s phone number, what they say on the call (a recording and a transcript), and details they give: name, company, email address, callback number. It receives no signed documents and no signer data from the product. | European Union. ElevenLabs and Anthropic, through CloudTalk, may process outside South Africa. |
Receives no customer data
DigiCert
The trusted timestamp on every seal. It receives a fingerprint (a hash) of the sealed document, which contains no personal information.
Receives no customer data
Google Cloud Scheduler
Starts our background jobs on a timer. It is not offered in africa-south1, so it runs in europe-west1, and it sends an empty request: the work itself is done in Johannesburg.
Receives no customer data
Mintlify
Hosts the public developer documentation. None of your data is in it.
Your choice
The AI naming assistant can be switched off.
It is on by default. An owner or an admin can turn it off for the whole organisation, in Settings, under Organisation. With it off, nothing from your templates is sent to the EU to name fields.
The other providers are how the product does its job: without email there is no invitation, and without a mobile code there is no Level 2. A sender chooses, per signer, whether a code or an identity check is asked for at all.
Residency, on the security pageQuestions a questionnaire didn’t cover?
Write to privacy@vumasign.com. The operator agreement, data subject requests and security questionnaires are answered by the people who wrote this page.
Signed, sealed, sorted. Lekker.