How we protect your files
How Everabyte protects your files: client-side zero-knowledge encryption, TLS 1.3 in transit, a second storage layer, recovery controls and monitoring.
Security is a foundation of Everabyte, not an add-on. Zero-knowledge encryption protects file contents on your device before upload, while transport and storage layers add further protection. This article explains each layer and why it matters for your data.
In short
Everabyte protects your files with zero-knowledge client-side encryption, TLS 1.3 in transit, a separate storage-level encryption layer, recovery controls, retention where enabled, object versioning, malware and anomaly detection, and event logging.
Encryption in transit and at rest
Data is protected in transit and at rest using modern cryptographic standards. Everabyte uses AES-256-GCM to encrypt files on your device before upload and TLS 1.3 to protect their transfer. A separate storage-level layer further protects ciphertext at rest.
Encryption before storage
Files are encrypted with AES-256-GCM on your device before upload; Everabyte stores ciphertext without the keys needed to decrypt file contents. The storage infrastructure adds its own encryption at rest. You can read more in The Everabyte encryption model.
Retention controls where enabled
Retention and Object Lock controls are available where enabled for the relevant storage configuration and provider. Retained objects cannot be modified or deleted until their configured retention period ends, which helps preserve data integrity and reduce the risk of deletion or tampering.
One storage region per environment
Each object resides in one region at one provider; multi-region replication is not part of the standard storage model. Individual accounts default to London, and choosing a different storage region is available to Company owners with an active EverStream or EverBlaze plan (including an active trial), under the product rules in effect.
Logging and monitoring
Security-sensitive actions are logged to support traceability, operational review and incident response. Administrative access is role-restricted and requires multi-factor authentication.
Testing and review
Dependency scanning and code review are part of the development process. Penetration testing engagements are scoped and documented individually where contractually agreed.
Tip — Want the full technical picture? Read our security architecture page.
Common issues
Does Everabyte have access to my encryption keys?
Everabyte’s zero-knowledge design keeps file decryption keys on authorized client devices. The platform cannot decrypt file contents. See Can Everabyte read my files?.
What happens if a storage region becomes unavailable?
Availability is covered by the 99.99% uptime SLA on paid plans marked “with SLA”, and by the provider’s own resilience measures. Multi-region replication of your objects is not part of the standard storage model.
Is the security of my data tested?
Dependency scanning and code review run continuously in development; penetration testing engagements are scoped and documented individually where contractually agreed.
Was this article helpful?
Thanks for your feedback.
Still need help?
Can't find what you're looking for? Our support team can help.