EuroComply
Sign up
Version 1.0 — Published 2026-05-11

EuroComply Sovereignty Disclosure

A public, dated, machine-readable record of every component in EuroComply's stack and its CLOUD Act exposure.

EU-hosted infrastructure by default. Mixed aggregate score — see table for per-vendor detail.
Last reviewed: 2026-05-11

What is EuroComply's sovereignty posture?

This page is the source of truth for EuroComply's data sovereignty claims. It is versioned, dated, and cross-referenceable with the CLOUD Act Exposure Score methodology published at /cloud-act-scores/methodology. Each row in the stack table below identifies a specific vendor, its legal jurisdiction, the physical location of data it handles, and the CLOUD Act Exposure Score (0–100) for that component. Scores are calculated using the five-factor weighted model described in the methodology. Version 1.0 is frozen: no inputs, weights, or tier boundaries will change without issuing v1.1 with a full migration changelog. Material vendor changes — such as switching cloud providers or registrars — will trigger a version bump and a new “Last reviewed” date. The prior version will be preserved at /sovereignty/v1.

Stack Disclosure

9 components. Production data layers (LLM, Database, Hosting, Payments) weighted 2× in the aggregate.

LLM

Compliance chat

8Sovereign
Vendor: Mistral AI
HQ: Paris, France
Jurisdiction: French SAS
Data residency: Paris + EU only
French SAS, EU-only inference, no US parent entity.
Database

Production Postgres

38Mixed
Vendor: Supabase
HQ: Frankfurt, Germany (project); Singapore Pte Ltd (HQ)
Jurisdiction: Singapore Pte Ltd with EU project hosted in AWS Frankfurt
Data residency: Frankfurt, Germany
Supabase HQ is Singapore-incorporated, not EU. AWS Frankfurt provides EU physical residency but the infrastructure operator (AWS) is US-jurisdiction. Score reflects the layered exposure.
Hosting

Web frontend

45Mixed
Vendor: Vercel
HQ: San Francisco, USA
Jurisdiction: US Inc (Delaware)
Data residency: Frankfurt (Europe Sovereign region)
EU Frankfurt region available and in use; however Vercel Inc is Delaware-incorporated and subject to US jurisdiction. CLOUD Act exposure is theoretically present via the US parent.
Email

Transactional + nurture

10Sovereign
Vendor: Brevo (Sendinblue)
HQ: Paris, France
Jurisdiction: French SAS
Data residency: Paris
French SAS incorporated in Paris, EU-only data processing, no US parent or US subsidiary with system access.
Payments

Subscriptions

35Mixed
Vendor: Paddle
HQ: London, UK
Jurisdiction: UK Ltd
Data residency: UK + EU regions
Post-Brexit UK. UK adequacy decision still in place as of 2026-05-11. Not US-jurisdiction. Paddle acts as Merchant of Record, holding customer payment data under UK law rather than EU law directly.
Analytics

Privacy-respecting analytics

5Sovereign
Vendor: Plausible
HQ: Tallinn, Estonia
Jurisdiction: Estonian OÜ
Data residency: Tallinn, Estonia
Estonian OÜ, EU-only infrastructure, no cookie, no personal data, no US parent entity.
Workflow automation

n8n automation

10Sovereign
Vendor: n8n.io GmbH
HQ: Berlin, Germany
Jurisdiction: German GmbH
Data residency: Self-hosted on EU infrastructure by EuroComply
German GmbH. EuroComply self-hosts the n8n instance on EU servers — no SaaS cloud data transfer to n8n.io. German company law applies.
Domain registrar / DNS

DNS

70US-Dominant
Vendor: Cloudflare Registrar
HQ: San Francisco, USA
Jurisdiction: US Inc (Delaware)
Data residency: n/a (registry data only)
US-incorporated. Registry data (nameservers, WHOIS) held under US jurisdiction. Does not hold production customer data. Score would reduce materially with migration to a French or German registrar (OVHcloud, IONOS). This is a planned improvement.
Error tracking

Application errors

5Sovereign
Vendor: Self-hosted GlitchTip
HQ: n/a (own infrastructure)
Jurisdiction: n/a — EuroComply-operated
Data residency: EU servers (EuroComply-controlled)
Open-source GlitchTip self-hosted by EuroComply on EU infrastructure. No third-party vendor receives error data. EuroComply is the sole data controller.

Weighted aggregate score

27
/100
Mixed tier

Weighted average across 9 stack components. Production data layers (LLM, Database, Hosting, Payments) counted at 2× weight. Lower is better. Methodology: /cloud-act-scores/methodology.

Weighted sum: (8×2)+(38×2)+(45×2)+(10×1)+(35×2)+(5×1)+(10×1)+(70×1)+(5×1) = 352
Total weight units: 13 · 352 ÷ 13 = 27 (rounded)

Verification Methodology

Each claim in this disclosure is verifiable against a public primary source. EuroComply does not accept vendor self-attestation without a corroborating public record. The following primary sources were used to verify each component:

  • Mistral AIFrench commerce register — Pappers / Infogreffe (SIREN 952223452)
  • SupabaseACRA Singapore commercial register (UEN 202127121H); AWS Frankfurt (eu-central-1) region disclosure
  • VercelDelaware Secretary of State / SEC filings; Vercel EU region documentation
  • Brevo (Sendinblue)Infogreffe / Pappers FR (SIREN 498774127)
  • PaddleUK Companies House (Company No. 07430028); UK adequacy decision (Commission Implementing Decision (EU) 2021/1772)
  • PlausibleEstonian Business Register (Reg. 14709282)
  • n8n.io GmbHHandelsregister Berlin-Charlottenburg (HRB 226969 B)
  • Cloudflare RegistrarDelaware SoS / SEC EDGAR; Cloudflare Inc 10-K filing
  • Self-hosted GlitchTipSelf-attested; GlitchTip source code publicly auditable at gitlab.com/glitchtip/glitchtip-backend

What we explicitly avoid

The following vendors are not used anywhere in the EuroComply stack for production data handling, as of the date of this disclosure:

AWS (direct — except as Supabase dependency)Google CloudMicrosoft AzureOpenAI (US)Anthropic (US)Stripe (US)Auth0 (US)Datadog (US)Segment (US)Twilio (US)SendGrid (US)LaunchDarkly (US)PagerDuty (US)

Note: EuroComply's compliance chat uses Mistral AI (French SAS), not OpenAI or Anthropic. Authentication is handled natively by Supabase Auth (Frankfurt project), not Auth0 or Clerk. Error tracking is self-hosted GlitchTip, not Sentry or Datadog.

Versioning and Change Log

VersionPublishedChanges
v1.02026-05-11Initial frozen publication. 9 stack components, weighted aggregate score, 4-tier classification.

This disclosure is frozen at v1.0. The changelog is maintained in git history: github.com/eurocomply/sovereignty-disclosure

Material changes to this disclosure — defined as a vendor change, jurisdiction change, or data residency change for any component — trigger a version bump. v1.1+ will preserve v1.0 at /sovereignty/v1. Cosmetic corrections (typos, formatting) may be made within the current version with an updated “Last reviewed” date.

Next step — compare

Read our sovereignty disclosure

Score your vendor stack against EuroComply's CLOUD Act exposure methodology — free, no signup.

Read our sovereignty disclosure

This disclosure is published by EuroComply (Code Tide Unipessoal LDA) in the interest of transparency and EU digital sovereignty. It is informational only and does not constitute legal advice. CLOUD Act Exposure Scores are assessments based on publicly verifiable corporate and infrastructure facts. Consult qualified legal counsel for a legal opinion specific to your organisation's situation.

v1.0 published: 2026-05-11 · License: CC BY 4.0 · Contact: [email protected]