Security ยท Cryptography

Protecting Your Digital Vault: End-to-End Cryptography Demystified

6 min read Published February 2026
A calm bedside table with a blank card, water glass, framed photo, and soft light.
In short: Our v2 E2EE architecture utilizes client-side AES-256-GCM encryption, meaning your private videos are encrypted inside your browser before uploading to our server. We never receive your password or plaintext files.

Most cloud storage platforms encrypt your data 'at rest,' meaning the files are encrypted only after they reach their servers. The critical vulnerability of that approach is that the platform holds the keys. If their server is compromised, or a rogue employee gains access, your private data can be decrypted.

MyFinalMessage uses client-side End-to-End Encryption (E2EE v2). Here's why that difference matters for private storage:

The Math of AES-256-GCM

When you record or upload a video on our platform, your browser generates a random 256-bit symmetric Data Encryption Key (DEK). The video file is scrambled using AES-GCM right in your browser's memory sandbox. By the time the file is transmitted over the internet, it is already indecipherable ciphertext.

Your password is run through a Key Derivation Function (PBKDF2 with 600,000 iterations) to wrap the DEK. Because we never store your password in plaintext (we only store a secure bcrypt hash of it), we have no mathematical way to decrypt your DEK or your video.

Client-Side Encrypted Storage

This design means that routine storage keeps video content as encrypted blobs. Without the required key material, the ciphertext cannot be reversed into a watchable video. Recipient delivery still depends on the documented server-assisted dispatch flow, so the precise claim is client-side encrypted storage rather than pure zero-knowledge.

Secure Your Digital Legacy Today

Write or record your thoughts in a client-side encrypted vault. Only delivered when your configured delivery process is complete.

Create Free Account →

Written by the MyFinalMessage Editorial Team · Last reviewed February 2026 · Back to Blog