CDN
CDN
cdnjs : Datenschutz, & EU Alternatives
cdnjs 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.
Last checked:
Is cdnjs GDPR compliant?
cdnjs 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?
Sovereignty Level: Level 0 of 4
US-Anbieter, US-Server. Voller CLOUD-Act-Zugriff. Bei jedem Schrems-Urteil fällt das Tool um.
- Level0
- Level1
- Level2
- Level3
- Level4
The five levels, from US-SaaS (Level 0) to fully sovereign (Level 4), we explain in detail here.
Contract & Subprocessor Chain
- 1.Cloudflare, Inc. (US, San Francisco CA)
Even if the main provider is based in the EU, a US subprocessor in this chain can trigger a third-country transfer. This is the core pitfall of .
Data Categories
What data does cdnjs 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.
meetergo Recommendation
JS-Bibliotheken selbst hosten oder über EU-CDN ausliefern
Public-CDNs wie cdnjs erzeugen mit jedem Page-Load eine US-Datenübertragung — selbst ohne aktiven Tracker. Schlankste Lösung: betroffene JS-Bibliotheken in den eigenen Build (npm + Webpack/Vite) integrieren. Alternative: EU-CDN wie Bunny.net (SI) oder ein Self-Hosted Reverse-Proxy.
GDPR-compliant providers
EU alternatives to cdnjs
Providers based in the EU or EEA. No third-country transfer, simpler DPA situation, TIA generally not required.
Bunny.net
🇸🇮EU-CDN mit vergleichbarer Latenz, ohne CLOUD-Act-Bezug.
Switch in ~3 days
Myra Security
🇩🇪Deutscher CDN- und Security-Provider.
Switch in ~7 days
3Q
🇩🇪Video platform with reliable scalable secure delivery.
Antares Project
🇩🇪Largest German infrastructure for digital education content.
Azin
🇳🇱Cloud deployment platform for devs to deploy apps.
Migration Plan
How to migrate away from cdnjs
The following steps are the typical path for this tool category. Order and time required depend on your specific setup.
- 1
Lower TTL of DNS entries (60 seconds)
- 2
Replicate cache and WAF rules in the EU alternative
- 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
cdnjs & Privacy: FAQ
Is cdnjs GDPR-compliant?
Is cdnjs GDPR-compliant?
Who is the contractual partner for cdnjs?
Who is the contractual partner for cdnjs?
What EU alternatives are there to cdnjs?
What EU alternatives are there to cdnjs?
Where is cdnjs data stored?
Where is cdnjs data stored?
What does the CLOUD Act mean for cdnjs users?
What does the CLOUD Act mean for cdnjs users?
Do I need a TIA for cdnjs?
Do I need a TIA for cdnjs?
How much effort is involved in switching away from cdnjs?
How much effort is involved in switching away from cdnjs?
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.
Note
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.