Security and Privacy
redNOTE prioritizes the protection of your video messages and personal information. Our commitment to security empowers you to trust that your legacy messages will be stored, consigned and delivered securely, maintaining the confidentiality and authenticity that you deserve.
A Zero-Trust, Dependable Platform for Conditional Unlock
Cryptographic System
redNOTE is designed from the ground up as a zero-trust cryptographic system, ensuring that private messages, files, and personal instructions remain unreadable to anyone except the intended recipient — even after the creator’s passing.
Zero Trust
Unlike traditional cloud platforms that rely on server-side access and internal permissions, redNOTE operates on a strict principle: the server must not, and cannot, access user content.
2 Layers
At the heart of redNOTE is a two-layer sealed file architecture. The creator encrypts their files locally in their own browser or mobile app, generating a one-time content key that never leaves their device.
Inner Payload
User encrypted files form the Inner Payload, which only the recipient can decrypt. redNOTE’s servers have no ability to extract, view, or reconstruct this content — even if they possess the sealed file itself. No employee, developer, partner, or system administrator can ever access the user’s material, because the decryption keys simply do not exist anywhere within redNOTE’s infrastructure.
Outer Package
The only part that redNOTE can interpret is the Outer Package, a metadata layer containing unlock conditions such as recipient identity, activation rules, verification windows, and death-check requirements. This metadata contains zero personal content.
Its purpose is solely to determine when the inner encrypted content may be released — and to whom.
Gatekeeper
When a recipient initiates a request to unlock the sealed file, redNOTE validates the conditions, then hands back the wrapped key for the inner layer. Only at this point does the recipient’s own browser locally unwrap the actual content key and decrypt the files. redNOTE becomes a gatekeeper of conditions, not a holder of secrets.
Trust
This creates a system where trust is anchored not in the company, but in mathematics, cryptography, and client-side execution.
Death Verification
Even in the creator’s death, the mechanism remains dependable. Death verification begins automatically when a recipient reports a passing; redNOTE initiates a 30-day silent verification cycle, ensuring both safety and respect.
Unlock
If the creator does not respond, the unlock conditions succeed — and yet redNOTE still never sees the message itself. Delivery happens between the sealed file and the recipient’s browser, with the platform merely facilitating the release of the wrapped key, not the content.
This zero-trust design guarantees three critical promises:
redNOTE cannot read your messages
By its intended design, Encryption and Decryption occur locally before the data ever reaches the server.
Your loved ones will receive
Your loved ones will receive what you intended, unchanged and untouched.
The system can verify conditions even if redNOTE staff cannot see the contents.
Your legacy persists
Your legacy persists beyond you, protected by cryptography instead of human judgment.
In a world where privacy failures are common, after-death messages require a level of integrity and confidentiality that traditional platforms cannot offer.
redNOTE provides a dependable, mathematically enforced assurance that your final words remain yours alone — delivered securely to the people you choose, even when you are no longer here to deliver them yourself.