CLIENT-SIDE DATA OWNERSHIP
Standalone encrypted backups locked with your passphrase
Export a complete encrypted archive of your journal entries and photos at any time, secured with scrypt key derivation and XChaCha20-Poly1305 authenticated encryption.
How it works
True data ownership requires being able to move and archive your writing without relying on proprietary cloud lock-in. Kept produces standalone backup files that you can store on an external drive, USB key, or cloud storage of your choice.
Technical implementation
Scrypt Key Derivation
Your chosen passphrase is key-stretched using the memory-hard scrypt algorithm to resist brute-force hardware cracking.
XChaCha20-Poly1305 Cipher
Entries, metadata, and attached photos are packaged and encrypted using authenticated XChaCha20-Poly1305 encryption.
Safe Merge Restore
Restoring from a backup merges entries into your existing database rather than overwriting, making it safe to restore multiple archives.
Zero-Knowledge Passphrase
Your backup passphrase is never transmitted or stored remotely. It cannot be recovered by Kept if lost.
Technical specifications
| Attribute | Specification |
|---|---|
| Key Derivation | Scrypt (Memory-hard) |
| Encryption Cipher | XChaCha20-Poly1305 |
| Included Media | Database + Attached Photos |
| Restore Mechanism | Safe merge (Non-destructive) |
| Portability | Standard standalone file |
Frequently asked questions
What happens if I forget my backup passphrase?
Because Kept does not operate a central server, lost backup passphrases cannot be recovered by anyone.
Can I export plain text without encryption?
Yes. You can export your full journal as clean Markdown (.md) files at any time through the share sheet.
Explore other architecture deep dives
Ready to start with Kept?