How we protect your files

Security is a foundation of Everabyte, not an add-on. Your files are protected through several independent layers, from the moment they leave your device to the encrypted copies kept in storage. This article explains each layer and why it matters for your data.

In short

Everabyte protects your files with TLS 1.3 in transit, layered encryption at rest (application level plus storage level), Vault-backed master key management, owner-controlled decryption, retention controls 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 TLS 1.3 for transport security: when a file travels between your device and our infrastructure, it is encrypted on the way. Stored data is protected with AES-256-GCM, a modern authenticated encryption standard.

Encryption before storage

Two layers of encryption protect stored files: Everabyte’s application services encrypt files (AES-256-GCM) before they are written, and the storage infrastructure adds its own encryption at rest — direct access to stored objects does not reveal the original file contents. 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.

Common issues

Does Everabyte have access to my encryption keys?

Direct access to stored objects does not reveal the original file contents, and your decryption key remains under your control: Everabyte services cannot use it or access decrypted stored files without an operation authorized by you. 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.