Security
Security explains how the platform protects data and governs recovery.
Review the product approach to encryption, storage behavior, recovery control, and the security posture behind protected backups.
Data protection philosophy
Backup and recovery are treated as one controlled system so protected copies remain useful the moment recovery is required.
Integrity and version history
The service preserves data state over time so teams can recover the correct version instead of relying on a single snapshot.
Access and recovery
Security is not limited to encryption alone. Access boundaries and controlled recovery are part of the same operating discipline.
Encryption
Protect backup data and transfer paths with encryption as a foundational service behavior.
Backup protection
Stored copies remain controlled and recoverable so source loss does not become operational loss.
Version history
Version history strengthens practical security by making the correct recovery state accessible.
Data isolation
Separate protected data cleanly and control access boundaries with a disciplined storage posture.
Access control
Manage permissions and recovery operations with a model that stays clear for users and administrators.
Secure recovery
Recovery matters as much as backup creation, especially when time and data integrity are critical.
Security Principles
- Encryption as a baseline service requirement.
- Access control that stays understandable under real operational use.
- Data isolation across users, devices, and protected scopes.
- Recovery that preserves control as well as availability.
Security FAQ
The security model is built around encrypted backup data, controlled recovery, clear access boundaries, and disciplined storage behavior.
A secure backup platform must restore the right version quickly and predictably. Availability without controlled recovery is not enough.
Clear separation improves operational control, helps reduce accidental exposure, and keeps protected data easier to manage across teams and environments.