Skip to main content

Security & Trust

Security architecture.

Audrie's security model is built on a single principle: the less data we hold, the less there is to protect or exploit.

01Architecture Overview

SECURITY ARCHITECTURE · CRYPTOGRAPHIC CHAIN

File contents stay on your device; hashes and authentication metadata are recorded

PDF

Document

any format

SHA-256

File Hash

computed locally

ML-DSA-65

Signed Record

post-quantum crypto seal

written simultaneously

Audrie Register

PostgreSQL · fast query cache

sub-100ms verify ＜100ms

Fast pathverify via Audrie register

Hedera HCS

Public ledger · independently governed

immutable · permanent proof 3–5 sec

Independent pathverifiable without Audrie

Audrie does not store file contents.

When a file is authenticated:

  • A cryptographic fingerprint (hash) of the file is created
  • The hash is bound to a verified identity
  • A timestamp is recorded
  • The authentication record is independently anchored

Audrie retains the hash, signature, identity and timestamp needed to verify the signing record. It does not retain the file’s contents.

Your device-held passkey authorises signing. The separate ML-DSA-65 signing key is held encrypted by Audrie, decrypted through AWS KMS for the signing operation, then cleared from memory.

Expert legal opinion

The evidentiary significance of the process.

Dr Ian Freckelton AO KC has considered Audrie’s passkey authorisation, cryptographic signing and public anchoring in an opinion on their evidentiary significance in Australian proceedings.

Explore the legal opinion →

02Identity Binding

Authentication requires verified identity.

This ensures authenticated files are bound to a real, verified individual – not simply an email address.

Identity verification is required once and is not used for marketing purposes.

03Independent Anchoring

Authentication records are anchored to the Hedera public network.

This ensures:

  • Integrity records exist independently of the Audrie platform
  • Verification remains possible even if Audrie is unavailable
  • Long-term defensibility is preserved

File integrity does not depend on trusting a single vendor.

04Verification Model

Verification requires:

  • File upload (drag-and-drop or selection)
  • Email entry (if no existing cookie)
  • Captcha to prevent abuse

Verification is free and publicly accessible.

Anyone can verify. Only verified identities can authenticate.

05Data Minimisation

Audrie:

  • Does not store file contents
  • Does not index document text
  • Does not retain document copies

Only the cryptographic fingerprint and authentication metadata are recorded.

06Enterprise Deployment

Enterprise clients may:

  • Deploy private verification endpoints
  • Integrate via API
  • Apply client branding to verification stamps

The core integrity architecture remains unchanged.