01 CLIENT-SIDE ENCRYPTION
YOUR BROWSER
PLAINTEXT
DATABASE_URL=postgre...
AES-256-GCM + ARGON2ID
→
ENCRYPTED OUTPUT
CIPHERTEXT
256 BIT KEY
|
65MB ARGON2 MEMORY
|
0 SERVER KNOWLEDGE
02 IF HACKERS BREACH OUR SERVER
SERVER MEMORY DUMP
vault_id: a7f2-9c1b-4e3d [PUBLIC]
ciphertext: X#k9$mZ@!pL2... [USELESS]
salt: 0x7f3a9b2c... [PUBLIC]
iv: 0x1d4e8f2a... [PUBLIC]
token_hash: sha256:9f2c... [ONEWAY]
ATTACKER GETS:
Your secrets
Decryption key
Original token
Useless gibberish
03 AUTO-DESTRUCTION TRIGGERS
TTL_EXPIRED
MONITORING
WRONG_TOKEN
MONITORING
READ_ONCE
MONITORING
SERVER_RESTART
MONITORING
THERE IS NO:
✗ Extend time ✗ Resend token ✗ Recovery option ✗ Second chance
GONE = GONE FOREVER
04 BRUTE FORCE? IMPOSSIBLE
SIMULATED ATTEMPTS
0
@ 1 TRILLION / SECOND
Token possibilities: 2²⁵⁶
Time to crack: 0 YEARS
Universe age: ~13.8 × 10⁹ years
05 MATH PROTECTS YOU, NOT PROMISES
Read your secrets
encrypted before reaching us
Recover deleted vaults
RAM only, no persistence
Extend vault lifetime
timer is immutable
Hand data to authorities
we don't have the keys
THIS IS BY DESIGN, NOT BY POLICY.