Skip to main content
    Back to Blog
    10 min readLast reviewed:
    GDPR
    Grok
    xAI
    Europe
    AI Compliance
    Data Protection

    Is Grok GDPR Compliant? DPC Inquiries and Work Use (2026)

    T

    Team Sonomos · Sonomos

    The Sonomos research team writes about AI privacy, data protection, and how to use generative AI safely at work.

    Short answer: It depends on which Grok you mean. Consumer Grok, on grok.com and inside X (formerly Twitter), comes with no data processing agreement, so an organisation cannot use it lawfully for EU personal data. xAI's business offerings are different: xAI publishes a Data Processing Addendum, with archived versions back to September 2024, and its Enterprise FAQ says the DPA "is automatically incorporated" into the Enterprise Terms of Service whenever a customer submits personal data. The harder problem for European teams is regulators, not paperwork: Ireland's Data Protection Commission (DPC) has two open inquiries, one into X's use of EU users' posts to train Grok and one into sexualised images made with it, and the UK's Information Commissioner's Office (ICO) is investigating the images too. This guide separates what the contracts now offer from what they cannot fix.

    Grok and xAI: the regulatory background

    Grok is the AI model built by xAI, Elon Musk's AI company, and is available through X, the standalone Grok.com interface and xAI's API. SpaceX acquired xAI in February 2026, and xAI's own legal pages now carry the SpaceXAI name and a SpaceX-owned contracting entity, so check which entity the version you sign names. Grok's real-time access to X's post stream distinguishes it from other major AI assistants.

    The GDPR problem with Grok is a training-data problem as much as a product-tier problem, and it has attracted direct supervisory-authority enforcement at the company level.

    The DPC inquiries (Ireland, 2024 to 2026). In August 2024 the DPC went to the Irish High Court over X's use of EU users' posts to train Grok, and X agreed to suspend that processing. On 11 April 2025 the DPC opened a formal inquiry into X Internet Unlimited Company, X's Irish entity, to determine whether personal data in publicly accessible posts by EU/EEA users was lawfully processed to train the Grok models, looking at both the lawfulness and the transparency of that processing. On 17 February 2026 it opened a second inquiry into the creation and publication on X of non-consensual intimate or sexualised images, including of children, using Grok, under Articles 5, 6, 25 and 35 of the GDPR.

    The ICO investigations (UK, 2026). On 3 February 2026 the UK's Information Commissioner's Office opened formal investigations into X Internet Unlimited Company and X.AI LLC, covering their processing of personal data in relation to Grok and its potential to produce harmful sexualised images and video. The ICO said the concerns are whether personal data was processed lawfully, fairly and transparently, and whether Grok was built with safeguards against that use.

    The DPC's April 2025 inquiry goes to the provenance of Grok's training data, and the 2026 investigations go to whether safeguards were built into the product's design.

    What xAI's business contracts now cover

    Earlier versions of this guide said xAI offered no enterprise DPA. That was wrong, and the terms matter for any team weighing the API or Grok's business plans.

    • A DPA under the Enterprise Terms. xAI's Enterprise FAQ says that if you submit personal data to its services, the DPA applies and is automatically incorporated into the Enterprise Terms of Service. The Enterprise Terms, in the version dated August 14, 2026, say xAI will process that data "as a processor on Customer's behalf" and link the DPA.
    • Transfers. The DPA incorporates the EU Standard Contractual Clauses for restricted transfers, and says personal data may be processed in the United States and other countries where xAI and its subprocessors operate. It gives general authorisation for subprocessors, which xAI lists on its site.
    • No training on API or business data by default. xAI's API security FAQ says it "never trains on your API inputs or outputs without your explicit permission", and the Enterprise Terms say user content will not be used to train foundation models, subject to disclosures and customer-controlled settings.
    • Retention. The API keeps requests and responses for 30 days for abuse monitoring. A team admin can switch on zero data retention (ZDR) in the console where xAI offers it self-serve, or it can be set in a negotiated enterprise agreement. ZDR rules out features that store data, such as the Files and Batch APIs.
    • No EU region. xAI's regional endpoints page says the global endpoint "does not guarantee a processing region" and offers only a US regional endpoint, adding that a regional endpoint is "not, by itself, a comprehensive data-residency guarantee."

    x.ai refuses automated requests, so we could not load the DPA, the Enterprise FAQ or the Enterprise Terms directly. The points above about them rest on search-engine extracts of those pages and on dated captures by the terms tracker ConductAtlas; the API documentation was read directly. Read the current DPA before you sign.

    Grok's GDPR posture at a glance (2026)

    AttributeConsumer Grok (grok.com, X)xAI API and business plans
    DPANoYes, incorporated into the Enterprise Terms
    Standard Contractual ClausesNoYes, in the DPA, for restricted transfers
    EU data residencyNoNo: a global endpoint or a US endpoint only
    Training on your dataCan be used; opt out in the app's data controlsNot without explicit permission
    Zero data retentionNoAvailable to team admins or by contract
    SOC 2Not applicableSOC 2 Type 2, according to xAI's API docs; report under NDA
    BAA for HIPAA workloadsNoNone published; xAI takes requests through a questionnaire
    Training-data lawful basisUnder DPC inquiry since April 2025Same models, same inquiry
    Supervisory investigationsDPC (two inquiries), ICOSame company

    Why training-data provenance still matters for deployers

    A DPA governs what xAI does with the data you send. It does not settle how the model was built, and that question reaches deployers too.

    The tainted-basis risk. If the supervisory authorities conclude that xAI's training data was processed without a valid lawful basis, Grok's outputs come from a model built on unlawfully processed personal data. Using such a model for high-stakes decisions about people is a risk an EU controller should record in its DPIA, whatever the DPA says.

    Procurement risk. When a supervisory authority has an open investigation against a vendor, procuring it for regulated workflows creates audit and reputational risk. If an investigation ends in an order to stop processing or a major fine, organisations that deployed Grok will face questions about their due diligence. The lead authority's training-data inquiry has not, as far as we could find, produced a published decision. (OpenAI's Italian fine over ChatGPT, by contrast, was annulled on competence grounds in March 2026, which says nothing either way about the merits.)

    The X stream. Grok can retrieve and synthesise X posts in real time. If a query makes Grok pull posts by EU individuals, their personal data becomes part of the response, and the legal basis for that retrieval sits with xAI and X, outside your DPA.

    Can Grok be used at all by EU teams?

    On consumer Grok, only for queries with no personal data: market research, public regulatory analysis, general technical questions. With no DPA, any work use involving personal data lacks the Article 28 contract the GDPR requires.

    Through the API or a business plan under the Enterprise Terms, the contractual pieces now exist: a processor DPA, SCCs, no training by default, and zero data retention for teams that need it. What is missing is an EU processing region, so EU personal data goes to the US under the SCCs and needs a transfer impact assessment. The open investigations are a reason to keep high-stakes personal data out until they are resolved.

    The practical recommendation for regulated European organisations in 2026: block consumer Grok for work, and assess the API or business plans like any other US processor, with the investigations recorded as a known risk.

    Frequently asked questions

    Is Grok available on any tier with GDPR compliance?

    Not on consumer Grok: X Premium and grok.com run on consumer terms with no DPA. xAI's API and business offerings come under its Enterprise Terms, which incorporate a DPA with Standard Contractual Clauses when you submit personal data. That gives you the Article 28 contract and a Chapter V transfer mechanism, but no EU data residency, and compliance still depends on your own lawful basis, DPIA and transfer assessment. If you buy Grok business seats, confirm in the order form that the Enterprise Terms and DPA apply.

    Could xAI resolve the training-data investigation and become GDPR compliant?

    Potentially. The DPC investigation could end with remediation undertakings, revised data practices, or a fine with required changes. Until a decision is published, the lawfulness of Grok's training data stays an open question that no customer contract can answer.

    Is it safe to use Grok for personal research, outside of work?

    For personal use with no employer involvement, the GDPR's controller-processor framework does not apply in the same way, because you are acting as a private individual. xAI's and X's consumer terms and privacy policies govern, and consumer Grok may use your conversations for training unless you turn that off in its data controls.

    We have employees who use Grok through X Premium. Is that a concern?

    Yes, if they use it for client data, patient information, financial records or other personal data at work. The employer is the controller for processing its staff carry out in the course of their work, and a personal X Premium account comes with no DPA. That Article 28 gap exists whatever xAI offers its business customers.

    What should we do about Grok on managed devices?

    Block or restrict consumer Grok through your acceptable-use policy and device controls, as you would any consumer AI tool without a DPA. If a team has a real need, route it through an approved API or business account under the Enterprise Terms, with the DPA in place, ZDR considered and the transfer assessed.

    The bottom line

    Grok's GDPR picture splits in two. Consumer Grok has no DPA and should stay out of any work involving EU personal data. xAI's API and business plans now come with a DPA, SCCs, no training by default and an optional zero data retention mode, which puts them on a contractual footing comparable to other US AI providers, minus an EU region. No contract changes the fact that Grok's lead EU supervisor is examining whether its training data was lawfully processed, or that both the DPC and the ICO are investigating sexualised images made with it.

    For regulated European organisations, the analysis is short: block consumer Grok for work, assess the business offering as a US processor with open regulatory risk, and keep the most sensitive personal data out of it until the investigations are resolved.

    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