Security

Don't take our word for it.

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.

CustomerLindiwe Nkosi
Installation12 kW solar, 2 inverters
Quoted totalR184 500.00
Signed26 Oct 2026, 14:32 SAST
✓Signed and not modified

What Adobe Reader reports when it opens this file. No Vumasign account needed.

It runs in Johannesburg

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.

The seal is checked by the reader

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.

One organisation cannot read another

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.

The audit trail cannot be edited

Append-only at the database level. There is no code path, and no support procedure, that rewrites an event after it happened.

Residency

One region, and it isn't a setting.

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.

Johannesburg, South Africa

Google Cloud africa-south1
  • Signed documents and signer data stored in South Africa, for every account, on every plan
  • A written operator agreement (s21) you can attach to your records
  • A South African operator with a registered company, named people and a physical address
  • Every sealed PDF carries its own certificate of completion, with the envelope’s history, to download from the envelope on any plan

The seal

Four steps. The first is the one nobody advertises.

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.

  1. Verify

    The original’s SHA-256 is checked before anything is written to it. A mismatch aborts the job rather than sealing something else.

  2. Flatten

    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.

  3. Certify

    The Certificate of Completion is generated and appended — who signed, when, from where, and how they were identified.

  4. Seal

    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

Enforced by the database, not by remembering.

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.

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.

Append-only audit events

Events can be written and read. They cannot be updated or deleted — by us either.

Test documents are watermarked, and their seal binds nobody

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.

Signing links are single-purpose

A recipient’s link gets them to their own envelope and nothing else. It is not an account, and it does not become one.

Passkeys for the people who send

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.

Single sign-on, on Business

Sign in through your organisation’s identity provider, and require it for your organisation when you are ready.

Your documents

The evidence travels inside the document.

A sealed PDF holds its own certificate of completion, so the copy you download is the whole record of who signed it.

How long do you keep our documents?
For as long as the account is open. We do not expire a sealed document, because the reason to keep one is that somebody may need it in five years — and a retention policy that quietly deletes evidence is worse than no policy.
Can we get our documents out?
Every sealed PDF carries its own certificate of completion, with the envelope’s history. Download it from the envelope in the dashboard on any plan, or fetch it with the API on the API plan.
What happens if we close the account?
Download your sealed PDFs first — they are yours and they verify without us. Once the account is closed the data goes with it; a copy we kept “just in case” would be a copy you did not authorise.
Who at Vumasign can see our documents?
Access to production data is limited to the people who operate the system, for the purpose of operating it. There is no browsing, and there is no support tool that reads a document to help with a ticket.

Signer checks

How we confirm who's signing.

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 levels
What we keep
The result, with the document’s record: the signer’s level, what was confirmed and when, and for an identity check the provider’s own reference. The same facts are printed on the certificate of completion, so they travel with the signed document.
What we don’t keep
Photos. The picture of the ID and the selfie are taken live on the signer’s own phone for our identity provider, VerifyNow, which runs the check. Vumasign keeps neither image.
What is checked, and where
A South African ID, the Smart ID card or the green ID book, is matched against the Department of Home Affairs photo. A passport is checked for authenticity and matched to its own photo; it is not checked against the issuing government’s records. Images of a passport or a green ID book may be processed by the provider in the EU.
What it doesn’t change
The kind of signature. An identity check strengthens the evidence of who signed. It does not make it an “advanced electronic signature”, which needs an accredited provider.

What we do not claim

The part of a security page that's usually missing.

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.

No ISO 27001 or SOC 2 certificate

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.

Not SAAA-accredited

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?

No penetration-test report to publish yet

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.

Check the seal yourself.

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.

Free · 5 envelopes a month · no cardStart free