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

E-Signature

DocuSign : Datenschutz, & EU Alternatives

Contract documents and signatory data go through DocuSign (US corporation), even with EU hosting. CLOUD Act applies.

🇺🇸USAUS-JurisdiktionTeilweise ersetzbar

Last checked:

Is DocuSign GDPR compliant?

DocuSign 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
AWS / Azure (Global, EU-Region möglich)
Owner
DocuSign Inc.🇺🇸

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.

Contract & Subprocessor Chain

  1. 1.DocuSign Inc. (US, San Francisco)

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 DocuSign process?

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

  • Full contract documents (PDF content)
  • Identity data of signatories
  • Audit trail with IP, timestamp and geolocation
  • Attachments and supporting documents

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:

  • Contract parties and signatories
  • For B2B: management of the counterparty

Concrete Impact

What does this mean in practice?

Contract documents and the full audit trail are stored with a US provider. For contracts with German / EU corporates this is a real source of escalation.

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

E-signatures directly in the meetergo booking flow

meetergo's built-in e-signature covers the standard case: send a contract at the end of a booking, collect signature, auto-archive. For qualified eIDAS signatures: meetergo integrates with Yousign (FR) and eSignAnyWhere (IT).

How to implement it

Buchung → Vertrag → Signatur in einem Flow, ohne Tool-Wechsel.

Time-to-Value: Buchungs-Signatur sofort, Vollmigration 2–4 Wochen

Migration Plan

How to migrate away from DocuSign

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

  1. 1

    Migrate contract templates

  2. 2

    Rebuild signature workflow (order, reminders)

  3. 3

    Check audit trail requirements (qualified vs simple signature)

  4. 4

    Keep existing contracts in the old system, new ones in the new

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

DocuSign & Privacy: FAQ

Is DocuSign GDPR-compliant?

DocuSign 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 (DocuSign Inc.), 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 DocuSign?

The contract chain includes: DocuSign Inc. (US, San Francisco). 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 DocuSign?

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 DocuSign (E-Signatur). meetergo covers the core workflow and can fully replace DocuSign in many cases.

Where is DocuSign data stored?

According to provider information: AWS / Azure (Global, EU-Region möglich). 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 DocuSign 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 DocuSign Inc. is subject to the CLOUD Act, US law enforcement could theoretically access DocuSign 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 DocuSign?

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

How much effort is involved in switching away from DocuSign?

Time-to-value according to our migration database: Buchungs-Signatur sofort, Vollmigration 2–4 Wochen. Buchung → Vertrag → Signatur in einem Flow, ohne Tool-Wechsel.

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.