Data Sovereignty

Your Data. Your Jurisdiction. Mathematically Proven.

Define which nodes store your data — by geography, provider, or certification. Transactions are physically isolated to your perimeter. Compliance is not a vendor promise — it's a cryptographic proof on-chain.

Why Data Sovereignty Matters

European regulation is clear: personal and sensitive data must stay within jurisdictions you control. The reality of most infrastructure makes that impossible to prove.

📜

GDPR & Schrems II

The GDPR requires that personal data of EU residents is processed lawfully and transparently. The Schrems II ruling invalidated the EU-US Privacy Shield, making transfers to US-controlled infrastructure legally precarious. If your cloud provider has a US parent, your data is exposed to the CLOUD Act — regardless of where the server sits.

CLOUD Act Exposure

The US CLOUD Act compels American companies to hand over data stored anywhere in the world when served with a warrant. Using AWS, Azure, or GCP means your data is one subpoena away from US government access — even if it is stored in Frankfurt or Paris. Contractual promises do not override US law.

🏛

Data Residency Requirements

Healthcare (HDS), finance (DORA, NIS2), and government sectors increasingly mandate that data physically resides within national borders. A "region picker" on a cloud console is not proof — it is a configuration setting that can change without your knowledge.

🔍

The Core Problem

Your data should physically stay where you decide, not where a vendor decides. Today, compliance is a promise in a PDF. Tomorrow's regulation demands mathematical proof. The gap between "we say we're compliant" and "anyone can verify we're compliant" is the gap ATSHI closes.

Most blockchains replicate data to every node on the planet. ATSHI lets you choose exactly which nodes touch your data.

Virtual Networks — How It Works

A virtual network is a subset of the ATSHI mainnet. You select which nodes participate, and transactions are replicated exclusively to those nodes — nowhere else.

  • Select nodes by geography — restrict your virtual network to nodes physically located in a specific region. EU only, France only, Germany only — you define the boundary. Data never leaves the jurisdiction you choose.
  • Select nodes by provider — choose infrastructure you trust. OVH only, Hetzner only, Scaleway + OVH — any combination. Your data only touches infrastructure from providers you have explicitly approved.
  • Select nodes by custom attributes — filter by any criteria that matters: certification level, hardware specification, operator identity, or any custom tag assigned to mainnet nodes.
  • Same ARCH consensus, restricted scope — your virtual network runs the same ATSHI protocol with the same ARCH consensus mechanism. The only difference is scope: transactions are validated and stored exclusively by your selected node subset.
  • Zero data leakage — physical isolation, not encryption — when a transaction is created inside a virtual network, it is replicated only to nodes belonging to that network. No data exchange with outside nodes. No exceptions. The data literally never exists on machines outside your perimeter.

Virtual Network Architecture

ATSHI Mainnet Hundreds of nodes across multiple countries and providers
Your Virtual Network A selected subset — e.g. 12 nodes in France on OVH
Outside Nodes Never receive your data — complete physical isolation

Isolation, Not Encryption

Most platforms encrypt data and broadcast it everywhere. ATSHI takes a fundamentally different approach: your data is physically confined to the nodes you choose.

Encryption Approach (Others)

Data is replicated to every node on the network, but encrypted. All nodes store your data — they just cannot read it. The data physically exists on machines you do not control, in jurisdictions you did not choose. A future cryptographic breakthrough or key compromise could expose everything retroactively.

Data everywhere, encrypted

Isolation Approach (ATSHI)

Data is replicated only to your selected nodes. Nodes outside your virtual network never receive the data at all — not encrypted, not hashed, not in any form. The data physically never exists on machines outside your perimeter. There is nothing to decrypt because there is nothing to intercept.

Data only on your nodes

Four Steps to Data Sovereignty

From definition to deployment in minutes — no separate chain, no dedicated infrastructure, no complex ceremony.

1

Define Your Network

Name your virtual network and set governance rules: who can administer it, who can submit transactions, and how membership changes are approved.

2

Select Node Criteria

Choose which mainnet nodes will participate. Filter by geographic location, cloud provider, certifications, or any custom attribute. Only matching nodes are included.

3

Deploy

Your virtual network is activated on the ATSHI mainnet. The selected nodes begin accepting transactions for your network. Same protocol, same consensus — isolated scope.

4

Transactions Are Isolated

Every transaction created in your virtual network is replicated exclusively to your node subset. Data never leaves the perimeter. Complete physical isolation is enforced at the protocol level.

Six Compliance Levels — Cryptographically Attested

Validators sign geographic and regulatory attestations that are anchored directly to the ATSHI mainnet. Every compliance claim is a living, verifiable cryptographic proof that updates in real time — not a PDF certificate buried in a drawer.

  • Cryptographic attestation — each validator signs proofs of geographic location, regulatory certification, and infrastructure provenance. These attestations are anchored on-chain and can be verified by anyone at any time.
  • Independent verification — any auditor, regulator, or counterparty can verify compliance independently without trusting anyone. The proof is mathematical, not legal.
  • Immutable audit trail — every compliance attestation is permanently recorded on-chain. If a validator falls out of compliance, the entire network knows instantly. Sovereignty is continuous and verifiable 24/7/365.

6 Compliance Levels

GDPR Standard Personal data within EEA — full data protection regulation compliance
GDPR Strict (Schrems II) No US/CN parent or subprocessor — strictest data sovereignty
France HDS Certified health data hosting for patient records & medical data
SecNumCloud ANSSI certification — EU capital ownership required
eIDAS 2.0 Qualified electronic trust service — EU-wide legal validity
GAIA-X Federated sovereign EU infrastructure — interoperable data spaces

Why ATSHI Data Sovereignty Changes Everything

Physical isolation, cryptographic proof, and full regulatory coverage — on a public mainnet.

🛡

True Physical Isolation

Data physically never leaves your defined perimeter. Not encrypted elsewhere — simply not there. You control exactly which machines hold your data, in which countries, on which providers.

Sovereignty

Cryptographic Compliance Proof

Every sovereignty claim is backed by cryptographic attestation anchored on-chain. Auditors verify math, not marketing materials. Compliance is provable, not promised.

Compliance
🛡

No US Cloud Act Exposure

No US parent company means zero exposure to US government data requests. Your data is governed exclusively by European law — period. No legal backdoors, no jurisdictional ambiguity.

Security

No Separate Chain Needed

Your virtual network runs on the ATSHI mainnet — same protocol, same consensus, same security model. No chain bootstrapping, no genesis ceremonies, no orphaned infrastructure to maintain.

Architecture
🏥

Healthcare & Finance Ready

HDS certification for patient data, DORA and NIS2 for financial institutions, MiFID compliance — all built into the protocol. Deploy regulated applications with confidence.

Regulated

Minutes to Deploy

Define your node criteria, set governance rules, and deploy. Your virtual network is live in minutes, not months. No hardware provisioning, no DevOps overhead, no chain bootstrapping.

Speed

ATSHI vs. The Competition

See how ATSHI Network stacks up against the incumbents on every dimension of data sovereignty and isolation.

Capability AWS / Azure / GCP Hyperledger Fabric Public Chains (ETH) ATSHI Network
Data Location US parent, CLOUD Act Depends on host Global, no control EU-only nodes, provable
Isolation Model VPC (same cloud) Channels None Virtual Networks (physical isolation)
GDPR Compliance Contractual Depends None Cryptographic proof
Sovereignty Proof None None None On-chain attestation
Health Data (HDS) Some providers No No Certified
SecNumCloud Very few No No Yes, EU capital
Setup Complexity Days-weeks Days-weeks N/A Minutes
Node Selection Region picker Manual Not possible Geography, provider, custom attributes

Where Data Sovereignty Makes the Difference

From regulatory compliance to enterprise data control — virtual networks solve real problems that encryption alone cannot address.

🇪🇺

GDPR Compliance

European personal data must stay in the EU. Create a virtual network restricted to nodes physically located in EU member states. Data never touches a server outside Europe — not encrypted on a US server, not stored anywhere outside your jurisdiction. True GDPR compliance by design, not by policy.

Regulatory
🏣

Enterprise Data Isolation

Enterprises need guarantees that their operational data is not co-located with competitors or untrusted parties. A virtual network gives you a dedicated perimeter on shared infrastructure — your data only exists on nodes you have vetted and approved. No shared storage, no shared replication.

Enterprise
🛒

Consortium Supply Chain

Multiple organizations in a supply chain need to share data — but only among themselves. Define a virtual network with nodes operated by consortium members. Suppliers, manufacturers, and distributors share a common ledger that is invisible to the rest of the network.

Supply Chain
🏥

Healthcare Data Sovereignty

Patient records and health data are subject to strict national regulations. Create a virtual network restricted to nodes within your country's borders, operated by certified healthcare infrastructure providers. Medical data physically never leaves the national perimeter.

Healthcare

Prove Your Sovereignty — Don't Just Claim It

Deploy on the only blockchain where data sovereignty is cryptographically verifiable. Stop relying on vendor promises. Start proving compliance with mathematics.