Row-level security, per organisation
Every table carries a policy. The isolation is a property of the database, so it holds for a query nobody has written yet.
Security
The evidence is in your hands, not on our server.
A sealed document verifies in your own software, with no Vumasign account and no request to us. Open it in Adobe Reader and see for yourself.
What Adobe Reader reports when it opens this file. No Vumasign account needed.
Application, database, documents and sealing all in Google Cloud’s africa-south1 region. Not a data-residency add-on and not an enterprise tier: there is no other region to fall back to. What travels is named below: email, through an email provider, the optional AI naming assistant’s filtered template text, and the images an identity check takes.
A PAdES seal with a trusted timestamp, checked in Adobe Reader with no Vumasign account and no request to a Vumasign server. Evidence you hold rather than evidence we hold for you.
Row-level security in the database itself, not a WHERE clause a future query could forget. A query that leaks across tenants does not return the wrong rows — it returns none.
Append-only at the database level. There is no code path, and no support procedure, that rewrites an event after it happened.
Residency
The application, database, document storage and sealing service all run inafrica-south1, Google Cloud's Johannesburg region. No other region to fall back to, no replica elsewhere, and no plan on which residency is an upgrade.
Signed documents and signer data are stored in Johannesburg. Email is delivered by an email provider: invitations carry a link, and the executed copy travels with the completion email as an attachment, unless it is too large to carry. Uploaded template text, after filtering, may be processed in the EU to name fields. Text inside the form's boxes is removed before AI sees it. A form whose fields already hold values is never sent, and ID numbers, phone numbers, dates and email addresses are removed first. An owner or an admin can turn the AI naming assistant off. For an identity check, images of a passport or a green ID book may be processed by the identity provider in the EU, and Vumasign keeps no photos.
Why it matters: POPIA s72 governs transferring personal information out of the country. This section names what travels and where, so your answer is a reading rather than a guess.
The seal
We check the original's hash before a single answer is written into it. That is the difference between sealing a document and sealing the document you uploaded.
Signing happens last, so the signature covers the whole assembled file: flattened answers and certificate pages both. Sign before the certificate is appended and the signature either breaks, or worse, stays valid while covering only part of what the reader sees.
The original’s SHA-256 is checked before anything is written to it. A mismatch aborts the job rather than sealing something else.
Every answer is drawn into the page as part of the document, not as an annotation a viewer can hide or a later tool can strip.
The Certificate of Completion is generated and appended — who signed, when, from where, and how they were identified.
PAdES-B-LT, then B-LTA: the signature, its validation data and a trusted timestamp are embedded, so the document can still be verified after the certificate that signed it has expired.
Isolation
Isolation written as a condition in application code is one forgotten clause away from a breach, in a query nobody has written yet. Ours are properties of the storage layer instead.
Every table carries a policy. The isolation is a property of the database, so it holds for a query nobody has written yet.
Events can be written and read. They cannot be updated or deleted — by us either.
A sandbox envelope is marked on every page, and the seal covers the mark — so stripping it breaks the signature. It is sealed by a certificate we issued for the sandbox and for nothing else, which is what lets an integrator rehearse signature verification against something real while the document itself obliges no one.
A recipient’s link gets them to their own envelope and nothing else. It is not an account, and it does not become one.
Two-step sign-in with an authenticator app or a passkey, on every plan. It is for you and your colleagues; signers never need one.
Sign in through your organisation’s identity provider, and require it for your organisation when you are ready.
Your documents
A sealed PDF holds its own certificate of completion, so the copy you download is the whole record of who signed it.
Signer checks
A sender can ask any signer for an email code, a mobile code or a full identity check before they sign. Every result goes on the certificate. No photo stays with us.
The three levelsWhat we do not claim
Everything above asks you to take something partly on trust. A company willing to name what it doesn't have is making a claim about everything else it said.
We do not hold either, and we will not imply we do with a badge. When one is in progress, this page will say so with a date rather than a logo.
Accreditation matters in the narrow band where a statute demands a signature without naming its type. For the agreements most teams send, it does not apply.
Do you need an AES?When there is one, the summary goes here. A page that stayed silent until it had good news would not be worth reading.
Uptime and incidents are published at status.vumasign.com. Found something? Tell us. We'd rather hear it from you than read about it.
Sign something, open the sealed PDF in Adobe Reader, and watch it confirm, without us in the loop, that nothing has changed since the seal.
Signed, sealed, sorted. Lekker.