Skip to main content
    Back to Blog
    14 min read
    Gemini
    Google
    DPA
    GDPR
    AI Compliance

    Google Gemini DPA (2026): Where to Find It and What It Covers

    T

    Team Sonomos · Sonomos

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

    Where to find it: Google's Cloud Data Processing Addendum covers Gemini in Google Workspace and Google Cloud's Gemini services. Workspace admins can confirm or accept it in the Admin console under Account > Account settings > Legal and compliance (Google's steps). The paid Gemini API uses a separate Data Processing Addendum for Products Where Google is a Data Processor.

    Short answer: There is no single "Gemini DPA". Which data processing terms apply depends on how you reach Gemini. Gemini in Gmail, Docs and Meet, the Gemini app used with a work or school account on a qualifying Workspace edition, and Gemini Notebook (formerly NotebookLM) are Workspace core services governed by the Cloud Data Processing Addendum. Gemini models on Gemini Enterprise Agent Platform, the developer platform Google called Vertex AI until April 2026, fall under the same addendum through the Google Cloud terms. The paid Gemini API and paid Google AI Studio use Google's processor terms. The consumer Gemini app on a personal Google account has no DPA at all: Google provides it as a consumer service under its own privacy notice. For EU transfers, Google relies first on its certification under the EU-U.S. Data Privacy Framework and keeps Standard Contractual Clauses as the fallback. Everything below was checked against Google's pages on 18 November 2026.

    Which Gemini products have a DPA

    A data processing agreement is the Article 28 GDPR contract that binds a processor to act only on the customer's instructions. Google offers one for every business route to Gemini and none for the consumer app. The table maps each route to the terms that govern it.

    How you use GeminiData processing termsTraining on your prompts
    Gemini in Workspace apps (Gmail, Docs, Sheets, Meet, Drive)Cloud Data Processing Addendum, as part of the Workspace agreementNot without your permission or instruction (Workspace Service Specific Terms, section 12.11)
    Gemini app signed in with a work or school account on a qualifying Workspace editionCloud Data Processing Addendum (the app is a Workspace core service)Same Workspace training restriction; chats and files not human-reviewed or used for training without permission
    Gemini Notebook (formerly NotebookLM) with a Workspace accountCloud Data Processing Addendum (core service)Not used to train models
    Gemini models on Gemini Enterprise Agent Platform (formerly Vertex AI), Gemini Enterprise, Gemini for Google CloudCloud Data Processing Addendum, through section 5.2 of the Google Cloud Platform TermsNot without prior permission or instruction (Service Specific Terms, Training Restriction)
    Gemini API and Google AI Studio, paidData Processing Addendum for Products Where Google is a Data ProcessorNot used to improve Google's products
    Gemini API and Google AI Studio, unpaid, outside the EEA, Switzerland and the UKNoneUsed to improve Google products, with human review
    Consumer Gemini app on a personal Google accountNone; the Gemini Apps Privacy Notice appliesDepends on the user's Gemini History settings

    Three rows deserve a closer look. The Workspace services summary, last modified 31 August 2026, lists the Gemini app among the "Main Core Services", although some editions exclude it. Google's Generative AI in Google Workspace Privacy Hub says use of the app on a qualifying edition is "subject to your organization's Workspace agreement, including the Cloud Data Processing Addendum". The same employee opening gemini.google.com in a personal Google account is outside all of that.

    The Gemini API Additional Terms, effective 23 March 2026, define the paid tier narrowly: the API is a paid service only "when accessing the API through a Cloud Project associated with an active billing account", and AI Studio is paid when the account has such a project or is a Workspace enterprise account. Unpaid use comes with a plain warning: "Do not submit sensitive, confidential, or personal information to the Unpaid Services." The exception is geographic. In the EEA, Switzerland and the UK, the paid-tier data terms "apply to all Services", including free AI Studio use, and developers may only offer API clients to users there through paid services.

    The last row is the one that causes trouble. Google's Gemini Apps Privacy Hub says the consumer app is provided by Google Ireland Limited in the EEA and Switzerland and by Google LLC elsewhere, with Google deciding how chats are used. There is no processor relationship for an employer to rely on.

    How the Cloud Data Processing Addendum is accepted

    The addendum used to carry different names: the "Data Processing Amendment" for Workspace and the "Data Processing and Security Terms" for Google Cloud. Its opening paragraph lists those former names and says the addendum is "incorporated into the Agreement(s)". The version we read was last modified on 30 October 2026.

    For Google Cloud, incorporation is automatic. Section 5.2 of the Google Cloud Platform Terms of Service says Google "will only access, use, and otherwise process Customer Data in accordance with the Cloud Data Processing Addendum". Gemini Enterprise Agent Platform is a Google Cloud service, listed in the Google Cloud services summary as "formerly Vertex AI Platform", so there is nothing extra to sign.

    For Workspace, Google's admin help says you only need to opt in if your agreement does not already incorporate the addendum, and recommends opting in when unsure because doing so "won't make any difference if, in fact, your agreement already incorporates it". A super administrator does it under Security and Privacy Additional Terms in the Legal and compliance page. The same page holds a step that is easy to overlook: if your billing address is outside Europe, the Middle East and Africa and the GDPR applies to your use, you certify that in the console and name your supervisory authority.

    The contracting party depends on the billing address. Google's contracting entity page assigns Google Cloud EMEA Limited in Dublin to most of the region, with Google Cloud France, Google Cloud Italy S.r.l. and Google Cloud Poland Sp. z o.o. for customers billed in those three countries. That applies to Workspace, Google Cloud and paid Gemini API agreements alike.

    Transfers: the Data Privacy Framework first, SCCs behind it

    Section 4.1 of the addendum's European data protection terms sets the order. If Google "has adopted an Alternative Transfer Solution" for restricted transfers, it will make them under that solution. Only if it has not, or stops, do Google's Standard Contractual Clauses apply. The addendum defines "Adequate Country" to exclude adequacy reached "on the basis of an optional data protection framework", which is why the Data Privacy Framework sits in the alternative-solution slot.

    Google's Alternative Transfer Solution page, last modified 29 September 2026, records the adoption: for EU and EEA data "as of September 1, 2023", and for UK and Swiss data as of 16 September 2024, each because Google LLC certified to the relevant framework. The Data Privacy Framework List shows Google LLC's EU-U.S., UK Extension and Swiss-U.S. certifications as active, covering HR and non-HR data, with a usage end date of 13 September 2027.

    The processor terms behind the Gemini API follow the same pattern and are more explicit. Section 7.4 of their European appendix says Google "has certified under the Data Privacy Framework on behalf of itself and certain wholly-owned US subsidiaries" and that the framework "will apply to any Restricted European Transfer to a certified Google entity in the US". SCCs again stand behind it.

    Two consequences follow. A transfer impact assessment for Gemini should record the framework as the primary mechanism and the clauses as the fallback, with the date you checked the list. And if the framework falls, the addendum already provides for the SCCs to apply once Google stops relying on it, so nothing new needs to be signed. Section 4.6 also lets you terminate immediately if you conclude that "appropriate safeguards are not provided" for your use. Whether the framework will survive is a separate question, covered in our comparison of how Anthropic, OpenAI and Google handle the DPF and SCCs.

    Sub-processors and notice

    Section 11.4 of the addendum requires Google to notify you "at least 30 days before the New Subprocessor starts processing any Customer Data", with its name, location and activities. Your remedy is blunt: within 90 days you may "object by immediately terminating the applicable Agreement for convenience". The processor terms for the Gemini API contain the same 30-day and 90-day periods. The lists themselves sit in three places: the Workspace sub-processor list, the Google Cloud list and the processor-terms list. Notices go to the notification email address in your admin console, so it is worth checking that it reaches a monitored mailbox.

    EU data residency for Gemini

    Data residency is where the routes differ most.

    Workspace. Admins can choose to store covered data in the United States or Europe. Google's Data Regions coverage page lists "Prompts and responses" for both the Gemini app and Google Workspace with Gemini as covered at rest. Coverage of data "processed in use", meaning where the model actually runs, is limited to Enterprise Data Regions and Assured Controls Data Regions, which come with Enterprise Plus, Frontline Plus, Enterprise Essentials Plus or as add-ons. Business Standard, Business Plus and Enterprise Standard get Fundamental Data Regions, which cover data at rest only. Gemini Notebook is not covered: Google says data region settings "do not apply to data in Gemini Notebook".

    Gemini Enterprise Agent Platform. Google's data residency page separates storage from computation. Stored data stays in the location you choose. Where the model runs depends on the endpoint: the EU multi-region endpoint keeps machine-learning processing within EU member states and expressly excludes the UK and Switzerland, regional endpoints such as europe-west1 keep it within the wider jurisdiction, and global endpoints "don't provide any data residency guarantees". Support varies by model, so check the table for the model you deploy.

    Gemini API. The API terms say paid-tier prompts and responses "may be stored transiently or cached in any country in which Google or its agents maintain facilities". There is no residency commitment.

    Retention and abuse logging

    A DPA tells you Google will not use your data for its own purposes. It does not say Google keeps nothing.

    In Workspace, the Privacy Hub says admins decide how long Gemini app conversations are kept, with automatic deletion after 3, 18 or 36 months and 18 months by default. With conversation history off, chats are still "saved in user accounts for up to 72 hours". Side-panel history in Gmail and Docs runs from 90 days to indefinite, as admins set.

    On Agent Platform, Google's zero data retention page lists what you must turn off, or leave off, to keep nothing: implicit caching (held for up to 24 hours), request-response logging, stored Interactions API sessions, and session resumption for the Live API. If you use Grounding with Google Search, Google keeps queries derived from prompts for up to three days, and that storage cannot be disabled. Abuse logging depends on contract and model: for most Google models, flagged prompts can be logged for up to 90 days only for customers on Google's online terms, while models Google designates as frontier or Advanced AI carry their own logging rules, set out on its abuse monitoring page.

    For the paid Gemini API, Google's abuse monitoring policy keeps prompts, context and outputs for 55 days for policy enforcement.

    The consumer-account gap and the DPIA

    In practice the gap is rarely the contract on the business tier. It is staff using the consumer tier anyway. A personal Google account at work, an unpaid AI Studio project, or a Gemini app signed in with a private Gmail address all sit outside the addendum, whatever the company signed. The pattern is identical to the one in our Anthropic DPA guide, and the control is the same: block or redirect the consumer route on managed devices and give people a covered one.

    Many deployments will also need a data protection impact assessment under Article 35. Google publishes a Gemini DPIA support guide for Workspace with Gemini. It describes Google's processing; it cannot assess your purposes, data categories or lawful basis, which remain the controller's work, as our GDPR guide to Gemini explains. Where US healthcare data is involved, the separate question of the BAA is covered in Is Gemini HIPAA compliant?.

    Sources and primary references

    Checked 18 November 2026. Google revises these pages often; the dates are the ones each page showed that day.

    Frequently asked questions

    Does the Google Workspace DPA cover the Gemini app?

    Yes, when the user is signed in with a work or school account on a Workspace edition that includes the Gemini app as a core service. Google's Workspace Privacy Hub says that use is governed by the organisation's Workspace agreement, including the Cloud Data Processing Addendum. It does not cover the same person using Gemini through a personal Google account.

    Is there a DPA for Google AI Studio?

    For paid use, yes: the Gemini API terms apply Google's processor terms to paid services, which include AI Studio when the account has a Cloud project with active billing or is a Workspace enterprise account. Unpaid use outside the EEA, Switzerland and the UK has no DPA, and Google may use the content to improve its products with human review.

    Is Vertex AI still covered now that it is called Gemini Enterprise Agent Platform?

    Yes. Google renamed Vertex AI on 22 April 2026, and its services summary lists Gemini Enterprise Agent Platform as "formerly Vertex AI Platform". It remains a Google Cloud service, so section 5.2 of the Google Cloud terms still ties it to the Cloud Data Processing Addendum.

    Which Google entity signs the DPA for European customers?

    It follows the billing address. For most of Europe, the Middle East and Africa it is Google Cloud EMEA Limited in Dublin, with Google Cloud France, Google Cloud Italy S.r.l. and Google Cloud Poland Sp. z o.o. for customers billed in those countries.

    Getting the paperwork right for each Gemini route

    The practical work is an inventory. List every route by which your people reach Gemini, match each to the terms in the table above, and close the routes that have none. Record the transfer mechanism as the framework with SCCs behind it, note the date you checked Google's certification, and decide where model processing must run before you choose a Workspace edition or an Agent Platform endpoint. Then deal with what the contract cannot touch: what goes into the prompt. Pseudonymising names and identifiers before they leave the device reduces what any route, covered or not, ever receives.

    That last step is where Locke fits. 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 does with Gemini.

    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