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.
01 – Architecture Overview
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
Only integrity checkpoints are stored.
02 – Identity 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.
03 – Independent 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.
04 – Verification 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.
05 – Data 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.
06 – Enterprise Deployment
Enterprise clients may:
- —Deploy private verification endpoints
- —Integrate via API
- —Apply client branding to verification stamps
The core integrity architecture remains unchanged.