By accepting these terms, Customer provides general advance authorisation for Google to engage any third-party subprocessors, with Google required to give at least 30 days advance notice of new subprocessors via the Notification Email Address; Customer's only contractual remedy for objecting to a new subprocessor is terminating the Agreement within 90 days.
This analysis describes what Google Ads's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
This provision implements GDPR Article 28(2) general written authorisation for subprocessor engagement and establishes that Customer's sole contractual remedy for objecting to a New Subprocessor is Agreement termination, which compliance teams should evaluate in the context of their own obligations to upstream controllers requiring subprocessor approval rights.
Under this provision, Customer's acceptance of these terms constitutes general advance authorisation for Google to engage any new third-party subprocessors, subject to 30 days advance notification; if Customer objects, the only available contractual remedy is termination of the Agreement within 90 days of receiving the notification.
Cross-platform context
See how other platforms handle Subprocessor Authorisation and Change Notification and similar clauses.
Compare across platforms →"Customer specifically authorises the engagement as Subprocessors of those entities listed as of the Terms Effective Date at the URL specified in Section 11.2 (Information about Subprocessors). In addition, without prejudice to Section 11.4 (Opportunity to Object to Subprocessor Changes) Customer generally authorises the engagement of any other third parties as Subprocessors. When any New Subprocessor is engaged during the Term, Google will, at least 30 days before the New Subprocessor processes any Customer Personal Data, inform Customer of the engagement (including the name and location of the relevant New Subprocessor and the activities it will perform) by sending an email to the Notification Email Address. Customer may object to any New Subprocessor by terminating the Agreement for convenience immediately upon written notice to Google, on condition that Customer provides such notice within 90 days of being informed of the engagement of the New Subprocessor.Excerpt from Google Ads's Data Processing Terms
REGULATORY LANDSCAPE: This provision engages GDPR Article 28(2), which permits general written authorisation for subprocessor engagement provided the processor informs the controller of changes, giving the controller the opportunity to object.
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
Get the research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.
This provision implements GDPR Article 28(2) general written authorisation for subprocessor engagement and establishes that Customer's sole contractual remedy for objecting to a New Subprocessor is Agreement termination, which compliance teams should evaluate in the context of their own obligations to upstream controllers requiring subprocessor approval rights.
Under this provision, Customer's acceptance of these terms constitutes general advance authorisation for Google to engage any new third-party subprocessors, subject to 30 days advance notification; if Customer objects, the only available contractual remedy is termination of the Agreement within 90 days of receiving the notification.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Google Ads.