Reep positions itself as a Digital Custodian, not an owner — every architectural and legal decision follows from that distinction.
Encryption and decryption happen client-side. Reep's servers store ciphertext only. There is no master key, no support-staff override, and no backdoor — because the architecture doesn't include one.
Open the secure app →Reep's release framework is built around the Revised Uniform Fiduciary Access to Digital Assets Act, giving fiduciaries a clear, lawful path to act.
Data minimization, the right to erasure, and explicit consent are built into the product, not bolted on for regional compliance.
Reep never claims ownership of stored data — a distinction that shapes everything from contract terms to deletion rights.
Your data is portable and can be deleted at any time, no questions asked.
Regional data centers comply with local privacy laws around digital inheritance.
Every vault interaction is logged on a private, tamper-evident ledger to prevent fraud during transfer.
Data is encrypted in the browser before upload. Reep servers never process plaintext.
All connections between the app and Reep infrastructure are encrypted end-to-end.
Vault blobs are stored with AES-256 encryption keys managed outside the application layer.
Multi-factor authentication, session limits, and guardian consensus protect every release.