Sovereignty Washing

Sovereignty Washing (n.) — Rebranding American or Chinese cloud infrastructure as "European sovereign" without changing its ownership or jurisdiction.

The mechanics are simple and by now standardised. A hyperscaler creates a European subsidiary, a European joint venture, or a "sovereign region" — European staff, European data centres, a European flag on the landing page. Marketing announces digital sovereignty. Procurement announces compliance. What has not changed: the ownership chain terminates in Delaware or Shenzhen, and jurisdiction follows ownership. A US-owned entity is reachable by the CLOUD Act wherever its servers sit and whatever its subsidiary is named; a Chinese-owned entity is reachable by the National Intelligence Law on the same logic.

Sovereignty washing is to digital policy what greenwashing is to climate policy: the substitution of the vocabulary of the goal for the substance of it — with the added hazard that the vocabulary actively suppresses demand for the substance. Every tender that accepts a washed offering as "sovereign" is a tender a genuinely European provider did not win, and a capability Europe did not build.

Development

Applied from May 2026 in commentary on the EU's Tech Sovereignty Package, which permitted member states to count hyperscaler "sovereign regions" toward European sovereignty targets. The term drew the obvious parallel to greenwashing and proposed the test that exposes it: the Ownership-Control Criterion — ask who owns the entity, not where the servers are or what the subsidiary is called.

Implications

The test for any sovereignty claim is one question: if a foreign court issues a lawful order to the ultimate parent, can it reach this data or this service? If yes, the offering is foreign infrastructure with European staging, and calling it sovereign is washing. The Accusation Audit tracks the gap between the EU's sovereignty language and this test — beginning with the Digital Sovereignty Package audit.

First public appearance

First used publicly on Bluesky (@jpahonen.eurosky.social); the origin thread will be linked here permanently.