How we protect your journal
End-to-end encryption for everything you write. Your keys, your control.
How encryption works
Your words are encrypted before they ever leave your device.
You write
Your journal entry exists only on your device
Device encrypts
AES-256-GCM encryption using your key
Ciphertext syncs
Only encrypted data leaves your device
We store safely
We hold your data but cannot read it
Security in depth
Multiple layers of protection for your most personal thoughts.
End-to-end encryption explained
Your journal entries are encrypted on your device before they ever leave it. This means the data that travels to our servers is already scrambled. Even if someone intercepted it, they would see meaningless ciphertext. We store your encrypted data but cannot read it.
Your encryption keys
Your encryption key is generated on your device and never leaves it unencrypted. When you add a new device, you must approve it from an existing device. This device approval flow ensures only your authorized devices can access your data. A recovery phrase lets you regain access if you lose all devices.
Web security
We enforce a strict Content Security Policy (CSP) that prevents cross-site scripting attacks. Cryptographic operations run in isolated contexts. All connections use HTTPS with modern TLS. Security headers protect against clickjacking, MIME sniffing, and other common web attacks.
What encryption does not cover
We want to be transparent: some metadata is not encrypted. This includes timestamps (when you created entries), device information (which device synced what), and ciphertext sizes. This metadata is necessary for sync to work but does not reveal what you wrote.
Encryption Algorithm
AES-256-GCM with unique 96-bit IV per entry
Key Derivation
PBKDF2-SHA256 with minimum 100,000 iterations
Mobile Key Storage
Platform keychain (iOS) / keystore (Android)
Web Key Storage
Secure browser storage with isolation
Key Logging
No key material in logs or error reports
Transit Security
TLS 1.2+ for all network requests
Note: These specifications may evolve as we adopt stronger cryptographic standards. We will always communicate changes in advance and ensure backward compatibility for your existing data.
New devices need your approval
When you sign in on a new device, it cannot access your encrypted data until you approve it from an existing device. This prevents unauthorized access even if someone has your password.
Device approval required
New devices must be approved from an existing trusted device
Key exchange protocol
Encryption keys are securely transferred between your devices
Recovery phrase backup
A recovery phrase lets you regain access if you lose all devices
Revoke anytime
Remove device access instantly from your security settings
Approve new device
Keys transfer securely between your devices. Only you control access.