Encryption first
Data is protected in transit with TLS 1.3 and at rest with layered encryption: application-level encryption before storage, plus a storage-level layer within Everabyte's storage infrastructure.
Security architecture
Security at Everabyte
Private cloud storage, designed with security at every layer.
Everabyte is built to protect customer data in transit, at rest, and throughout its lifecycle. The platform combines strong encryption, controlled access, resilient backups, and carefully managed infrastructure to deliver a security posture designed for demanding teams.
At restAES-256-GCMfor protected stored data
In transitTLS 1.3for network transport
BackupsRetentionObject Lock where enabled
HostingSingle regionregion choice where allowed
Layered security model Live
Secure preparationFile prepared, integrity checked
TLS 1.3Encrypted in transit
Encrypted storageCiphertext only
Retention layer
Retention controlsObject Lock · where enabled
LockedCore principles
Four principles that guide every security decision.
Everabyte is engineered around a simple goal: protect customer data with layered security, clear operational controls, and strong infrastructure design.
Controlled access
Access to administrative systems is restricted and monitored. Security-sensitive actions are logged to support traceability, operational review, and incident response.
Retention controls
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.
Infrastructure discipline
Everabyte relies on trusted infrastructure environments designed to support high availability, strong isolation, and dependable security operations.
Data flow
How data moves through Everabyte.
Every file passes through a layered security model from upload to backup.
01Client
Secure preparation
Files are prepared for upload with security in mind before being committed to persistent storage.
02Identity
Authentication
User authentication and session handling are separated from file protection logic. Session tokens are used for access control, not as decryption material.
03Transport
Transport security
All network traffic is protected with TLS 1.3 to prevent interception during transfer between devices, APIs, and storage services.
04Storage
Encrypted storage
Stored objects remain protected as encrypted data, so the storage layer handles ciphertext rather than readable user content.
05Retention
Retention protection
Retention and Object Lock controls, where enabled for the relevant storage configuration and provider, prevent retained objects from being modified or deleted until their configured retention period ends.
06Audit
Monitoring and auditability
Security-relevant events are logged and monitored to support operational visibility, incident response and anomaly detection.
Protection model
What we protect against, and where the boundaries are.
Everabyte is designed to defend against realistic security threats with a layered architecture and clear controls.
Threat scenarioOutcomeDefenseAssessment
Infrastructure compromise
If an infrastructure component is attacked, the security model is designed to limit exposure through encryption, access restriction, and operational safeguards.
Mitigated
Encryption, access restriction, and operational safeguards layered together
Layered
Internal risk
Administrative privileges are tightly controlled and monitored to reduce the risk of unauthorized internal access.
Restricted
Tightly controlled and monitored administrative privilege
Controlled
Legal and regulatory requests
Everabyte handles data requests according to applicable law and the scope of the service configuration in use. Security and privacy are treated as first-class operational requirements.
Documented
Requests handled within the scope of the deployed architecture and applicable law
Scoped
Recovery boundaries
Recovery behavior depends on the product configuration and account recovery model. The platform is designed to balance strong protection with reliable operational recovery where applicable.
Depends
Recovery model tuned per product configuration and account type
Varies
Endpoint security
Security at the cloud layer does not replace endpoint security. Customer devices should still be protected with strong authentication and modern device hygiene.
Limited
Endpoint security remains a shared responsibility
Shared
Isolation boundaries
Isolation is layered — and it is not availability.
Different layers isolate different things. Isolation separates your data and services from other companies; it does not by itself provide high availability or disaster recovery, which depend on the contracted service.
Tenant isolation — always on
On the shared platform, each company's application data stays logically separated from every other company.
Application environment isolation — optional
A Managed Private Environment runs your application services in a dedicated environment, separated from other companies' instances.
PostgreSQL isolation — with a private environment
With a Managed Private Environment, your company receives its own PostgreSQL instance. The shared platform uses centrally operated PostgreSQL with logical tenant isolation.
Separate object storage
File storage objects live on Everabyte's separate object-storage architecture — never inside an application VM or PostgreSQL instance.
Backup protection
Retention and Object Lock controls, where enabled for the relevant storage configuration and provider, protect retained files on Everabyte's storage platform until their retention period ends. Database backups inside a Managed Private Environment follow the backup policy defined in your service agreement.
Availability is separate
Redundancy and uptime depend on the infrastructure and contracted service — isolation alone does not create high availability.
Standards & trust
How Everabyte maps to recognized controls.
Everabyte applies its own security controls across encryption, access management, monitoring, and backup resilience. The infrastructure environment used by Everabyte is selected to support strong security, privacy, and operational reliability.
Everabyte applies its own security controls across encryption, access management, monitoring, and backup resilience. The infrastructure environment used by Everabyte is selected to support strong security, privacy, and operational reliability.
GDPR support
GDPR-oriented privacy controls and data handling practices.
Data residency
Customer data can be stored across 12 storage regions — London (default for individuals), Amsterdam, Frankfurt, Paris, Milan, Toronto, Tokyo, Oregon, San Jose, Virginia, Sydney, and Singapore. Region availability depends on the product and plan you use.
Encryption in transit
Encryption in transit with TLS 1.3.
Encryption at rest
Encryption at rest with AES-256-GCM: each file is encrypted with its own key, stored only in wrapped (encrypted) form.
Backup resilience
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 retention period ends.
Security testing
Dependency scanning and code review in the development process; penetration testing engagements are scoped and documented individually where contractually agreed.
Master key management
Everabyte protects its infrastructure master encryption keys through platform-managed, versioned key storage kept outside the application database.
Malware detection
Malware detection helps identify potentially harmful files through Everabyte's supported scanning workflows. Availability varies by plan and configuration.
Anomaly detection
Anomaly detection helps identify suspicious activity and unusual storage operations that may indicate a security threat. Availability varies by plan and configuration.
Everabyte works with infrastructure environments that are chosen for dependable availability, strong isolation, and recognized security practices.
Storage model
Each object resides in its assigned storage region within Everabyte's storage infrastructure; there is no standard automatic cross-region replication. Region choice is available where the product rules allow it.
Infrastructure certifications
Where applicable, underlying infrastructure providers may maintain certifications or compliance programs relevant to their own services.
Facts an enterprise reviewer can verify: our regulator, our subprocessors, and our public commitments.
ICO registration
Everabyte Limited is registered with the UK Information Commissioner's Office (registration ZC209141).
Subprocessors
Stripe, NowPayments, IONOS UK, Mailgun, Lenochat and Google Analytics (with consent) are named in our privacy policy, with 30 days' notice before any new subprocessor is added.
Breach notification
We notify the ICO of notifiable personal data breaches without undue delay and, where feasible, within 72 hours of becoming aware of them, as set out in our privacy policy.
Procurement & due diligence
Answers for enterprise and security review.
This page gives enterprise teams a clear starting point for security review, due diligence, and procurement validation.
Q · 01Access
Q.Can Everabyte staff access customer files?
Two layers of encryption protect stored files — application-level before storage and storage-level at rest within Everabyte's storage infrastructure — and direct access to stored objects does not reveal the original file contents. Your decryption key stays under your control for the operations you trigger: Everabyte services use decryption keys and process decrypted content only inside controlled, logged workflows — your own operations and the platform's disclosed scheduled integrity verification — and no operator can read your files interactively. For Managed Private Environment or custom-module deployments, your order form or data processing agreement states what Everabyte can access.
Q · 02Encryption
Q.Is data encrypted in transit and at rest?
Yes. TLS 1.3 protects data in transit, and stored data is protected by two encryption layers: application-level encryption (AES-256-GCM) before storage and a storage-level layer within Everabyte's storage infrastructure. Master keys are protected through platform-managed key management.
Q · 03Recovery
Q.How can I restore my encrypted files?
Your recovery passphrase enables you to restore your encrypted files through Everabyte's secure recovery process. Keep your recovery passphrase secure and follow the instructions available in your account.
Q · 04Backups
Q.How are backups protected?
Stored files keep application-level encryption, and the storage layer adds its own encryption at rest. Retention and Object Lock controls are available where enabled for the relevant storage configuration: retained objects cannot be modified or deleted until their configured retention period ends.
Q · 05Due diligence
Q.Do enterprise customers get security documentation?
Security information, architecture details, and trust documentation can be shared during customer due diligence based on the scope of the request and the deployment model.
Q · 06Hosting
Q.Where is customer data hosted?
Hosting location depends on the selected infrastructure and deployment setup. Regional options can be discussed based on performance, residency, and contractual requirements.
Why Everabyte
Why customers choose Everabyte.
Everabyte is designed for teams that want security, clarity, and dependable storage without unnecessary complexity.
Layered encryption
Two encryption layers protect stored files — application level before storage, storage level at rest — with platform-managed master key management.
Controlled operational access
Restricted, monitored, and logged administrative paths reduce internal risk.
Retention controls where enabled
Retention and Object Lock controls, where enabled for the relevant storage configuration and provider, protect retained objects until their retention period ends.
Trusted infrastructure foundations
High-availability environments with strong isolation and dependable security operations.
Clear answers for enterprise review
Documentation, scoping, and security review support tailored to deployment model.
Talk to the security team
Need architecture details, procurement answers, or support for a security review?
Everabyte can share the right information based on deployment model, data sensitivity, and compliance requirements. Reach out for architecture diagrams, scoping questions, or to set up a security review call.