Skip to Content
Australian support
1300 195 055 support@truevault.com.au Mon–Fri · 9am–5pm AEST
How it works

Seven simple ideas.
One modern way to handle identity .

Modern digital identity doesn't require more data, more tracking, or less privacy. When it's designed properly, it requires less of everything that puts you at risk. Here are the seven ideas that make that possible — and how they stack together.

Read the series See how they fit together
A coherent system

Seven ideas.
One system.

No one concept stands alone. Read this as a connected whole — each idea closes a gap the others don't. Remove one and the system gets weaker, not lighter.

The articles below explain each in plain language, and what it changes for you and for the businesses you deal with.

Chapter 01 · Selective disclosure

Share only what answers
the question.

A service rarely needs your full identity. It needs the answer to one question — are you over 18, do you live here, are you who you say you are. Selective disclosure lets you answer that one question, and keep the rest.

01 Limits what is shared
Selective disclosure
For you

Your data is used to answer a question — not copied, stored, or built into a profile.

Example
Prove you're over 18 without revealing your date of birth.
For your business

Make reliable decisions without becoming a custodian of sensitive data.

Example
Confirm an age requirement is met. Store the result. Never the document.
Chapter 01 of 07
Next: Verifiable credentials
Chapter 02 · Verifiable credentials

Verify once.
Use it everywhere it matters.

Think of a driver's licence — issued once, accepted anywhere. Verifiable credentials are the digital version. A trusted issuer signs them; any service can check they're real. And combined with selective disclosure, you choose how much of the credential to share. With TrueVault's unique system, you can also see who requested what, and what you agreed to.

02 Makes trust reusable
Verifiable credentials
For you

Prove facts about yourself without starting from scratch every time.

Example
You verify your identity once with a trusted provider, then reuse that proof anywhere — no more uploading your passport for every new account.
For your business

Turn trust into a reusable asset instead of a repeated, risky process.

Example
Accept a signed credential issued by a trusted provider. Check it cryptographically. Store the outcome, not the source.
Chapter 02 of 07
Next: Identity-backed authentication
Chapter 03 · Identity-backed authentication

Log in as you.
Not as a password.

Passwords confirm you know a string. Devices confirm you're holding one. Identity-backed authentication goes further — it confirms the person logging in is the same verified human as last time. Quietly, in the background, every session.

03 Secures access
Identity-backed authentication
For you

Your account is tied to you, not to a device that could be lost or a password that could be guessed.

Example
You sign in to a service. Behind the scenes, a biometric check ties access to your verified identity — the service knows it's you, without storing anything new.
For your business

Authenticate real people, not just credentials. Strong assurance without storing documents.

Example
Run a standard OAuth flow. The identity provider only issues tokens after a live biometric ties to a verified identity. Your app gets a regular token, with much stronger meaning.
Chapter 03 of 07
Next: One person, one account
Chapter 04 · One person, one account

One person. One account.
No second face.

Most rules only work if they apply to real people. Bans, refunds, fair queues, one-vote-per-person — all of them break the moment someone can spin up a fresh account on a new email. Binding each account to a verified human turns rules from suggestions into something the system can actually enforce.

04 Makes rules enforceable
One person, one account
For you

You're competing and interacting with real people — not armies of fake accounts.

Example
A platform you use stays fair because someone who was removed can't just come back with a new email.
For your business

Make enforcement meaningful. Reputation, refunds, bans and limits become real.

Example
An account cannot be created or revived without biometric matching against your existing verified identity record.
Chapter 04 of 07
Next: Proof of personhood
Chapter 05 · Proof of personhood

A real person.
Right now.

Proof of personhood answers one small question — is there a live human here, at this moment. Not who they are, not whether they've been here before. It blocks bots and AI agents pretending to be you. It's a useful first line. It is not, on its own, enough.

05 Limits automation
Proof of personhood
For you

Fewer bots, less manipulation, and no AI agents impersonating you.

Example
A liveness check during sign-up blocks scripted access — but real protection comes when it's paired with an identity-backed account.
For your business

Block automation at the front door. Pair with identity for lasting enforcement.

Example
Proof of personhood stops scripted account creation. Identity-backed authentication stops the same human creating five accounts the slow way.
Chapter 05 of 07
Next: User-controlled identity
Chapter 06 · User-controlled identity

Your identity.
Used with your permission.

A centralised identity that nobody can question quickly becomes something else. User control keeps it honest. You can see when your identity is used, what was shared, and you can revoke that permission. Consent is ongoing, not a checkbox you ticked once.

06 Preserves legitimacy
User-controlled identity
For you

Real, ongoing control over how your identity is used — not a one-time agreement you can't take back.

Example
You open your dashboard, see every business that's used your identity in the last month, and switch off any you no longer use.
For your business

Transparent, consent-driven identity. Easier to justify, easier to audit, harder to abuse.

Example
A user grants access for a specific purpose. If they revoke it later, future requests are denied automatically.
Chapter 06 of 07
Next: Verifying without keeping documents
Chapter 07 · Verifying without keeping documents

Verified.
No documents kept.

The traditional model: every business asks for a copy of your passport, then keeps it forever. The modern one: identity is verified once, by a trusted provider. The verified facts — the answers a business actually needs — get reused. The documents that produced them don't get kept. Same answer. No scans to leak.

07 Removes the data liability
Verifying without keeping documents
For you

The facts that were checked stay, so you don't have to re-verify. The passports and licences that proved them aren't kept anywhere they could be stolen.

Example
You verify your identity once. The next service to ask only learns it was verified — they never see the passport.
For your business

Meet the verification bar without holding the documents. Keep the verified facts you need to reuse. Leave the scans, uploads and source files out of your systems.

Example
Receive a verified outcome from a trusted provider. Store the facts you need to act on. The source documents that produced them don't enter your storage.
The system, recapped

Identity, designed as
risk infrastructure .

Read top-to-bottom: each layer assumes the ones beneath it. Read bottom-to-top: each layer makes the one above it possible. We don't pick — we use all seven.

"

Modern digital identity doesn't require more data, more tracking, or less privacy. Designed as a coherent system, it reduces data collection, improves security, and gives you real control.

Next

Now see what it looks like
as a product.

Seven ideas, one identity, one product. Take the tour, or take it back — it's been yours all along.