A Greenwolf Tech Labs site · Our Data Studio agency team, India and USAgreenwolftechlabs.com ↗

Compliance guide

Data Studio GDPR: how to run compliant reports for EU clients

Data Studio GDPR compliance comes down to three things: accepting Google's data processing terms in your account settings, keeping personal data out of reports that do not need it, and controlling every copy of the data that leaves the report. This guide is for marketing agencies, ecommerce brands and in-house teams that report on EU or UK customers in Data Studio (formerly Looker Studio). We cover what Google commits to, the settings you must complete, where connectors and scheduled emails create risk, what Data Studio Pro adds, and a checklist you can work through this week.

Analyst reviewing Data Studio GDPR sharing and data source settings on a laptop
Compliance guide7 min readUpdated November 18, 2026 · by Harsh Khubchandani

Quick answer

Is Data Studio GDPR compliant?

Data Studio can be used in a GDPR-compliant way. Google acts as a data processor under its Ads Data Processing Terms, which are part of the Data Studio terms of service. You still need to complete the GDPR fields in your account settings, keep personal data out of reports where possible, sign DPAs with partner connectors, and control sharing.

  • Google is a processor for Data Studio; you or your client remain the controller.
  • Every user subject to GDPR must complete the Account and Privacy fields, or an admin accepts for the organisation.
  • Partner connectors, extracts and scheduled emails are separate data flows that each need a decision.
  • Most marketing dashboards need aggregated data only, which removes most of the risk.
01

Is Data Studio GDPR compliant?

Data Studio is not compliant or non-compliant on its own. GDPR applies to the way you use it. Google provides the contract and controls a processor must provide, and you decide what personal data goes in, who sees it and where copies end up.

Google's Data Studio documentation states that Google operates as a data processor for the product, and that this is reflected in the Google Ads Data Processing Terms, which are incorporated into the Data Studio terms of service. Those terms (version 8.0, effective May 30, 2024, when we reviewed them) say that Google is a processor of customer personal data and that the customer is the controller or a processor, as applicable.

That last phrase matters for agencies. When an agency builds reports on a client's GA4, ad and CRM data, the client is usually the controller and the agency is a processor acting on its instructions. Google then becomes a sub-processor in the client's chain. Article 28 of the GDPR requires a written contract between controller and processor, and says a processor may not engage another processor without the controller's prior written authorisation. In plain terms, your client agreement should name Data Studio, Google and any connector vendor you use.

This guide is a practical summary for planning, not legal advice. Your data protection officer or counsel should confirm the final setup, especially if you process special category data.

02

What does Google commit to under the data processing terms?

The Ads Data Processing Terms set out what Google does with the personal data that passes through Data Studio. Reading them once saves a lot of back-and-forth with client procurement teams, because most of their questions are answered there.

For transfers out of the EEA, the terms rely on an approved transfer mechanism. Where Google has not adopted an alternative transfer solution, the Standard Contractual Clauses (processor to processor, Google as exporter) apply. Separately, the EU-US Data Privacy Framework was challenged in the case Latombe v Commission (T-553/23). On September 3, 2025, the EU General Court dismissed that challenge and found the United States ensured an adequate level of protection when the framework was adopted. Mr Latombe announced an appeal to the Court of Justice, so check the current position before you rely on it in client paperwork.

TopicWhat the Ads Data Processing Terms sayWhat it means for your reports
RoleGoogle is a processor of customer personal dataYou or your client stay the controller and set the purpose
Sub-processorsListed at business.safety.google/adssubprocessors, 30 days notice before new onesReference the list in your own DPA instead of copying it
DeletionPersonal data deleted within a maximum of 180 days after a request or the end of the term, unless law requires storageTell clients deletion is not instant when a report is removed
SecurityISO 27001 certification, encryption at rest, incident notification to the customerCite these in security questionnaires rather than inventing your own wording
TransfersStandard Contractual Clauses where no alternative transfer solution appliesRecord the transfer mechanism in your records of processing
03

Which Data Studio GDPR settings do you need to complete?

Google's GDPR page for Data Studio says that if you are subject to GDPR, you must complete all required fields in Data Studio under User Settings, then Account and Privacy. It also says each user within a company subject to GDPR must complete them, or an administrator can accept the data processing terms on behalf of the organisation.

The required fields are a primary contact name, email and address. Contact details for an EEA representative and a data protection officer are optional. If you accept the Data Processing Amendment on behalf of your company, you must enter a company name, and Google notes that once saved, the name cannot be changed. Enter the legal entity name exactly as it appears in your contracts.

For agencies, the practical question is whose account owns the reports. If reports and data sources sit in a freelancer's or account manager's personal Google account, that person's settings apply and the client has no visibility. Owning reports in an organisation account, and transferring ownership to the client where they are the controller, keeps the paper trail clean.

  • Open User Settings, then Account and Privacy, in Data Studio for every creator and editor.
  • Enter the primary contact name, email and address; add the DPO and EEA representative if you have them.
  • Use the exact legal entity name, because it cannot be edited later.
  • Or ask your Workspace or Cloud administrator to accept the terms for the whole organisation.
  • Record the date accepted in your records of processing activities.
04

Where does personal data actually flow in a Data Studio report?

Most GDPR problems in reporting come from copies people forget about. A Data Studio report is not one place where data lives. It is a chain of systems, and each link needs its own decision.

Take a typical client report built on GA4, Google Ads, Meta Ads through a partner connector, and a CRM export in Google Sheets. GA4 and Google Ads data are aggregated before they reach the report, and Google Analytics terms prohibit sending personally identifiable information to GA4 in the first place. Meta data passes through the connector vendor's servers, so that vendor is a processor too. The CRM sheet is the risky part, because it often holds names, emails and phone numbers that nobody needed for a channel performance chart.

A Matomo community thread on visualising analytics data in Data Studio reached the same conclusion: aggregated data carries far less risk, but custom dimensions or fields can quietly include identifiers such as emails, and then full GDPR obligations apply.

Data flowPersonal data riskControl to apply
GA4 and Google Ads native connectorsLow: aggregated metrics, PII banned in GA4Check custom dimensions and URLs for emails or IDs
Partner connector (Supermetrics, Windsor.ai, Porter Metrics and others)Medium: vendor processes client dataSign the vendor's DPA, list it as a sub-processor
Google Sheets or CSV upload from a CRMHigh: often contains names and contact detailsAggregate before upload, remove direct identifiers
BigQuery tablesDepends on the modelExpose views with only reporting columns, set dataset location
Data extractsA stored copy of query resultsExtract only aggregated fields, review who can edit
Scheduled email deliveryPDF copies land in inboxesLimit recipients, avoid row-level tables in emailed pages
Viewers and link sharingAnyone with the link can see the dataRestrict sharing to named people or your domain
05

How should agencies handle GDPR in white-label reporting?

White-label reporting multiplies the chain. The agency's client is often itself an agency, which reports to the brand that owns the customer data. Each step needs a contract that flows the same obligations down, and each step needs to know which tools sit in the chain.

In our experience, three practices prevent most problems. First, keep a written list of data sources, connectors and storage locations per client, and attach it to the DPA. Second, design templates that use aggregated data only, so a new client can be onboarded without a fresh privacy review. Third, separate clients completely: one set of data sources and credentials per client, never a shared Sheet or BigQuery dataset with a client filter on top. Data Studio has no built-in client management for agencies, so this separation has to be designed in.

Credentials deserve their own line. A data source using owner's credentials lets every viewer see the data the owner can access. That is fine for an aggregated dashboard, and risky when the owner's access covers several clients. Viewer's credentials make each viewer authenticate with their own access, which suits internal teams but frustrates external clients who lack access to the underlying platforms. Decide per data source and write the decision down.

If a client asks for row-level views, for example each regional manager seeing only their region, Data Studio's filter by email option on a data source can restrict rows to the signed-in viewer. Test it with a non-admin account before launch.

06

What does Data Studio Pro add for GDPR and data residency?

Data Studio Pro adds controls that procurement and security teams ask about, and it costs $9 per user per project per month, with viewers needing no licence. The free edition is enough for many agencies, but Pro is worth reviewing when a client requires organisation-owned content, audit logs or a fixed data location.

Google's Pro documentation describes data residency, which keeps data physically within a chosen geographic area, and customer-managed storage, which stores file uploads in your own Cloud Storage bucket and data extracts in your own BigQuery dataset. Customer-managed encryption keys (CMEK) let you encrypt Pro data such as report and data source configurations and scheduled emails with your own Cloud KMS keys, and revoking the key makes that data unavailable.

There is a timing trap. Google states that CMEK can only be enabled when you create a new Pro subscription, not added to an existing one, and that it requires customer-managed storage and a data location in the same region as the key. If a client might need CMEK later, decide before you set up the subscription.

  • Organisation-owned content tied to a Google Cloud project, so reports do not leave with a departing employee.
  • Team workspaces with defined roles for managers, content managers and contributors.
  • Audit logging for access reviews.
  • Data residency, customer-managed storage and CMEK for clients with strict location or encryption rules.
07

Worked example: a GDPR review for a 12-client agency

Here is a hypothetical agency in Germany with 12 ecommerce clients, each with a monthly Data Studio report built on GA4, Google Ads, Meta Ads through one partner connector, and a Shopify order export in Google Sheets. The figures are illustrative, chosen to show the method.

Mapping the flows shows 4 data sources per client, so 48 data source connections, 12 shared Sheets and 12 scheduled email deliveries. Only one flow per client holds direct identifiers: the Shopify export, which includes customer names and emails because it was the default export.

The fix takes a few steps rather than a rebuild. Replace the raw export with a summary of orders and revenue by day, channel and product category, so the Sheets hold no personal data. Sign the connector vendor's DPA and add it to the sub-processor annex of each client contract. Move report ownership from two account managers' personal accounts to the agency's organisation account. Restrict link sharing to named client contacts. After the change, the only processors handling personal data are Google and the connector vendor, both under signed terms, and the templates can be reused for client 13 without a new review.

08

What mistakes put Data Studio reports at GDPR risk?

The mistakes we see most often are not exotic. They are ordinary shortcuts that copy personal data into places nobody tracks.

  • Uploading full CRM or order exports with names and emails when the chart only needs totals.
  • Leaving reports on anyone with the link sharing after a pitch or a client handover.
  • Using a partner connector without signing its DPA or listing it as a sub-processor.
  • Building every client's reports in one employee's personal Google account.
  • Sending scheduled PDFs with customer-level tables to long distribution lists.
  • Sharing one BigQuery dataset across clients and relying on a report filter to separate them.
  • Assuming GA4 data is anonymous without checking custom dimensions and page URLs for emails or IDs.
09

Data Studio GDPR checklist

Work through this list once per account and once per client. The first pass takes the longest, because it surfaces flows nobody documented. After that, it becomes a short step in onboarding each new client.

When it is better not to change tools: if your concern is that GA4 itself is unsuitable for a client, switching the dashboard tool will not solve it, because the issue sits in the data collection layer. Fix consent and tagging first. If a client requires all processing to stay within the EU on EU-owned infrastructure, Data Studio may not meet that policy, and a self-hosted tool may be the honest answer.

  • Complete the Account and Privacy GDPR fields, or have an admin accept the terms for the organisation.
  • List every data source, connector, extract, upload and scheduled delivery per client.
  • Remove direct identifiers from Sheets, uploads and BigQuery views used for reporting.
  • Sign DPAs with partner connector vendors and name them in client contracts.
  • Choose owner's or viewer's credentials per data source and record why.
  • Restrict sharing to named people or your domain and review access each quarter.
  • Keep reports in organisation-owned accounts, and transfer ownership where the client is controller.
  • Decide on Pro data residency and CMEK before creating a Pro subscription, if a client may need them.
10

How Greenwolf Tech Labs builds GDPR-aware reporting

We start with a free review of your current reports, data sources, connectors and sharing settings, and return a written map of where personal data flows. We then rebuild templates around aggregated data, move ownership into accounts you control, and document credentials and sharing per client so your DPA annexes match reality.

Our team has delivered 100+ projects for 200+ clients in 50+ locations, including white-label and managed reporting for agencies. We quote a fixed price after the review, and we are clear about what is a technical fix and what needs your legal adviser.

FAQ

Frequently asked questions

Is Looker Studio GDPR compliant now that it is called Data Studio?

The rename in April 2026 did not change the legal position. Google still acts as a processor under the Ads Data Processing Terms, existing reports moved over automatically, and the same GDPR settings apply. Compliance still depends on how you configure and share reports.

Does Data Studio store my data?

Data Studio mainly queries your sources when a report loads, but some copies are stored, such as data extracts and file uploads, and scheduled emails send PDFs to inboxes. Treat each as a data flow. Data Studio Pro's customer-managed storage lets you keep uploads and extracts in your own Cloud Storage and BigQuery.

Do I need a DPA with Google for Data Studio?

Google's Ads Data Processing Terms are already incorporated into the Data Studio terms of service. If you are subject to GDPR, you complete the GDPR fields under User Settings, Account and Privacy, or an administrator accepts the terms for the organisation. Keep a record of when that was done.

Can I put customer emails in a Data Studio report?

You can, but you then carry full GDPR obligations for that report, including lawful basis, access control and deletion. Most marketing and sales dashboards only need totals by day, channel or product, so aggregate the data before it reaches Data Studio.

Are partner connectors like Supermetrics GDPR compliant?

Each connector vendor processes your data on its own servers, so it is a separate processor with its own terms. Check that the vendor offers a DPA, sign it, and list the vendor as a sub-processor in your client contracts. Vendor terms change, so review them yearly.

Can Data Studio keep data in the EU?

Data Studio Pro offers a data residency setting that keeps Pro data within a chosen geographic area, plus customer-managed storage and encryption keys. CMEK can only be enabled when a new Pro subscription is created. The free edition does not offer these controls.

Who is the controller when an agency builds client reports?

Usually the client is the controller, because it decides why the data is processed, and the agency is a processor acting on instructions. Google and any connector vendor are then sub-processors. Article 28 of the GDPR requires this chain to be covered by written contracts.

Reviewed by Team Greenwolf Tech Labs · 18 Nov 2026

Get started

Tell us what your reporting has to do

Describe the dashboards you need, who reads them and where the data sits. We reply within one business day with an approach, the connectors involved and a fixed-price plan.

  • Free 30-minute reporting review
  • Fixed quote before any work starts
  • Everything built and owned in your Google account

Prefer email? info@greenwolftechlabs.com

Get a free proposal

Two lines is enough to start.

A Data Studio lead replies from info@greenwolftechlabs.com, usually within one business day. No mailing lists.

Ask us anything

A Data Studio lead replies from info@greenwolftechlabs.com, usually within one business day.

A Data Studio lead replies from info@greenwolftechlabs.com, usually within one business day. No mailing lists.