Your Data. Your Rules. Your Law.
European Data Storage. Managed by European Law
For many European organisations, knowing where data is stored, who can access it and which jurisdiction applies has become an important governance, security and compliance requirement.
GDPR does not impose a universal requirement that all personal data remain physically inside Europe; international transfers are legally possible under GDPR mechanisms.
The regulatory landscape
European data law is not what it was five years ago
Several European and international legal frameworks can influence how organisations design and govern their storage infrastructure. NIS2 does not apply to every organisation.
GDPR
In force since 2018
General Data Protection Regulation
GDPR establishes clear obligations around how personal data is stored, accessed, and protected. For storage infrastructure specifically, it requires:
Technical security measures
Article 32 — encryption, access control, integrity verification.
Data location and transfer governance
Organisations must understand where personal data is processed and ensure that any international transfers have an appropriate legal basis.
Audit trail capability
Appropriate logging and records can provide evidence of security controls and support accountability and incident investigation.
The right to erasure
Personal data must be technically deletable — traceably and verifiably.
GDPR fines reach up to 4% of global annual turnover — and enforcement has accelerated year on year since 2020.
NIS2
In force since 2026
Portuguese Cybersecurity Legal Framework
Transposed into Portuguese law by Decree-Law No. 125/2025, with implementation rules established by Regulation No. 756/2026.
Risk management measures
Technical controls proportionate to risk, including storage security.
Business continuity & backup
Documented recovery is now a regulatory requirement, not just practice.
Incident reporting
NIS2 introduces staged incident-notification obligations for covered entities, subject to the applicable legal framework and incident classification.
Supply chain accountability
Obligations extend to technology suppliers and service providers.
If your organisation falls within NIS2 scope — and many do — your storage architecture is now a compliance matter.
CLOUD Act
US law since 2018
The risk European businesses rarely discuss
US-based service providers may be subject to US legal requirements even when infrastructure is physically located in Europe. For organisations with strict sovereignty requirements, provider jurisdiction can therefore be an important architectural consideration alongside physical data location.
EU data centre ≠ EU jurisdiction
A US provider hosting in Europe may still be subject to US legal orders.
A board-level risk
For sensitive commercial, legal, or personal data.
The same software. Hardware you can trust.
Five data storage questions every CEO must be able to answer
These are not IT questions. They are governance, compliance, and business-continuity questions that land — ultimately — on the CEO’s desk.
Do you know, precisely, where your data is?
Most organisations cannot answer this with certainty once cloud providers, sub-processors and regional failover are involved.


Can you prove compliance in an audit?
GDPR and NIS2 audits are not theoretical. Authorities may request access logs, processing records and evidence of technical controls.
Who has access to your data — and do you control it?
“We set it up correctly at the start” is not an acceptable answer when user roles, contractors, and systems change continuously.


If something goes wrong, how quickly do you recover?
SanbrickOS supports recovery architectures based on snapshots, replication, backup integration and high availability.
Do you know what your storage will cost in year three?
Cloud storage costs grow with your data — and not linearly. Modest cloud bills frequently become three to five times higher within a few years, with no practical exit route.

The answer starts with architecture
Sovereignty is not a setting. It is an architectural decision.
One made before any purchase — and one that determines everything that follows. Two principles underpin a genuinely sovereign data infrastructure.
Ownership Over Access
Renting infrastructure from a foreign provider is not sovereignty, however the marketing describes it. Owning or directly controlling the physical and legal chain of custody of your data is.
Jurisdiction Over Geography
A server physically located in Europe, operated by a company subject to non-European law, does not remove jurisdictional risk. What matters is which law actually governs the provider.
These two principles are the foundation on which SanbrickOS was built.
From regulation to practice
How SanbrickOS can support technical requirements
| Regulatory requirement | What it demands | How SanbrickOS supports it |
|---|---|---|
| GDPR Art. 32 — Technical security | Encryption, access control, integrity assurance | AES-256 encryption at rest, access control, integrity verification built into SanbrickOS |
| GDPR — Right to erasure | Verifiable, traceable deletion of personal data | Storage administration capabilities can support organisational data-retention and deletion procedures. |
| GDPR — Audit readiness | Access logs and processing records for authorities | SanbrickOS provides audit logging for supported administrative, authentication and storage-management events. |
| NIS2 — Risk management | Technical controls proportionate to risk | Configurable security policies, network segmentation support, access hardening |
| NIS2 — Business continuity | Documented backup and recovery capability | SanbrickOS supports recovery architectures based on snapshots, replication, backup integration and high availability. Actual recovery time depends on deployment architecture, dataset size, incident scope and configured protection policies. |
| NIS2 — Incident response | Detect, contain, and report incidents promptly | Real-time monitoring, alert management, incident documentation support |
| Data residency | Data location and transfer governance | SanbrickOS can be deployed on customer-controlled European infrastructure, allowing the organisation to define and document its data location. |
| CLOUD Act exposure | Data outside reach of non-European legal orders | Reduces dependency on infrastructure operated under non-EU jurisdiction |
GDPR Art. 32 — Technical security
- What it demands
- Encryption, access control, integrity assurance
- How SanbrickOS supports it
- AES-256 encryption at rest, access control, integrity verification built into SanbrickOS
GDPR — Right to erasure
- What it demands
- Verifiable, traceable deletion of personal data
- How SanbrickOS supports it
- Storage administration capabilities can support organisational data-retention and deletion procedures.
GDPR — Audit readiness
- What it demands
- Access logs and processing records for authorities
- How SanbrickOS supports it
- SanbrickOS provides audit logging for supported administrative, authentication and storage-management events.
NIS2 — Risk management
- What it demands
- Technical controls proportionate to risk
- How SanbrickOS supports it
- Configurable security policies, network segmentation support, access hardening
NIS2 — Business continuity
- What it demands
- Documented backup and recovery capability
- How SanbrickOS supports it
- SanbrickOS supports recovery architectures based on snapshots, replication, backup integration and high availability. Actual recovery time depends on deployment architecture, dataset size, incident scope and configured protection policies.
NIS2 — Incident response
- What it demands
- Detect, contain, and report incidents promptly
- How SanbrickOS supports it
- Real-time monitoring, alert management, incident documentation support
Data residency
- What it demands
- Data location and transfer governance
- How SanbrickOS supports it
- SanbrickOS can be deployed on customer-controlled European infrastructure, allowing the organisation to define and document its data location.
CLOUD Act exposure
- What it demands
- Data outside reach of non-European legal orders
- How SanbrickOS supports it
- Reduces dependency on infrastructure operated under non-EU jurisdiction
The right hardware
Data sovereignty begins with software. It is completed by hardware
Sanbrick appliances are purpose-built to run SanbrickOS — pre-configured and validated for deployment in European environments. Three series cover the full range of organisational requirements.
Small business & SOHO
SanbrickOS in a compact format for edge deployments, branch offices and local data environments. The right architecture when simplicity, proximity to operations and direct support matter more than scale.
Mid-market
1U performance for workloads where rack footprint, speed and simplicity all count. Supports 2.5″ SATA, SAS and NVMe — the natural fit for fast file and block services without the complexity of larger chassis.
Enterprise & critical infrastructure
The primary Sanbrick appliance for enterprise workloads — available in three configurations, each optimised for a distinct storage profile: core capacity, high density, or all-flash performance.
Prefer to run SanbrickOS on your own hardware? That is equally supported.
Frequently asked questions
Questions, answered
Not necessarily. US-based service providers may be subject to US legal requirements even when infrastructure is physically located in Europe, so provider jurisdiction matters alongside physical data location.
Sanbrick is a Portuguese brand of CoreDevtek, operating under Portuguese and EU law. Customers can deploy SanbrickOS without relying on a US hyperscale cloud provider.
NIS2 scope is broader than the original directive and now includes many mid-sized companies in sectors like healthcare, education, energy and digital infrastructure. If in doubt, a compliance review can confirm your status.
A declaration is a policy document that asserts compliance. Technical controls — such as encryption, access control, logging and deletion procedures — are enforced by the platform itself and can help support those policies, independent of whether anyone remembers to follow them.
Most migrations use SanbrickOS replication to seed data in the background, with a short cutover window. Timelines vary by data volume, but a phased migration plan is standard practice.
Book a compliance review with a Sanbrick engineer — no obligation. We map your current exposure against GDPR, NIS2 and CLOUD Act risk and recommend next steps.

Your Data. Your Rules. Your Law.
Sanbrick — European Data Storage & Backup Software Solutions. Portuguese engineering. European standards. Local support.