OpenAI DPA data processing addendum Art. 28 GDPR review for Germany
tools

OpenAI DPA: Yes — What the OpenAI Data Processing Addendum Covers

Does OpenAI offer a DPA under GDPR Art. 28?

Yes. OpenAI publishes a Data Processing Addendum under GDPR Art. 28 at openai.com/policies/data-processing-addendum/, effective January 1, 2026. It supplements the OpenAI Services Agreement, names OpenAI OpCo, LLC or OpenAI Ireland Ltd. as contracting party, and relies on EU SCCs for transfers.

  • The OpenAI DPA is public: policy page, PDF download, and a web form for a countersigned copy.
  • EEA and Swiss customers, including Germany, contract with OpenAI Ireland Ltd.; others with OpenAI OpCo, LLC.
  • Transfers rely on the 2021 EU SCCs plus the UK Addendum; US processing makes your transfer assessment mandatory.

Yes — OpenAI offers a Data Processing Addendum (DPA) under GDPR Art. 28, published openly at openai.com/policies/data-processing-addendum/. The document supplements the OpenAI Services Agreement, and the current version — updated December 1, 2025, effective January 1, 2026 — names OpenAI OpCo, LLC as contracting party, or OpenAI Ireland Ltd. when the customer is based in the EEA or Switzerland, which includes Germany. It covers the full Art. 28 processor framework: documented instructions, confidentiality, security, subprocessor control with a 30-day objection right, deletion, annual audits, and EU Standard Contractual Clauses for transfers.

This page is a document companion: it walks through the OpenAI DPA clause by clause, maps it against the Art. 28 GDPR checklist, and shows how to fold it into a German procurement file. This page provides general information and is not legal advice for a specific deployment. For the broader vendor review — training defaults, data residency, ZDR — see our OpenAI API overview; for the German-language companion, see ChatGPT AVV.

What the OpenAI DPA covers: clause-level index

The OpenAI DPA is a compact document — six sections plus a Schedule of Processing — but it addresses each mandatory element of Art. 28 GDPR. Legal and privacy teams should verify every row against the actual deployment instead of treating the DPA as a checkbox:

DPA sectionWhat it providesWhat to verify for your deployment
Preamble + §1 (Details)Contracting party: OpenAI OpCo, LLC; OpenAI Ireland Ltd. for EEA/Swiss customers. OpenAI acts as data processor; processing details sit in Schedule 1That your order or account sits under the Services Agreement, and which entity actually contracts with you
§2.1–2.2 Instructions and noticesYour documented instructions are the DPA, the Agreement, and configuration choices made in the Services; OpenAI must flag instructions it considers unlawful and notify you of binding law-enforcement requestsYour internal usage rules and prompt policies, because they form part of the instructions
§2.3–2.5 Confidentiality, data subject requests, securityPersonnel confidentiality duties; assistance with access and deletion requests, including redirection; security measures as set forth in the AgreementYour own response procedures for data subject requests, and the security documentation referenced in the Agreement
§2.6–2.8 Assistance, breaches, auditsReasonable assistance including DPIA support; breach notification without undue delay; privacy and security documentation on written request and audits limited to once per yearHow audit evidence reaches you in practice, and whether annual audit rights match your sector requirements
§2.9–2.10 SubprocessorsGeneral authorization to engage the list at platform.openai.com/subprocessors; change notice via blog post, service notification, or email; 30-day objection window; termination with refund if unresolved; liability flow-downArchiving the current subprocessor list — Microsoft Azure is the infrastructure layer — and calendarizing the objection mechanism
§2.11 Return or deletionReturn or deletion of customer data at your instruction after termination, unless retention is legally requiredDeletion settings inside the Services, which remain your configuration responsibility under §3.3
§3 Customer obligationsYou warrant notices, consents, and authorizations for the data you submit; configurations such as retention and deletion are your design decisionsPrivacy notices, lawful basis, and retention configuration on your side
§4 International transfersEEA and Swiss data: processed under OpenAI Ireland Ltd. with SCCs or an Art. 45 adequacy decision for onward transfers. UK data: OpenAI OpCo, LLC with the SCCs as amended by the UK AddendumCountries involved, support access, and your own transfer impact assessment
§5 US privacy lawsCCPA service-provider commitments: no sale or share of personal data, de-identified data rules, purpose limitsRelevant only if US state privacy laws apply to you
§6 + Schedule 1Definitions (Customer Data, SCCs, Sub-Processor List, UK Addendum) and the processing record: nature, duration, data categories, data subjects, frequencyThe Schedule 1 statement that no sensitive data is intended to be transferred against your actual data categories

Two provisions deserve special attention from German buyers. First, the contracting-entity split: EEA and Swiss customers contract with OpenAI Ireland Ltd., yet §4.2 routes UK data through OpenAI OpCo, LLC, and Schedule 1 names the San Francisco entity as data importer with the DPO contact at [email protected] — a structure your records should mirror. Second, the sensitive-data statement in Schedule 1: OpenAI declares that no sensitive data is intended to be transferred unless a user includes it unexpectedly in unstructured data. That is a planning constraint, not a prohibition clause — HR data, health data, and other Art. 9 GDPR material do not belong in an OpenAI workflow without a separate, deeper review.

GDPR procurement guidance: where the OpenAI DPA sits in your processor chain

A German buyer should treat the OpenAI DPA as one layer in a three-layer stack: the Services Agreement (commercial terms), the DPA (processor terms), and your own documentation (controller duties). The review that turns the DPA into a defensible deployment record:

  1. Fix the contract path. Confirm the DPA is incorporated into the Services Agreement that governs your account or Order Form — the preamble makes acceptance effective by clicking “I agree,” accepting an Order Form, or using the Services. Enterprise buyers should attach the executed copy to the order file.
  2. Treat your configuration as contract. Under §2.1, your configuration choices are documented instructions; under §3.3, retention and deletion design is your responsibility. Record both in the deployment file, because they define what OpenAI actually does with personal data.
  3. Document transfers honestly. Standard OpenAI processing runs on US infrastructure through Microsoft Azure, so the SCC route in §4.1 applies. Your transfer impact assessment remains mandatory.
  4. Calendar the subprocessor mechanism. Save the current list from platform.openai.com/subprocessors with its review date, subscribe to change notifications, and note the 30-day objection window.
  5. Register the deployment. Enter the OpenAI deployment in your Art. 30 record of processing activities, referencing the DPA version (effective January 1, 2026) and the contracting entity.

For the full procurement framework — vendor assessment criteria, documentation templates, and sign-off workflows — see our GDPR AI procurement guide. German-speaking teams will find the same framework in our DSGVO-KI-Beschaffung guide.

Art. 28 GDPR checklist for the OpenAI DPA

Article 28(3) GDPR prescribes the minimum content of a processor agreement. Applied to the OpenAI DPA, the checklist looks like this:

  • Processing on documented instructions — §2.1: the DPA, the Agreement, and your configuration choices form the instruction set
  • Confidentiality commitments — §2.3: personnel are bound to confidentiality or a statutory duty
  • Security measures — §2.5: organizational and technical measures “as set forth in the Agreement”; cross-check against the published security documentation and your Art. 32 GDPR requirements
  • Subprocessor regime — §2.9–2.10: published list, general authorization, 30-day objection, comparable flow-down obligations, OpenAI remains liable
  • Data subject rights assistance — §2.4: notification, redirection authorization, and technical-organizational assistance
  • Deletion or return — §2.11: at your instruction after termination, subject to legal retention
  • Audit and information duties — §2.8: documentation once per year on written request; audits once per year under NDA, or audit-report summaries where permitted
  • Transfer safeguards — §4: EU SCCs (June 4, 2021) for EEA/Swiss data, UK Addendum for UK data; your TIA completed separately

If any checklist point cannot be answered from the DPA plus OpenAI’s published documentation, ask the vendor in writing before rollout — written answers become part of the procurement record.

How to obtain and sign the OpenAI DPA

OpenAI keeps the whole path public and ungated, which is faster than vendors that release their DPA only inside a customer portal:

  1. Review the policy page at openai.com/policies/data-processing-addendum/ — it shows the current version, its effective date, and a link to the previous version for diffing.
  2. Download the PDF via the Download PDF button (served from cdn.openai.com/pdf/openai-data-processing-addendum.pdf) and save it with the access date into the procurement file.
  3. Execute a signed copy if your procurement rules require more than click-acceptance: the Execute Data Processing Agreement link on the policy page opens a public Ironclad form that produces a countersigned DPA — the fastest route to a signed “OpenAI DPA form” without engaging sales.
  4. Record the version — “Updated December 1, 2025, effective January 1, 2026” plus the contracting entity — in your vendor management system and Art. 30 register.
  5. Re-verify at renewal — re-download, compare against the archived copy, and check whether the previous version has advanced.

For comparison, the Anthropic DPA is incorporated into commercial terms and accessed through a portal, the Cursor DPA publishes a standalone addendum with its own sensitive-data prohibition, and the ChatGPT Enterprise page covers the enterprise procurement scope.

Is there a separate DPA for Azure OpenAI?

No — the OpenAI DPA does not cover the Azure OpenAI Service. That service is contracted with Microsoft, so the governing processor document is Microsoft’s Data Protection Agreement under the Microsoft Product Terms, and EU data-center region selection changes the transfer picture entirely. If EU data residency is a hard requirement, evaluate the Azure OpenAI Service as a distinct procurement track with its own DPA review, or compare residency options in our OpenAI API overview. Treat the two DPAs as separate documents in separate files — a signed OpenAI DPA adds nothing to an Azure OpenAI deployment.

When the OpenAI DPA is not enough

The DPA answers the processor-contract question. It does not answer the deployment question. These obligations remain with you as the controller:

  • Legal basis (Art. 6 GDPR) — the DPA never provides your lawful basis for processing.
  • Record of processing (Art. 30 GDPR) and DPIA (Art. 35 GDPR) — document the deployment yourself; large-scale or sensitive workflows may require an impact assessment regardless of the DPA.
  • Employee data and works council duties — rollouts that touch employee workflows can trigger co-determination rights under section 87(1) no. 6 BetrVG.
  • EU AI Act deployer duties — if OpenAI models feed a high-risk AI system, deployer obligations sit on top of GDPR compliance.

Compound Law advises businesses, startups, and in-house teams in Germany on AI procurement, DPA and AVV review, transfer assessments, and vendor governance. If you want us to review your OpenAI deployment or another AI vendor contract before rollout, contact us.

Related Tool Guides

Claude Team vs Enterprise plan comparison table for German businesses
tools

Claude Team vs Enterprise (2026): Pricing, Seats & GDPR

Claude Team vs Enterprise compared for 2026: seat pricing, seat minimums, SSO, GDPR DPA and EU data residency — and which plan fits your business in Germany.

Salesforce DPA data processing addendum Art. 28 GDPR review for Germany
tools

Salesforce DPA: Yes — What the SFDC Data Processing Addendum Covers

Yes, Salesforce publishes a Data Processing Addendum on its legal hub. What the Salesforce DPA covers under GDPR Art. 28 — and how German buyers execute it.

Canva DPA data processing addendum reviewed under Article 28 GDPR
tools

Does Canva Offer a DPA? Yes — Canva DPA Guide for Germany

Yes — Canva provides a Data Processing Addendum on paid plans. See what the Canva DPA covers clause by clause: SCCs, subprocessors, audits, German-law gaps.

ElevenLabs DPA data processing addendum reviewed under Article 28 GDPR
tools

Does ElevenLabs Offer a DPA? Yes — ElevenLabs DPA Guide for Germany

Yes — ElevenLabs publishes a Data Processing Addendum at elevenlabs.io/dpa. What the ElevenLabs DPA covers clause by clause under Article 28 GDPR.

Cursor DPA data processing agreement Art. 28 GDPR review for Germany
tools

Cursor DPA: Yes — What the Anysphere Data Processing Agreement Covers

Yes, Cursor offers a DPA at cursor.com/terms/dpa. What the Cursor data processing agreement covers under GDPR Art. 28 — and how German buyers should review it.

Synthesia GDPR compliance facts: AI video training policy, DPA, and EU data storage
tools

Synthesia GDPR: Training, DPA & German Compliance Facts

No — Synthesia does not train on customer content. GDPR-usable for German firms: Art. 28 DPA and EU storage in Ireland. What to verify before rollout.

Tool Library

Browse More AI Tools by Topic

Compare more tools, privacy issues, and deployment scenarios in the full AI tool library.

View all AI tools

Frequently asked questions

Yes. OpenAI publishes a Data Processing Addendum addressing the Art. 28 GDPR processor requirements at openai.com/policies/data-processing-addendum/. The current version is effective January 1, 2026 and supplements the OpenAI Services Agreement. EEA and Swiss customers contract with OpenAI Ireland Ltd.; everyone else with OpenAI OpCo, LLC. Sufficiency depends on data, transfers, and workflow.

The policy page at openai.com/policies/data-processing-addendum/ has a Download PDF button, served from cdn.openai.com/pdf/openai-data-processing-addendum.pdf. No registration or sales contact is required. Save the reviewed version with its date into the procurement file and re-download at renewal — OpenAI revises the document and keeps the previous version published for comparison.

Yes. Beyond click-acceptance through the Services Agreement, OpenAI offers a public execution form — the Execute Data Processing Agreement link on the policy page opens an Ironclad form that produces a countersigned copy for your records. Procurement teams that need a signed document rather than a click-accepted term should use that form and archive the executed PDF.

No OpenAI-issued DPA applies to the Azure OpenAI Service. The service is contracted with Microsoft, so the Microsoft Data Protection Agreement under the Microsoft Product Terms is the governing processor document, with EU data-center region options. If EU data residency drives your OpenAI procurement, compare the Azure OpenAI Service separately from this DPA.

OpenAI Ireland Ltd. The DPA provides that customers based in an EEA country or Switzerland enter into the DPA with OpenAI Ireland Ltd., and Germany is in the EEA. Customers elsewhere contract with OpenAI OpCo, LLC of San Francisco. Note the asymmetry: UK data is processed under OpenAI OpCo, LLC even when the customer contracts with the Irish entity.

Transfers out of the EEA and Switzerland rely on the EU Standard Contractual Clauses adopted June 4, 2021, or on an adequacy decision under Art. 45 GDPR; UK data uses the SCCs as amended by the UK Addendum. Because standard OpenAI processing runs on US infrastructure, German buyers still need their own transfer impact assessment — the DPA supplies the safeguard, not your documentation.

The DPA supplements the OpenAI Services Agreement governing OpenAI's business services, which is the contract path for ChatGPT Enterprise, ChatGPT Business, and API usage. Free consumer ChatGPT does not sit under this processor relationship. If your question is really about enterprise procurement scope, audit logs, or admin controls, review our ChatGPT Enterprise page instead.

Get a quote