Risk indicator, not a GDPR compliance verdict. Point-in-time assessment based on public web stack signals.Methodology & LimitationsCorrect listing / submit response
jsDelivr-Logo

CDN

jsDelivr : Datenschutz, & EU Alternatives

jsDelivr is EU/EEA-based: no third-country transfer at the primary vendor. Still check the subprocessor list.

🇪🇺EUDrittlandtransfer prüfen

Last checked:

Is jsDelivr GDPR compliant?

jsDelivr is EU/EEA-based: no third-country transfer at the primary vendor. Still check the subprocessor list.

Vendor Profile

Who is the contractual partner?

Jurisdiction
EU
Hosting
Multi-CDN: Cloudflare, Fastly, Bunny, G-Core (load-balanced)
Owner
Prospect One sp. z o.o. (jsDelivr-Maintainer)🇪🇺

Sovereignty Level: Level 3 of 4

EU-Anbieter mit US-Subprozessoren. Vertragspartner ist EU, aber ein einzelner US-Subprozessor reichert das Setup wieder mit Drittland-Risiko an.

  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.

Contract & Subprocessor Chain

  1. 1.Prospect One sp. z o.o. (Polen, EU)
  2. 2.Cloudflare (US-Subprozessor)
  3. 3.Fastly (US-Subprozessor)
  4. 4.Bunny.net (Slowenien, EU-Subprozessor)

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 jsDelivr 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 EU-CDN pinnen

jsDelivr leitet Traffic ohne Garantie an US-CDNs weiter (Cloudflare/Fastly als Hauptträger). DSGVO-sauberste Lösung: betroffene Bibliotheken in den eigenen Build integrieren. Alternativ direkt Bunny.net (SI) als Quelle nutzen.

Migration Plan

How to migrate away from jsDelivr

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

jsDelivr & Privacy: FAQ

Is jsDelivr GDPR-compliant?

jsDelivr 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 (Prospect One sp. z o.o. (jsDelivr-Maintainer)), 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 jsDelivr?

The contract chain includes: Prospect One sp. z o.o. (Polen, EU) · Cloudflare (US-Subprozessor) · Fastly (US-Subprozessor) · Bunny.net (Slowenien, EU-Subprozessor). The legal parent entity is decisive for data protection. Even if an EU subsidiary signs the DPA, a US subprocessor in the chain can trigger third-country transfer obligations.

What EU alternatives are there to jsDelivr?

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 jsDelivr (JavaScript-CDN). meetergo covers the core workflow and can fully replace jsDelivr in many cases.

Where is jsDelivr data stored?

According to provider information: Multi-CDN: Cloudflare, Fastly, Bunny, G-Core (load-balanced). 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 jsDelivr 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 Prospect One sp. z o.o. (jsDelivr-Maintainer) is subject to the CLOUD Act, US law enforcement could theoretically access jsDelivr 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 jsDelivr?

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 jsDelivr legally defensible.

How much effort is involved in switching away from jsDelivr?

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.

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

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.