Google Denmark: DPA, subprocessors and transfers

Links last opened 31 October 2026. Record confirmed by a person on 2 October 2026. 2 recorded changes, listed below.

Google Denmark contracts through Google Denmark ApS, registered in Denmark. It is registered inside the EEA, so sending personal data to it is not a transfer out of the EEA. Its trust center is published at https://cloud.google.com/trust-center. Its customer data processing agreement, also called a data processing addendum, is published by Google Denmark itself; the link is below. Its sub-processor list is published by Google Denmark itself; the link is below. We open those pages every day — last on 31 October 2026 — and a person last went through this record on 2 October 2026.

Contracting legal entity: Google Denmark ApS
Country of registration: Denmark
Transfer mechanism for its own onward transfers: Not applicable
Reaching Google Denmark is not a transfer out of the EEA: it is registered in Denmark. This is what the record holds for where it sends personal data on, and it is not something we have checked — its sub-processor list is the place to look.
Data processing agreement: https://cloud.google.com/terms/data-processing-addendum
Subprocessor list: https://cloud.google.com/terms/subprocessors
Security or trust page: https://cloud.google.com/trust-center

What to put in your subprocessor list

A ready row. Replace the purpose with what your client actually uses Google Denmark for.

Subprocessor	Legal entity	Country	Purpose	Transfer	DPA
Google Denmark	Google Denmark ApS	DK	—	n/a	https://cloud.google.com/terms/data-processing-addendum

Questions people ask about Google Denmark

Where is Google Denmark's DPA?: Google Denmark publishes its customer data processing agreement at https://cloud.google.com/terms/data-processing-addendum. We last opened that link on 31 October 2026.
Is Google Denmark's DPA the same thing as a data processing addendum?: Yes. A data processing agreement and a data processing addendum are two names for the document Article 28 of the GDPR requires between a controller and a processor; vendors use both, and some call it processor terms. What it has to contain does not change with the name. Google Denmark's is at https://cloud.google.com/terms/data-processing-addendum.
Where is Google Denmark's sub-processor list?: Google Denmark publishes the list of its own sub-processors at https://cloud.google.com/terms/subprocessors. We last opened that link on 31 October 2026.
Which legal entity does Google Denmark contract through?: Google Denmark ApS, registered in Denmark. That is the name to put in a record of processing or a sub-processor list, not the brand.
Does sending personal data to Google Denmark count as a transfer out of the EEA?: No. Google Denmark ApS is registered in Denmark, inside the EEA, so no transfer mechanism is needed to reach it. Where it sends personal data on to is a separate question, and one for its own sub-processor list.
Where is Google Denmark's trust center?: Google Denmark publishes it at https://cloud.google.com/trust-center. A trust center, trust page or security page is the same thing under different names: the vendor's own account of how it protects data, and the place it keeps its certifications. It is Google Denmark's page, so we link to it rather than repeat what it says.

What has changed, and when

Changes we noticed on Google Denmark's own pages, each with the page we saw it on. The vendor does not publish this, and neither does anyone else.

31 October 2026
Google Denmark's subprocessor list now includes Google Cloud Universal Ledger (GCUL), a distributed ledger service for financial institutions, added in the October 30, 2026 version. The data processing agreement was updated to reflect that Transaction Data stored on GCUL cannot be deleted by either the customer or Google during the service term or upon termination, and customers must handle data rectification through subsequent transactions or their own systems rather than requesting deletion.
Seen on https://cloud.google.com/terms/data-processing-addendum
20 October 2026
Google Denmark added subprocessors in India and Malaysia for AI Solutions, Pre-Trained APIs, AI Platform/Gemini platform, Generative AI Services and Agentic AI Services. These countries lack EU adequacy decisions, requiring additional safeguards for personal data transfers under data protection law.
Seen on https://cloud.google.com/terms/subprocessors

Building your own sub-processor list?

Enter your website: each service it loads, what it is for and links to its own DPA, in a minute or two. No sign-up.

Build my list

Worked out from the registry and what we have written: the country this vendor contracts from, the guides that answer the question this page raises, and the rest of the registry.

Subprocessor

Legal entity

Country

Purpose

Transfer

DPA

Google Denmark

Google Denmark ApS

—

n/a

https://cloud.google.com/terms/data-processing-addendum

Questions people ask about Google Denmark

Where is Google Denmark's DPA?

Google Denmark publishes its customer data processing agreement at https://cloud.google.com/terms/data-processing-addendum. We last opened that link on 31 October 2026.

Is Google Denmark's DPA the same thing as a data processing addendum?

Yes. A data processing agreement and a data processing addendum are two names for the document Article 28 of the GDPR requires between a controller and a processor; vendors use both, and some call it processor terms. What it has to contain does not change with the name. Google Denmark's is at https://cloud.google.com/terms/data-processing-addendum.

Where is Google Denmark's sub-processor list?

Google Denmark publishes the list of its own sub-processors at https://cloud.google.com/terms/subprocessors. We last opened that link on 31 October 2026.

Which legal entity does Google Denmark contract through?

Google Denmark ApS, registered in Denmark. That is the name to put in a record of processing or a sub-processor list, not the brand.

Does sending personal data to Google Denmark count as a transfer out of the EEA?

No. Google Denmark ApS is registered in Denmark, inside the EEA, so no transfer mechanism is needed to reach it. Where it sends personal data on to is a separate question, and one for its own sub-processor list.

Where is Google Denmark's trust center?

Google Denmark publishes it at https://cloud.google.com/trust-center. A trust center, trust page or security page is the same thing under different names: the vendor's own account of how it protects data, and the place it keeps its certifications. It is Google Denmark's page, so we link to it rather than repeat what it says.

What has changed, and when

Changes we noticed on Google Denmark's own pages, each with the page we saw it on. The vendor does not publish this, and neither does anyone else.

31 October 2026

Google Denmark's subprocessor list now includes Google Cloud Universal Ledger (GCUL), a distributed ledger service for financial institutions, added in the October 30, 2026 version. The data processing agreement was updated to reflect that Transaction Data stored on GCUL cannot be deleted by either the customer or Google during the service term or upon termination, and customers must handle data rectification through subsequent transactions or their own systems rather than requesting deletion.

Seen on https://cloud.google.com/terms/data-processing-addendum

20 October 2026

Google Denmark added subprocessors in India and Malaysia for AI Solutions, Pre-Trained APIs, AI Platform/Gemini platform, Generative AI Services and Agentic AI Services. These countries lack EU adequacy decisions, requiring additional safeguards for personal data transfers under data protection law.

Seen on https://cloud.google.com/terms/subprocessors

Google Denmark: DPA, subprocessors and transfers

What to put in your subprocessor list

Questions people ask about Google Denmark

What has changed, and when

Building your own sub-processor list?

Where to go next

Google Denmark: DPA, subprocessors and transfers

What to put in your subprocessor list

Questions people ask about Google Denmark

What has changed, and when

Building your own sub-processor list?

Where to go next