Skip to Content
Australian support
1300 195 055 support@truevault.com.au Mon–Fri · 9am–5pm AEST
TrueVault Identity Manager
Protect me
NoTouch PDF Signing · built from the source

Signed by the human. Not the keyboard.

Upload a PDF. The recipient looks at their camera once. The signature is bound to a verified face — not a typed name, not a drawn squiggle, not a link forwarded to someone else's inbox. The future of signing, built from the source, not bolted onto old tech.

01
Bound to a face
Not a typed name
02
NoTouch
No mistakes
03
Audit, not argued
Signed event, non-repudiable
Contract.pdf · 7 pages
p. 7 / 7
Employment Agreement
Full name
Mara Holloway
Address
14 Rowan St, Carlton VIC
Date
24 May 2026
Position
Senior Engineer
Signed by
Mara Holloway
verified_human:0x4f…a91c · 14:02:11 AEST
Bound
SHA · 4f9c
Match · liveness
0.998 · passed
01 / The shift

Signing has been arguing about itself for 20 years.

A typed name. A drawn squiggle. A code from an SMS that anyone could be holding. Every generation of e-sign has dressed the same question up in newer clothes — and answered it with the keyboard, not the person. We're done asking the keyboard.

The old way · 01

Type your name

A box on a webpage. Anyone with the link types anything. We pretend it counts.

  • Doesn't prove who pressed enter
  • Repudiable in any contested signing
  • No connection to a real human
The old way · 02

Draw a squiggle

A finger-painting that looks vaguely like a name. It's the same squiggle on every doc.

  • Doesn't match the person, ever
  • Lifted, screen-grabbed, replayed
  • Forgery left as an exercise
The old way · 03

Click the SMS link

A code arrives on a phone. Whoever holds the phone — or the SIM — agrees on the signer's behalf.

  • SIM-swapped, forwarded, shared
  • A phone is not a face
  • No proof the right person tapped
The TrueVault way

One face. One signature.

The recipient looks at the camera. We bind the signature to a verified human, sealed into the PDF itself. No box to type into. No squiggle to forge. No SMS to forward.

  • Only the intended recipient can sign — needs their face
  • Bound into the PDF; verifiable offline, by anyone
  • Non-repudiable; argued by a court, not a vendor
02 / How it works

Send a PDF. Trust the signature.

You don't need to teach the recipient anything. They tap the link, look at their camera once, and the document comes back to you signed — bound to a verified human, with a complete audit trail attached.

On the recipient's phone Live
14:02
Sign · Employment Agreement
Hold still
capturing · 1.8s
Sign with my face
No app to install. No password to remember. ~6s end-to-end
The signing

Six seconds, end to end.

1
Send the PDF
Upload, or generate from a template.
0.0s
2
Recipient opens it
Their phone, their browser. No app.
+1s
3
One look at camera
Live biometric check — ~3 seconds.
+4s
4
Signed and sealed
Bound into the PDF, your inbox pinged.
+6s
No new enrolment: if the recipient already has a TrueVault identity, that's the face we bind. If not, they enrol in ~90 seconds — once, for every doc afterwards.
03 / Two ways to send

Send a doc. Or a doc that fills itself in.

Sometimes the PDF is finished and ready. Sometimes it's an eCAF, a tenancy application, a vendor onboarding pack — and you'd like the recipient's verified details to land in the right boxes by themselves. TrueVault does both, from the same envelope.

Mode A · Upload

Ready-to-sign PDF

Drop a PDF that's already complete — an NDA, a board resolution, a tax declaration. The recipient sees what you sent, looks at their camera, and the signature lands. No tagging signature fields. No filling in for them.

Documents to send · 2 ready
PDF
Employment-agreement-v3.pdf
To Mara Holloway · 184 KB
Queued
PDF
NDA-mutual-2026.pdf
To Daniel Tjandra · 92 KB
Queued
  • Works on any PDF — your tools, your wording
  • Only the intended recipient can sign — needs their face
  • The signed PDF is bit-for-bit verifiable offline
Mode B · Template

Auto-filled from verified data

Send an eCAF, a tenancy form, a vendor onboarding pack. The recipient's name, address, DOB, ABN — anything verified — drops into the right boxes, sourced from the identity they already own. No touch, no typos, no transcription errors.

template · eCAF-conveyance.v4 autofilled
Full legal name Mara Joan Holloway gov-id
Residential address 14 Rowan St, Carlton VIC 3053 gov-id
Date of birth 11 Jun 1991 gov-id
Email mara@…holloway.com.au verified
Phone +61 4… 922 verified
  • eCAF, tenancy, vendor onboarding, KYC packs
  • Fields auto-populated from the recipient's verified identity
  • Recipient confirms with a look — no retyping their own details
04 / The one-shot workflow

One request from you. One easy flow for them.

Signing rarely sits on its own. It comes wrapped around onboarding a new hire, signing up a tenant, taking on a client. TrueVault lets you bundle all of it into a single request — and the recipient walks through one calm flow instead of six.

The request you send

Build it once, send it forever.

Onboard hire · v4
01 Verify contact details
email + phone
02 ID check
gov-id + face
03 Background check
court + police
04 Contract review
employment-v3.pdf
05 Sign with face
biometric bind
06 Enrol to systems
okta · payroll · slack
What the recipient sees

One link. Six steps. Eight minutes.

  1. Contact verified
    Email + phone, sourced live
    1m
  2. ID checked
    Gov ID + biometric match
    2m
  3. Background
    Court / police, where required
    1m
  4. Contract review
    Read, ask questions, agree
    3m
  5. Signed with face
    Bound, sealed, returned
    6s
  6. Systems enrolled
    Email, payroll, access — on
    30s
Each step is optional. Use the bits you need, in the order you need them. Skip what doesn't apply.
05 / The record

Signed by a human. Argued by no-one.

When a signature is queried six months later — by a counterparty, a regulator, a court — you don't recover a "we sent the link" alibi. You hand over a signed event: the right human, the right document, the right time, sealed together at the moment of signing.

Bound, not bolted on

The signature is part of the PDF — verifiable offline, by anyone with the file.

Non-repudiation by design

We never argue about who signed. The biometric, the document hash and the time are co-signed.

Audit logs you can hand to a court

Every step — request, view, capture, bind, return — is a signed event in a single ledger.

signing.log · doc-a91c Sealed 
{
  "event":     "document.signed",
  "document":  {
    "name":    "employment-agreement-v3.pdf",
    "sha256":  "4f9c…a91c",
    "pages":   7
  },
  "signer":    {
    "id":      "verified_human:0x4f…a91c",
    "match":   0.998,
    "liveness":"passed"
  },
  "intent":    "I agree to be bound by this document",
  "issued_at": "2026-05-24T14:02:11+10:00",
  "bound_at":  "2026-05-24T14:02:17+10:00",
  "seal":      "tv1.0:e2…7c"
}
Verifiable offline · TrueVault seal v1 ✓ valid

Send the doc.Trust the signature.

Standalone or stitched into one-shot onboarding — we'll wire it to your workflow, your forms and the systems you already have.