Sovereignty Scan
Scan
Sovereignty Scan/Vendors/Let's Encrypt
Risk indicator, not a GDPR compliance verdict. Point-in-time assessment based on public web stack signals.Methodology & LimitationsCorrect listing / submit response
Let's Encrypt-Logo

CDN

Let's Encrypt : Datenschutz, & EU Alternatives

Let's Encrypt is subject to US law (CLOUD Act / FISA 702). GDPR-compliant use is only possible with a valid DPA, Standard Contractual Clauses (SCCs) and a Transfer Impact Assessment (TIA). For sensitive data, an EU alternative is the more robust choice.

🇺🇸USAUS-Jurisdiktion

Last checked:

Is Let's Encrypt GDPR compliant?

Let's Encrypt is subject to US law (CLOUD Act / FISA 702). GDPR-compliant use is only possible with a valid DPA, Standard Contractual Clauses (SCCs) and a Transfer Impact Assessment (TIA). For sensitive data, an EU alternative is the more robust choice.

Vendor Profile

Who is the contractual partner?

Jurisdiction
USA
Hosting
n/a (CA)
Owner
Internet Security Research Group (ISRG)🇺🇸

Sovereignty Level: Level 0 of 4

US-Anbieter, US-Server. Voller CLOUD-Act-Zugriff. Bei jedem Schrems-Urteil fällt das Tool um.

  1. Level0
  2. Level1
  3. Level2
  4. Level3
  5. Level4

The five levels, from US-SaaS (Level 0) to fully sovereign (Level 4), we explain in detail here.

Data Categories

What data does Let's Encrypt process?

In typical use, the following data categories arise. Which ones are relevant for you depends on your setup and scope of use.

  • Every HTTP request to your website (URL, referrer, IP)
  • Caching rules and edge logs
  • For WAF: active content inspection

Data Subjects

Who is affected by the processing?

Under Art. 30 GDPR, you must document the categories of data subjects per processing activity. In typical use, these include:

  • All website visitors with request metadata

Concrete Impact

What does this mean in practice?

Every HTTP request to your website (URL, IP, referrer) is routed through US edge infrastructure. Granular browsing profile of all visitors.

Note: This is a risk description, not a specific incident. Whether access occurred in your case depends on many factors. What can be documented: the risk must be named in your TIA and mitigated with additional measures.

GDPR-compliant providers

EU alternatives to Let's Encrypt

Providers based in the EU or EEA. No third-country transfer, simpler DPA situation, TIA generally not required.

Bunny.net-Logo

Bunny.net

🇸🇮

EU-CDN mit vergleichbarer Latenz, ohne CLOUD-Act-Bezug.

Switch in ~3 days

Myra Security-Logo

Myra Security

🇩🇪

Deutscher CDN- und Security-Provider.

Switch in ~7 days

3Q-Logo

3Q

🇩🇪

Video platform with reliable scalable secure delivery.

Antares Project-Logo

Antares Project

🇩🇪

Largest German infrastructure for digital education content.

Azin-Logo

Azin

🇳🇱

Cloud deployment platform for devs to deploy apps.

Migration Plan

How to migrate away from Let's Encrypt

The following steps are the typical path for this tool category. Order and time required depend on your specific setup.

  1. 1

    Lower TTL of DNS entries (60 seconds)

  2. 2

    Replicate cache and WAF rules in the EU alternative

  3. 3

    DNS cutover on weekend with rollback plan

We help with migration planning at no cost: 30 minutes with a data protection specialist to prioritise and define a migration sprint. Book appointment

Frequently Asked Questions

Let's Encrypt & Privacy: FAQ

Is Let's Encrypt GDPR-compliant?

Let's Encrypt can be used in a GDPR-compliant way if a valid DPA is in place, Standard Contractual Clauses (SCCs) are signed, and a Transfer Impact Assessment (TIA) has been conducted. However, the provider is headquartered in the US (Internet Security Research Group (ISRG)), so the CLOUD Act and FISA 702 continue to apply. This is true even when data is stored in an EU data centre. For sensitive data or strict oversight (public authorities, healthcare, large corporates), switching to an EU provider is often preferred.

Who is the contractual partner for Let's Encrypt?

The contracting party according to the DPA is Internet Security Research Group (ISRG). The vendor profile above shows the exact ownership chain including subprocessors.

What EU alternatives are there to Let's Encrypt?

There are several GDPR-compliant EU alternatives. They are listed under "EU Alternatives" on this page. The selection is tailored to the feature set of Let's Encrypt (Zertifikat). meetergo covers the core workflow and can fully replace Let's Encrypt in many cases.

Where is Let's Encrypt data stored?

According to provider information: n/a (CA). Note: even an EU data centre does not protect against the CLOUD Act when the parent company is in the US. This is the core finding of the Schrems II decision.

What does the CLOUD Act mean for Let's Encrypt users?

The US CLOUD Act (Clarifying Lawful Overseas Use of Data Act, 2018) allows US authorities to request data from US companies regardless of the physical storage location. If Internet Security Research Group (ISRG) is subject to the CLOUD Act, US law enforcement could theoretically access Let's Encrypt data stored in Frankfurt without involving EU authorities. The EDPB Recommendations 01/2020 therefore require additional safeguards or a switch to an EU provider.

Do I need a TIA for Let's Encrypt?

Yes, in most cases. Since Schrems II (July 2020), a Transfer Impact Assessment is mandatory for US providers when personal data is transferred. The TIA documents US law, practical risks (NSA access, subpoenas) and additional measures (encryption, pseudonymisation). Only a valid TIA makes the use of Let's Encrypt legally defensible.

How much effort is involved in switching away from Let's Encrypt?

Migration effort depends on your specific setup: typically between a few business days (booking, forms) and several weeks (CRM, hosting). The roadmap below shows the typical order.

Related Vendors

More tools in CDN

Next Step

Which tools are running on your website?

60 seconds, no login: the Sovereignty Scan shows all detected vendors with jurisdiction, risk, and matching EU alternatives.

To the ScanMethodology

Note

Hinweis

Risiko-Indikator, keine Rechtsberatung.

Der Sovereignty Scan wertet öffentlich erreichbare Signale aus (HTML der Startseite und Rechtsseiten, DNS-, MX-, SPF- und ASN-Daten) und vergleicht sie mit unserer Datenbank von ca. 3.000 Anbietern. Die Zuordnung von Tool zu Eigentümer und Jurisdiktion basiert auf öffentlichen Quellen (Impressum, Datenschutzerklärung, Wappalyzer, RIPE/ARIN-Registrierungen) und ist als Erstindikation zum Stichtag der Auswertung gedacht, nicht als rechtsverbindliche Bewertung.

Die Note A–E ist ein Risiko-Indikator, kein DSGVO-Konformitätsurteil. Für eine konkrete DSGVO-Bewertung, insbesondere für Auftragsverarbeitungsverträge (AVV/DPA), Standardvertragsklauseln (SCC) und Transfer Impact Assessments (TIA), wenden Sie sich bitte an Ihren Datenschutzbeauftragten oder eine externe Rechtsberatung. meetergo trifft keine Aussage darüber, ob ein konkreter Anbieter in einem konkreten Anwendungsfall DSGVO-konform eingesetzt werden kann.

Korrektur & Stellungnahme: Wenn Sie Domain-Inhaber, Datenschutzbeauftragter oder Pressestelle der bewerteten Domain sind und die hier gezeigten Signale nicht Ihrer aktuellen Tool-Konfiguration entsprechen, nehmen wir Korrekturen auf und passen die Anzeige nach Prüfung umgehend an.

Methodik & GrenzenListing korrigieren / Stellungnahme einreichen