Skip to main content
    Back to Blog
    12 min read
    GDPR
    Data Transfers
    Anthropic
    OpenAI
    Google

    Anthropic, OpenAI and Google DPF Status: Who Relies on SCCs

    T

    Team Sonomos · Sonomos

    Team Sonomos writes about AI, privacy, and what happens to sensitive information at work.

    Short answer, checked 18 November 2026: On the official Data Privacy Framework List, Google LLC holds active EU-U.S., UK Extension and Swiss-U.S. certifications. Neither Anthropic nor OpenAI appears on the list at all, as an active or an inactive participant. Their data processing addendums rely on the European Commission's 2021 Standard Contractual Clauses instead. Google's own terms put the framework first and keep SCCs as the fallback.

    The framework itself is still in force. The EU General Court rejected Philippe Latombe's challenge on 3 September 2025, his appeal to the Court of Justice (Case C-703/25 P) has produced no judgment, and in July 2026 the European Data Protection Board asked the Commission to assess what a US Supreme Court ruling on the Federal Trade Commission means for it. This guide sets out what each company's paperwork says, what the framework does and does not cover, and what to write in your transfer records.

    The three vendors side by side

    CompanyData Privacy Framework ListTransfer mechanism in its DPAEU contracting entity
    Google LLCActive: EU-U.S., UK Extension and Swiss-U.S.; HR and non-HR dataFramework first (adopted 1 September 2023 for EU data), SCCs as fallbackGoogle Cloud EMEA Limited for most of Europe
    AnthropicNot listed2021 SCCs, Module Two or Three, plus UK and Swiss addenda; no mention of the frameworkAnthropic Ireland, Limited for customers in the EEA, Switzerland or UK
    OpenAINot listedOpenAI Ireland transfers EEA and Swiss data onward under SCCs or an adequacy decision; UK data under SCCs with the UK AddendumOpenAI Ireland Ltd. for customers in the EEA or Switzerland

    So the answer to "is Anthropic on the DPF?" and "is OpenAI on the DPF?" is no. That does not mean either company transfers data unlawfully. The GDPR offers several routes for transfers to the United States, and the clauses are one of them.

    How we checked the list

    The US Department of Commerce publishes the Data Privacy Framework List and a downloadable copy of every participant record. We downloaded the file the site described as current "as of Tuesday, November 17, 2026 6:01 AM EST" and searched every public name, legal name and covered-entity field, for active and inactive participants alike. "Google LLC" returned three active certifications. "Anthropic" and "OpenAI" returned nothing in any field.

    Google's participant record says the certification "applies to Google LLC and its wholly-owned U.S. subsidiaries", lists EU data protection authorities as the dispute resolution body, and shows a usage end date of 13 September 2027.

    You should repeat the check before relying on it. The EDPB's DPF FAQ for European businesses, version 2.0 of 15 January 2026, says an exporter "must ascertain that the company in the U.S. holds an active self-certification (certifications must be renewed annually) and that this certification covers the data in question". It adds that HR data is covered only where the certification says so, and that "an EEA data exporter cannot rely on the DPF for transfers of personal data to companies that do not hold an active self-certification".

    What the Data Privacy Framework covers, and what it does not

    The framework rests on the Commission's Implementing Decision (EU) 2023/1795 of 10 July 2023, an adequacy decision under Article 45 of the GDPR. US companies self-certify to the Department of Commerce and commit to the framework's principles. Transfers to a certified company, within the scope of its certification, need no further transfer tool.

    Four limits matter in practice.

    • Only certified companies. Adequacy attaches to the organisation on the list, not to the United States as a whole. Eligibility is limited to companies under the jurisdiction of the FTC or the Department of Transportation, so banks and insurers cannot join.
    • It is not a DPA. The EDPB FAQ says controller and processor must conclude an Article 28 contract "regardless of whether the processor is self-certified under the DPF". A data processing agreement is still required.
    • It solves Chapter V only. The FAQ says that "all other requirements in the GDPR and any other national data protection law remain applicable": lawful basis, transparency, minimisation and the rest.
    • The national security safeguards apply to everyone. In its July 2023 information note, the EDPB said the US government's safeguards, including the new redress mechanism, "apply to all data transferred to the US, regardless of the transfer tool used", and that exporters using SCCs should take the Commission's assessment into account.

    That last point is easy to miss. A transfer impact assessment for Anthropic or OpenAI usually leans on the same Commission findings about US law that support the framework. If the Court of Justice struck those findings down, SCC users would need to revisit their assessments too.

    Anthropic: SCCs, and nothing else

    Anthropic's Data Processing Addendum, effective 24 February 2025, incorporates "Module Two (controller to processor) and/or Module Three (processor to processor)" of the clauses approved by Commission Implementing Decision (EU) 2021/914, "to the extent required by Applicable Data Protection Laws". Schedule 3 adds the UK International Data Transfer Addendum and Swiss amendments. The clauses are governed by Irish law. The document does not mention the Data Privacy Framework.

    Anthropic's Commercial Terms name Anthropic Ireland, Limited as the contracting party for customers in the EEA, Switzerland or the UK. The addendum describes the data importer as "the Anthropic entity that executed the Agreement" and promises information "reasonably necessary for Customer to complete a transfer impact assessment". Its consumer privacy policy, effective 10 September 2026, also relies on adequacy decisions and standard contractual clauses and says nothing about the framework.

    Several published summaries have said Anthropic participates in the framework, and an earlier version of our Anthropic DPA guide did too. The official list does not support that, and we have corrected the guide. If a vendor questionnaire in your files records Anthropic as DPF-certified, update it.

    OpenAI: OpenAI Ireland and SCCs

    OpenAI's Data Processing Addendum, version v.010126, is entered into with OpenAI Ireland Ltd. when the customer is based in the EEA or Switzerland, and with OpenAI OpCo, LLC otherwise. Section 4.1 says that, whoever the contracting party is, the customer "instructs OpenAI Ireland Limited to process any EEA and Swiss Data". Where OpenAI Ireland sends that data to affiliates or third parties outside Europe, "it will do so on the basis of agreements containing SCCs" or "an adequacy decision issued by the European Commission under Article 45 GDPR".

    Because OpenAI is not on the framework list, the adequacy route cannot cover transfers to OpenAI's own US companies; it remains relevant only for countries with their own adequacy decisions. UK data is handled differently: section 4.2 instructs OpenAI OpCo, LLC to process it under the SCCs as amended by the UK Addendum, with English law and the ICO named in Schedule 1. The sub-processor clause gives 30 days to object after notice of a change. Our ChatGPT GDPR guide covers the rest of OpenAI's posture.

    The Irish structure has a practical effect. An EEA customer hands data to an Irish company, so the customer's own transfer stays inside the EEA. The transfer to the United States is OpenAI Ireland's, made under clauses you are not a party to. Your transfer impact assessment should say so, and section 2.6 of the addendum commits OpenAI to reasonable assistance with your data protection obligations.

    Google: the framework first, SCCs behind it

    Google's Cloud Data Processing Addendum, last modified 30 October 2026, sets the order in section 4.1 of its European terms: if Google has adopted an "Alternative Transfer Solution", restricted transfers follow it, and only otherwise do Google's SCCs apply. Google's Alternative Transfer Solution page records the adoption "as of September 1, 2023" for EU data, after Google LLC certified to the framework, and as of 16 September 2024 for UK and Swiss data. The processor terms behind the paid Gemini API say the framework "will apply to any Restricted European Transfer to a certified Google entity in the US".

    For Gemini customers, this means the framework does the work today, the clauses wait in reserve, and section 4.6 gives a right to terminate if you conclude the safeguards are not appropriate for your use. Which Gemini products those terms reach is covered in our Gemini DPA guide.

    Where the framework stands legally in November 2026

    The decision is in force. EUR-Lex lists Decision 2023/1795 as "In force", with no end date and no amending act, and records that it was confirmed by the General Court's judgment in Case T-553/23.

    The General Court upheld it. On 3 September 2025 the court dismissed Latombe's action in full. According to the court's press release No 106/25, it found that the appointment and functioning of the Data Protection Review Court come with "several safeguards and conditions" securing its judges' independence, that Schrems II requires bulk collection to be subject at least to "ex post judicial review" rather than prior authorisation, and that the Commission "is required to monitor continuously" the US legal framework and may suspend, amend or repeal the decision if it changes.

    The appeal is pending. Latombe lodged an appeal on 31 October 2025, registered as Case C-703/25 P, on four grounds concerning the review court's independence and the rules on bulk collection. As of 18 November 2026, EUR-Lex holds no judgment, order or Advocate General's opinion in the case.

    The FTC question is open. On 29 June 2026 the US Supreme Court held in Trump v. Slaughter that the FTC commissioners' for-cause removal protection is unconstitutional. The adequacy decision relies on the FTC as an independent enforcer, and in a letter of 31 July 2026 the EDPB asked the Commission "to closely assess whether this development affects the functioning" of the decision. We found no Commission decision amending or suspending the framework since.

    One way to read all this: the framework is lawful today and may stay so for a year or more, but it now carries two live risks at once, a pending appeal and a question about its enforcement body. Planning for both outcomes costs little.

    What to put in your transfer records

    • Google: record the framework as the primary mechanism, the certification's scope and the date you checked the list, with Google's SCCs as the contractual fallback.
    • Anthropic and OpenAI: record the SCC module, the contracting entity (Anthropic Ireland or OpenAI Ireland for EEA customers) and a transfer impact assessment. Do not record framework certification.
    • All three: note whether model processing happens in the United States, keep the Standard Contractual Clauses annexes filled in for your actual use, and recheck the list each year because certifications lapse.
    • Supplementary measures: the measure most within your control is pseudonymisation before the data leaves Europe, so that what crosses the Atlantic is not identifiable. Our GDPR and AI guide puts this in the wider compliance picture.

    Frequently asked questions

    Is Anthropic certified under the EU-U.S. Data Privacy Framework?

    No. Anthropic does not appear on the Data Privacy Framework List, as an active or inactive participant, in the version current on 17 November 2026. Its Data Processing Addendum relies on the 2021 Standard Contractual Clauses, with UK and Swiss addenda, and does not mention the framework.

    Is OpenAI on the Data Privacy Framework List?

    No. Neither OpenAI nor any OpenAI entity appears on the list checked on 18 November 2026. OpenAI's DPA routes EEA and Swiss customer data through OpenAI Ireland Limited, which transfers it onward under SCCs, and handles UK data under the SCCs with the UK Addendum.

    Do Gemini customers still need SCCs if Google is certified?

    Not as the primary mechanism. Google's Cloud Data Processing Addendum uses the framework while Google relies on it and switches to Google's SCCs if it stops. You still need the addendum itself, because the framework does not replace an Article 28 contract.

    What happens to SCC transfers if the Court of Justice annuls the framework?

    The clauses would remain valid, but the EDPB has said the US national security safeguards behind the framework apply to all transfers whatever the tool. Assessments that relied on the Commission's findings would need to be redone, and supplementary measures would carry more weight.

    Paperwork for today, a plan for the ruling

    The vendors' paperwork is settled for now: Google relies on the framework, Anthropic and OpenAI rely on the clauses, and all three sit on the same Commission findings about US law. The part of the transfer you control is the content. Personal data that is removed or replaced before a prompt is sent cannot be exposed by any later ruling about where it went.

    That is the gap Locke is built for. It runs on your device, detects names, account numbers and other sensitive values in the AI tools it screens, and swaps them for placeholders before the prompt leaves, and the unmasked content is never sent to Sonomos. Download Locke and try it on the work your team already sends to US AI providers.

    Send the AI less personal data

    Locke runs on your own computer and replaces the names, email addresses and other personal data it detects with placeholders before a prompt reaches the AI tools it screens, so less personal data is transferred to the AI provider. It does not make an AI tool GDPR compliant or replace a DPA, a transfer mechanism or a DPIA, and anything it does not detect is sent as typed.

    Sonomos, which publishes this blog, makes Locke. Free for one person on x64 Windows and Linux; macOS is coming soon.

    This article is general information about privacy and AI, not legal advice, and reading it does not create a solicitor–client or attorney–client relationship. Regulatory requirements turn on your specific facts and jurisdiction and change over time. Consult qualified counsel before relying on anything here, and check the publication and last-reviewed dates above. We may revise posts, but we do not undertake to keep any post current as the law changes.

    Reference pages for this post