Security
Security isn't a feature.
It's the foundation of YourKeep.
YourKeep is designed so that your private files remain under your control—not ours. Every backup is encrypted locally before it leaves your device, and only you hold the information required to recover it.
🔒 Local Encryption
Files are encrypted entirely on your own device before any backup is created. Your encryption password never leaves your device.
🛡 Zero-Knowledge
YourKeep cannot read your files, recover your password, or decrypt your backups. There are no master keys or hidden backdoors.
🧩 Distributed Backups
Encrypted fragments can be stored across multiple cloud providers, external drives, or local storage, reducing dependence on any single location.
📖 Open Recovery Protocol
Your backups follow a documented recovery protocol. Even if YourKeep no longer exists, compatible recovery tools can restore your data.
Learn More →Our Security Principles
- Your files belong to you.
- Your encryption keys belong to you.
- Your backups belong to you.
- YourKeep should never be required to recover your data.
- Trust should come from architecture, not promises.
How YourKeep Differs
| Traditional Cloud Backup | YourKeep | |
|---|---|---|
| Files stored on vendor servers | Usually | No |
| Provider can access data | Sometimes | No |
| Requires provider to restore | Usually | No |
| Works with your own storage | Limited | Yes |
| Vendor lock-in | Often | No |
Security by Architecture
YourKeep is intentionally designed so that we cannot access your protected data, even if we wanted to.
Privacy is achieved through architecture—not through trust.
Recovery Should Never Depend on Us
Learn how the Recovery Protocol ensures that your encrypted backups remain recoverable in the future.
Explore Recovery Protocol