Google Ads Data Processing Terms

<!DOCTYPE html> <html lang="en"> <head> <meta content="width=device-width, minimum-scale=1, initial-scale=1" name="viewport"> <meta charset="utf-8"> <link href="https://fonts.googleapis.com/css?family=Google+Sans:400,500,700&display=swap&lang=en" rel="stylesheet" nonce="VjdPCupRCLdoDNcXjoUT9Q"> <link href="/static/compiled/index.min.css?cache=0e10251" rel="stylesheet" nonce="VjdPCupRCLdoDNcXjoUT9Q"> <link rel="apple-touch-icon-precomposed" sizes="180x180" href="/static/assets/img/favicon/apple-touch-icon.png"> <link rel="icon" type="image/png" sizes="32x32" href="/static/assets/img/favicon/favicon-32x32.png"> <link rel="icon" type="image/png" sizes="16x16" href="/static/assets/img/favicon/favicon-16x16.png"> <link rel="shortcut icon" href="/static/assets/img/favicon/favicon.ico"> <link href="https://www.gstatic.com/glue/cookienotificationbar/cookienotificationbar.min.css" rel="stylesheet" nonce="VjdPCupRCLdoDNcXjoUT9Q"> <title>Google Ads Data Processing Terms</title> <meta name="robots" content="noindex, nofollow"> <script nonce="VjdPCupRCLdoDNcXjoUT9Q"> (function(i, s, o, g, r, a, m) { i['GoogleAnalyticsObject'] = r; i[r] = i[r] || function() { (i[r].q = i[r].q || []).push(arguments) }, i[r].l = 1 * new Date(); a = s.createElement(o), m = s.getElementsByTagName(o)[0]; a.async = 1; a.src = g; m.parentNode.insertBefore(a, m) })(window, document, 'script', '//www.google-analytics.com/analytics.js', 'ga'); ga('create', 'UA-49447312-51', 'auto'); ga('send', 'pageview'); </script> </head> <body class="glue-body page-body"> <header class="glue-header glue-header--single no-margin" id="glue-header"> <div id="glue-drawer" class="glue-header__bar glue-header__bar--desktop glue-header__drawer"> <div class="glue-header__tier desktop-header-container"> <div class="glue-header__container"> <div class="glue-header__lock-up"> <div class="glue-header__logo"> <a class="glue-header__logo-link" href="../" title="Google" aria-label="Google logo"> <div class="glue-header__logo-container"> <svg role="img" alt="" aria-hidden="true" class="glue-header__logo-svg"> <use xlink:href="/static/assets/img/glue-icons.svg#google-color-logo"></use> </svg> </div> <p class="glue-header__logo--product"> Business Data Responsibility </p> </a> </div> </div> </div> <div class="glue-header__container glue-header__container--flex-auto"> <nav class="glue-header__link-bar"> <ul class="glue-header__list glue-header__link-bar--arrow" id="list-1"> <p class="header-product">Business Data Responsibility</p> <li aria-level="1" class="glue-header__item"> <a class="glue-header__link" href="../" aria-label="Overview"> Overview </a> </li> <li aria-level="1" class="glue-header__item"> <a class="glue-header__link" href="../compliance/" aria-label="Compliance"> Compliance </a> </li> <li aria-level="1" class="glue-header__item"> <a class="glue-header__link" href="../product-controls/" aria-label="Product Controls"> Product Controls </a> </li> <li aria-level="1" class="glue-header__item"> <a class="glue-header__link" href="../data-safety/" aria-label="Data Safety"> Data Safety </a> <ul class="glue-header__list glue-header__list--nested" id="list-2"> <li aria-level="2" class="glue-header__item"> <a class="glue-header__link" href="../data-safety/marketers-and-publishers/" aria-label="For Marketers and Publishers"> For Marketers and Publishers </a> </li> <li aria-level="2" class="glue-header__item"> <a class="glue-header__link" href="../data-safety/built-in-security/" aria-label="Built-in Security"> Built-in Security </a> </li> <li aria-level="2" class="glue-header__item"> <a class="glue-header__link" href="../data-safety/security-and-privacy-all/" aria-label="Security and Privacy for all"> Security and Privacy for all </a> </li> </ul> </li> <li aria-level="1" class="glue-header__item"> <a class="glue-header__link" href="../responsible-innovation/" aria-label="Responsible Innovation"> Responsible Innovation </a> <ul class="glue-header__list glue-header__list--nested" id="list-2"> <li aria-level="2" class="glue-header__item"> <a class="glue-header__link" href="../responsible-innovation/safety-engineering-centre/" aria-label="Safety Engineering Center"> Safety Engineering Center </a> </li> </ul> </li> <li aria-level="1" class="glue-header__item"> <a class="glue-header__link" href="../resources/" aria-label="Resources"> Resources </a> </li> </ul> </nav> </div> <div class="glue-header__container glue-header__container--cta"> <div class="glue-header__cta"> <a class="glue-button glue-button--medium-emphasis" href="https://policies.google.com/privacy" aria-label="Privacy Policy" target="_blank" rel="noopener noreferrer"> Privacy Policy </a> </div> </div> </div> </div> <div class="glue-header__bar glue-header__bar--mobile"> <div class="glue-header__tier"> <div class="glue-header__container hide-desktop"> <div class="glue-header__lock-up"> <div class="glue-header__logo"> <a class="glue-header__logo-link" href="../" title="Google" aria-label="Google logo"> <div class="glue-header__logo-container"> <svg role="img" alt="" aria-hidden="true" class="glue-header__logo-svg"> <use xlink:href="/static/assets/img/glue-icons.svg#google-color-logo"></use> </svg> </div> </a> </div> </div> </div> <div class="glue-header__container"> <div class="glue-header__cta"> <div class="glue-header__hamburger"> <div class="glue-header__hamburger-wrapper"> <button aria-controls="glue-drawer" aria-expanded="false" aria-label="Open the navigation drawer" class="glue-header__drawer-toggle-btn" type="button"> <svg class="glue-icon glue-icon--24px" role="presentation"> <use xlink:href="/static/assets/img/glue-icons.svg#menu"></use> </svg> </button> </div> </div> <div class="glue-header__logo"> <a class="glue-header__logo-link" href="../" title="Business Data Responsibility" aria-label="Business Data Responsibility"> <div class="glue-header__logo-container hide-mobile"> <svg role="img" alt="" aria-hidden="true" class="glue-header__logo-svg"> <use xlink:href="/static/assets/img/glue-icons.svg#google-color-logo"></use> </svg> </div> <p class="glue-header__logo--product"> Business Data Responsibility </p> </a> </div> </div> </div> </div> </div> <div class="glue-header__drawer-backdrop"></div> </header> <div class="terms-banner"> <p class="terms-banner__text"> As of 16 September 2024, when our clients and partners use Google’s Ads Services, Google relies, in certain circumstances, on the Swiss-U.S. Data Privacy Framework and the UK Extension to the EU-U.S. Data Privacy Framework for the transfer of personal information from Switzerland and the UK, respectively, to the U.S. Google has relied, in certain circumstances, on the EU-U.S. Data Privacy Framework for the transfer of personal information to the U.S since 1 September 2023. We have provided more information <a class="terms-banner__link" href="/adsdatatransfers/">here</a> and more information will also be available <a class="terms-banner__link" href="https://policies.google.com/privacy/frameworks" target="_blank" rel="noopener noreferrer">here</a> from the 16 September. </p> </div> <main class="glue-page"> <section class="glue-grid terms-page remove-margin"> <div class="glue-grid__col glue-grid__col--span-12 headline"> <div class="glue-grid"> <div class="glue-grid__col glue-grid__col--span-0-sm glue-grid__col--span-1-lg"></div> <div class="glue-grid__col glue-grid__col--span-4-sm glue-grid__col--span-12-md glue-grid__col--span-12-lg headline-order"> <div> <h1 class="glue-headline glue-headline--headline-1 font-weight-medium spacer-3-4 title-break has-blue-text-child-span"> Google Ads Data Processing Terms </h1> <div class="glue-body headline-description glue-mod-spacer-4-bottom"> <p>Google and the counterparty agreeing to these terms (“<strong>Customer</strong>”) have entered into an agreement for the provision of the Processor Services (as amended from time to time, the “<strong>Agreement</strong>”).</p> <p>These Google Ads Data Processing Terms (including the appendices, “<strong>Data Processing Terms</strong>”) are entered into by Google and Customer and supplement the Agreement. These Data Processing Terms will be effective, and replace any previously applicable terms relating to their subject matter (including any data processing amendment or data processing addendum relating to the Processor Services), from the Terms Effective Date.</p> <p>If you are accepting these Data Processing Terms on behalf of Customer, you warrant that: (a) you have full legal authority to bind Customer to these Data Processing Terms; (b) you have read and understand these Data Processing Terms; and (c) you agree, on behalf of Customer, to these Data Processing Terms. If you do not have the legal authority to bind Customer, please do not accept these Data Processing Terms.</p> </div> </div> </div> </div> </div> <div class="glue-grid__col glue-grid__col--span-0-md glue-grid__col--span-1-lg glue-grid__col--span-1-xl hide-mobile"> </div> <div class="glue-grid__col glue-grid__col--span-12-md content glue-grid__col--span-12"> <div class="content-block"> <h2 class="glue-headline glue-headline--headline-3 title-break glue-mod-spacer-4-bottom"> <span class="oneline-section-heading"><span>1.</span> Introduction</span> </h2> <div class="text-block"> <p>These Data Processing Terms reflect the parties’ agreement on the terms governing the processing of Customer Personal Data.</p> </div> </div> <div class="content-block"> <h2 class="glue-headline glue-headline--headline-3 title-break glue-mod-spacer-4-bottom"> <span class="oneline-section-heading"><span>2.</span> Definitions and Interpretation</span> </h2> <div class="text-block"> <div class="sub-section-content"> <p><span>2.1</span> In these Data Processing Terms:</p> <p>“<strong>Additional Product</strong>” means a product, service or application provided by Google or a third party that: (a) is not part of the Processor Services; and (b) is accessible for use within the user interface of the Processor Services or is otherwise integrated with the Processor Services.</p> <p>“<strong>Additional Terms</strong>” means the additional terms referred to in Appendix 3, which reflect the parties’ agreement on the terms governing the processing of Customer Personal Data in connection with certain Applicable Data Protection Legislation.</p> <p>“<strong>Affiliate</strong>” means an entity that directly or indirectly controls, is controlled by, or is under common control with, a party.</p> <p>“<strong>Applicable Data Protection Legislation</strong>” means, as applicable to the processing of Customer Personal Data, any national, federal, EU, state, provincial or other privacy, data security or data protection law or regulation including European Data Protection Legislation, the LGPD and US State Privacy Laws.</p> <p>“<strong>Customer Personal Data</strong>” means personal data that is processed by Google on behalf of Customer in Google’s provision of the Processor Services.</p> <p>“<strong>Data Incident</strong>” means a breach of Google’s security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Customer Personal Data on systems managed by or otherwise controlled by Google. “Data Incidents” will not include unsuccessful attempts or activities that do not compromise the security of Customer Personal Data, including unsuccessful log-in attempts, pings, port scans, denial of service attacks, and other network attacks on firewalls or networked systems.</p> <p>“<strong>Data Subject Tool</strong>” means a tool (if any) made available by a Google Entity to data subjects that enables Google to respond directly and in a standardised manner to certain requests from data subjects in relation to Customer Personal Data (for example, online advertising settings or an opt-out browser plugin).</p> <p>“<strong>EU GDPR</strong>” means Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC.</p> <p>“<strong>European Data Protection Legislation</strong>” means, as applicable: (a) the GDPR; and/or (b) the Swiss FDPA.</p> <p>“<strong>GDPR</strong>” means, as applicable: (a) the EU GDPR; and/or (b) the UK GDPR.</p> <p>“<strong>Google</strong>” means the Google Entity that is party to the Agreement.</p> <p>“<strong>Google Entity</strong>” means Google LLC, Google Ireland Limited or any other Affiliate of Google LLC.</p> <p>“<strong>Instructions</strong>” has the meaning given in Section 5.2 (Customer’s Instructions).</p> <p>“<strong>ISO 27001 Certification</strong>” means ISO/IEC 27001:2013 certification or a comparable certification for the Processor Services.</p> <p>“<strong>LGPD</strong>” means the Brazilian General Data Protection Law (Lei Geral de Proteção de Dados Pessoais).</p> <p>“<strong>New Subprocessor</strong>” has the meaning given in Section 11.1 (Consent to Subprocessor Engagement).</p> <p>“<strong>Notification Email Address</strong>” means the email address designated by Customer, via the user interface of the Processor Services or such other means provided by Google, to receive certain notifications from Google relating to these Data Processing Terms. </p> <p>“<strong>Processor Services</strong>” means the applicable services listed at <a href="../adsservices/">business.safety.google/adsservices</a>.</p> <p>“<strong>Security Documentation</strong>” means the certificate issued for the ISO 27001 Certification and any other security certifications or documentation that Google may make available in respect of the Processor Services. </p> <p>“<strong>Security Measures</strong>” has the meaning given in Section 7.1.1 (Google’s Security Measures).</p> <p>“<strong>Subprocessors</strong>” means third parties authorised under these Data Processing Terms to have logical access to and process Customer Personal Data in order to provide parts of the Processor Services and any related technical support.</p> <p>“<strong>Swiss FDPA</strong>” means, as applicable, the Federal Data Protection Act of 19 June 1992 (Switzerland) (with the Ordinance to the Federal Data Protection Act of 14 June 1993), or the revised Federal Data Protection Act of 25 September 2020 (with the Ordinance to the Federal Data Protection Act of 31 August 2022). </p> <p>“<strong>Term</strong>” means the period from the Terms Effective Date until the end of Google’s provision of the Processor Services under the Agreement.</p> <p>“<strong>Terms Effective Date</strong>” means the date on which Customer clicked to accept or the parties otherwise agreed to these Data Processing Terms.</p> <p>“<strong>UK GDPR</strong>” means the EU GDPR as amended and incorporated into UK law under the UK European Union (Withdrawal) Act 2018, and applicable secondary legislation made under that Act.</p> <p>“<strong>US State Privacy Laws</strong>” has the meaning found at <a href="../usdataprotectionlaws/">business.safety.google/usdataprotectionlaws</a>.</p> <p><span>2.2</span> The terms “<strong>controller</strong>”, “<strong>data subject</strong>”, “<strong>personal data</strong>”, “<strong>processing</strong>” and “<strong>processor</strong>” as used in these Data Processing Terms have the meanings given by either (a) Applicable Data Protection Legislation; or (b) absent any such meaning or law, the GDPR.</p> <p><span>2.3</span> The words “<strong>include</strong>” and “<strong>including</strong>” mean “including but not limited to”. Any examples in these Data Processing Terms are illustrative and not the sole examples of a particular concept.</p> <p><span>2.4</span> Any reference to a legal framework, statute or other legislative enactment is a reference to it as amended or re-enacted from time to time.</p> <p><span>2.5</span> To the extent any translated version of these Data Processing Terms is inconsistent with the English version, the English version will govern.</p> </div> </div> </div> <div class="content-block"> <h2 class="glue-headline glue-headline--headline-3 title-break glue-mod-spacer-4-bottom"> <span class="oneline-section-heading"><span>3.</span> Duration of these Data Processing Terms</span> </h2> <div class="text-block"> <p>These Data Processing Terms will take effect on the Terms Effective Date. Regardless of whether the Agreement has terminated or expired, these Data Processing Terms will remain in effect until, and automatically expire when, Google deletes all Customer Personal Data as described in these Data Processing Terms.</p> </div> </div> <div class="content-block"> <h2 class="glue-headline glue-headline--headline-3 title-break glue-mod-spacer-4-bottom"> <span class="oneline-section-heading"><span>4.</span> Application of these Data Processing Terms</span> </h2> <div class="text-block"> <div class="section-content"> <p> <span>4.1</span> <strong>General</strong>. These Data Processing Terms will only apply to the Processor Services for which the parties agreed to these Data Processing Terms, for example: (a) the Processor Services for which Customer clicked to accept these Data Processing Terms; or (b) if the Agreement incorporates these Data Processing Terms by reference, the Processor Services that are the subject of the Agreement. </p> <p> <span>4.2</span> <strong>Incorporation of Additional Terms</strong>. The Additional Terms supplement these Data Processing Terms. </p> </div> </div> </div> <div class="content-block"> <h2 class="glue-headline glue-headline--headline-3 title-break glue-mod-spacer-4-bottom"> <span class="oneline-section-heading"><span>5.</span> Processing of Data</span> </h2> <div class="text-block"> <div class="section-content"> <p> <span>5.1</span> <strong>Roles and Regulatory Compliance; Authorisation</strong>. </p> <div class="sub-section-content"> <p> <span>5.1.1</span> <strong>Processor and Controller Responsibilities</strong>. The parties acknowledge and agree that: </p> <div class="sub-section-content"> <p> <span>(a)</span> Appendix 1 describes the subject matter and details of the processing of Customer Personal Data; </p> <p> <span>(b)</span> Google is a processor of Customer Personal Data; </p> <p> <span>(c)</span> Customer is a controller or processor, as applicable, of Customer Personal Data; and </p> <p> <span>(d)</span> each party will comply with the obligations applicable to it under Applicable Data Protection Legislation with respect to the processing of Customer Personal Data. </p> </div> <p> <span>5.1.2</span> <strong>Processor Customers</strong>. If Customer is a processor: </p> <div class="sub-section-content"> <p> <span>(a)</span> Customer warrants on an ongoing basis that the relevant controller has authorised: (i) the Instructions, (ii) Customer’s appointment of Google as another processor, and (iii) Google’s engagement of Subprocessors as described in Section 11 (Subprocessors); </p> <p> <span>(b)</span> Customer will forward to the relevant controller promptly and without undue delay any notice provided by Google under Sections 7.2.1 (Incident Notification) or 11.4 (Opportunity to Object to Subprocessor Changes); and </p> <p> <span>(c)</span> Customer may make available to the relevant controller any information made available by Google under Sections 7.4 (Security Certification), 10.2 (Data Centre Information) and 11.2 (Information about Subprocessors). </p> </div> </div> <p> <span>5.2</span> <strong>Customer’s Instructions</strong>. By entering into these Data Processing Terms, Customer instructs Google to process Customer Personal Data only in accordance with applicable law: (a) to provide the Processor Services and any related technical support; (b) as further specified via Customer’s use of the Processor Services (including in the settings and other functionality of the Processor Services) and any related technical support; (c) as documented in the form of the Agreement (including these Data Processing Terms); and (d) as further documented in any other written instructions given by Customer and acknowledged by Google as constituting instructions for purposes of these Data Processing Terms (collectively, the “<strong>Instructions</strong>”). </p> <p> <span>5.3</span> <strong>Google’s Compliance with Instructions</strong>. Google will comply with the Instructions unless prohibited by applicable laws, or such applicable laws require other processing. </p> <p> <span>5.4</span> <strong>Additional Products</strong>. If Customer uses any Additional Product, the Processor Services may allow that Additional Product to access Customer Personal Data as required for the interoperation of the Additional Product with the Processor Services. For clarity, these Data Processing Terms do not apply to the processing of personal data in connection with the provision of any Additional Product used by Customer, including personal data transmitted to or from that Additional Product. </p> </div> </div> </div> <div class="content-block"> <h2 class="glue-headline glue-headline--headline-3 title-break glue-mod-spacer-4-bottom"> <span class="oneline-section-heading"><span>6.</span> Data Deletion</span> </h2> <div class="text-block"> <div class="section-content"> <p> <span>6.1</span> <strong>Deletion During Term</strong>. </p> <div class="sub-section-content"> <p> <span>6.1.1</span> <strong>Processor Services With Deletion Functionality</strong>. During the Term, if: </p> <div class="sub-section-content"> <p> <span>(a)</span> the functionality of the Processor Services includes the option for Customer to delete Customer Personal Data; </p> <p> <span>(b)</span> Customer uses the Processor Services to delete certain Customer Personal Data; and </p> <p> <span>(c)</span> the deleted Customer Personal Data cannot be recovered by Customer (for example, from the “trash”), </p> </div> <p> then Google will delete such Customer Personal Data from its systems as soon as reasonably practicable and within a maximum period of 180 days, unless applicable laws require storage. </p> <p> <span>6.1.2</span> <strong>Processor Services Without Deletion Functionality</strong>. During the Term, if the functionality of the Processor Services does not include the option for Customer to delete Customer Personal Data, then Google will comply with: </p> <div class="sub-section-content"> <p> <span>(a)</span> any reasonable request from Customer to facilitate such deletion, insofar as this is possible taking into account the nature and functionality of the Processor Services and unless applicable laws require storage; and </p> <p> <span>(b)</span> the data retention practices described at <a href="https://policies.google.com/technologies/ads" rel="noopener noreferrer" target="_blank">policies.google.com/technologies/ads</a>. </p> </div> <p>Google may charge a fee (based on Google’s reasonable costs) for any data deletion under Section 6.1.2(a). Google will provide Customer with further details of any applicable fee, and the basis of its calculation, in advance of any such data deletion. </p> </div> <p> <span>6.2</span> <strong>Deletion on Term Expiry</strong>. Customer instructs Google to delete all remaining Customer Personal Data (including existing copies) from Google’s systems at the end of the Term in accordance with applicable law. Google will comply with this instruction as soon as reasonably practicable and within a maximum period of 180 days, unless applicable laws require storage. </p> </div> </div> </div> <div class="content-block"> <h2 class="glue-headline glue-headline--headline-3 title-break glue-mod-spacer-4-bottom"> <span class="oneline-section-heading"><span>7.</span> Data Security</span> </h2> <div class="text-block"> <div class="section-content"> <p> <span>7.1</span> <strong>Google’s Security Measures and Assistance</strong>. </p> <div class="sub-section-content"> <p> <span>7.1.1</span> <strong>Google’s Security Measures</strong>. Google will implement and maintain technical and organisational measures to protect Customer Personal Data against accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access as described in Appendix 2 (the “<strong>Security Measures</strong>”). As described in Appendix 2, the Security Measures include measures: (a) to encrypt personal data; (b) to help ensure the ongoing confidentiality, integrity, availability and resilience of Google’s systems and services; (c) to help restore timely access to personal data following an incident; and (d) for regular testing of effectiveness. Google may update or modify the Security Measures from time to time, provided that such updates and modifications do not result in the degradation of the overall security of the Processor Services. </p> <p> <span>7.1.2</span> <strong>Access and Compliance</strong>. Google will: (a) authorise its employees, contractors and Subprocessors to access Customer Personal Data only as strictly necessary to comply with the Instructions; (b) take appropriate steps to ensure compliance with the Security Measures by its employees, contractors and Subprocessors to the extent applicable to their scope of performance; and (c) ensure that all persons authorised to process Customer Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality. </p> <p> <span>7.1.3</span> <strong>Google’s Security Assistance</strong>. Google will (taking into account the nature of the processing of Customer Personal Data and the information available to Google) assist Customer in ensuring compliance with Customer’s (or, where Customer is a processor, the relevant controller’s) obligations relating to security of personal data and personal data breaches under Applicable Data Protection Legislation, by: </p> <div class="sub-section-content"> <p> <span>(a)</span> implementing and maintaining the Security Measures in accordance with Section 7.1.1 (Google’s Security Measures); </p> <p> <span>(b)</span> complying with the terms of Section 7.2 (Data Incidents); and </p> <p> <span>(c)</span> providing Customer with the Security Documentation in accordance with Section 7.5 (Verifying Compliance) and the information contained in these Data Processing Terms. </p> </div> </div> <p> <span>7.2</span> <strong>Data Incidents</strong>. </p> <div class="sub-section-content"> <p> <span>7.2.1</span> <strong>Incident Notification</strong>. If Google becomes aware of a Data Incident, Google will: </p> <div class="sub-section-content"> <p> <span>(a)</span> notify Customer of the Data Incident promptly and without undue delay; and </p> <p> <span>(b)</span> promptly take reasonable steps to minimise harm and secure Customer Personal Data. </p> </div> <p> <span>7.2.2</span> <strong>Details of Data Incident</strong>. Notifications made under Section 7.2.1 (Incident Notification) will describe: the nature of the Data Incident including the Customer resources impacted; the measures Google has taken, or plans to take, to address the Data Incident and mitigate its potential risk; the measures, if any, Google recommends that Customer take to address the Data Incident; and details of a contact point where more information can be obtained. If it is not possible to provide all such information at the same time, Google’s initial notification will contain the information then available and further information will be provided without undue delay as it becomes available. </p> <p> <span>7.2.3</span> <strong>Delivery of Notification</strong>. Google will deliver its notification of any Data Incident to the Notification Email Address or, at Google’s discretion (including if Customer has not provided a Notification Email Address), by other direct communication (for example, by phone call or an in-person meeting). Customer is solely responsible for providing the Notification Email Address and ensuring that the Notification Email Address is current and valid. </p> <p> <span>7.2.4</span> <strong>Third Party Notifications</strong>. Customer is solely responsible for complying with incident notification laws applicable to Customer and fulfilling any third party notification obligations related to any Data Incident. </p> <p> <span>7.2.5</span> <strong>No Acknowledgement of Fault by Google</strong>. Google’s notification of or response to a Data Incident under this Section 7.2 (Data Incidents) will not be construed as an acknowledgement by Google of any fault or liability with respect to the Data Incident. </p> </div> <p> <span>7.3</span> <strong>Customer’s Security Responsibilities and Assessment</strong>. </p> <div class="sub-section-content"> <p> <span>7.3.1</span> <strong>Customer’s Security Responsibilities</strong>. Customer agrees that, without prejudice to Google’s obligations under Sections 7.1 (Google’s Security Measures and Assistance) and 7.2 (Data Incidents): </p> <div class="sub-section-content"> <p> <span>(a)</span> Customer is responsible for its use of the Processor Services, including: </p> <div class="sub-section-content"> <p> <span>(i)</span> making appropriate use of the Processor Services to ensure a level of security appropriate to the risk in respect of Customer Personal Data; and </p> <p> <span>(ii)</span> securing the account authentication credentials, systems and devices Customer uses to access the Processor Services; and </p> </div> <p> <span>(b)</span> Google has no obligation to protect Customer Personal Data that Customer elects to store or transfer outside of Google’s and its Subprocessors’ systems. </p> </div> <p> <span>7.3.2</span> <strong>Customer’s Security Assessment</strong>. Customer acknowledges and agrees that the Security Measures implemented and maintained by Google as set out in Section 7.1.1 (Google’s Security Measures) provide a level of security appropriate to the risk in respect of Customer Personal Data, taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of the processing of Customer Personal Data as well as the risks to individuals. </p> </div> <p> <span>7.4</span> <strong>Security Certification</strong>. To evaluate and help ensure the continued effectiveness of the Security Measures, Google will maintain the ISO 27001 Certification. </p> <p> <span>7.5</span> <strong>Verifying Compliance</strong>. To demonstrate compliance by Google with its obligations under these Data Processing Terms, and to assist Customer in verifying Google’s compliance with (i) Customer’s Instructions; (ii) its obligations under these Data Processing Terms; and (iii) its obligations under Applicable Data Protection Legislation, Google will: </p> <div class="sub-section-content"> <p> <span>(a)</span> make the Security Documentation available for review by Customer; </p> <p> <span>(b)</span> provide the information contained in the Data Processing Terms; and </p> <p> <span>(c)</span> provide or otherwise make available, in accordance with Google’s standard practices, other materials concerning the nature of the Processor Services and the processing of Customer Personal Data (for example, help centre materials). Customer may also verify Google’s compliance with its obligations under these Data Processing Terms by reviewing the certificate issued for the ISO 27001 Certification (which reflects the outcome of an audit conducted by a third party auditor). </p> </div> </div> </div> </div> <div class="content-block"> <h2 class="glue-headline glue-headline--headline-3 title-break glue-mod-spacer-4-bottom"> <span class="oneline-section-heading"><span>8.</span> Impact Assessments and Consultations</span> </h2> <div class="text-block"> <p>Google will (taking into account the nature of the processing and the information available to Google) assist Customer in ensuring compliance with Customer’s (or, where Customer is a processor, the relevant controller’s) obligations relating to data protection impact assessments and prior regulatory consultations under Applicable Data Protection Legislation, by:</p> <div class="sub-section-content"> <p><span>(a)</span> providing the Security Documentation in accordance with Section 7.5 (Verifying Compliance);</p> <p><span>(b)</span> providing the information contained in the Agreement (including these Data Processing Terms); and</p> <p><span>(c)</span> providing or otherwise making available, in accordance with Google’s standard practices, other materials concerning the nature of the Processor Services and the processing of Customer Personal Data (for example, help centre materials).</p> </div> </div> </div> <div class="content-block"> <h2 class="glue-headline glue-headline--headline-3 title-break glue-mod-spacer-4-bottom"> <span class="oneline-section-heading"><span>9.</span> Data Subject Rights</span> </h2> <div class="text-block"> <div class="section-content"> <p><span>9.1</span> <strong>Responses to Data Subject Requests</strong>. If Google receives a request from a data subject in relation to Customer Personal Data, Customer authorises Google to, and Google hereby notifies Customer that it will:</p> <div class="sub-section-content"> <p><span>(a)</span> respond directly to the data subject’s request in accordance with the standard functionality of the Data Subject Tool (if the request is made via a Data Subject Tool); or </p> <p><span>(b)</span>advise the data subject to submit their request to Customer, and Customer will be responsible for responding to such request (if the request is not made via a Data Subject Tool).</p> </div> <p><span>9.2</span> <strong>Google’s Data Subject Request Assistance</strong>. Google will assist Customer in fulfilling its (or, where Customer is a processor, the relevant controller’s) obligations under Applicable Data Protection Legislation to respond to requests for exercising the data subject’s rights, in all cases taking into account the nature of the processing of Customer Personal Data and, if applicable, Article 11 of the GDPR, by:</p> <div class="sub-section-content"> <p><span>(a)</span> providing the functionality of the Processor Services;</p> <p><span>(b)</span> complying with the commitments set out in Section 9.1 (Responses to Data Subject Requests); and </p> <p><span>(c)</span> if applicable to the Processor Services, making available Data Subject Tools.</p> </div> <p><span>9.3</span> <strong>Rectification</strong>. If Customer becomes aware that any Customer Personal Data is inaccurate or outdated, Customer will be responsible for rectifying or deleting that data if required by Applicable Data Protection Legislation, including (where available) by using the functionality of the Processor Services.</p> </div> </div> </div> <div class="content-block"> <h2 class="glue-headline glue-headline--headline-3 title-break glue-mod-spacer-4-bottom"> <span class="oneline-section-heading"><span>10.</span> Data Transfers</span> </h2> <div class="text-block"> <div class="section-content"> <p><span>10.1</span> <strong>Data Storage and Processing Facilities</strong>. Subject to any provisions applicable to data transfers set out in the Additional Terms, Google may process Customer Personal Data in any country in which Google or its Subprocessors maintain facilities.</p> <p><span>10.2</span> <strong>Data Centre Information</strong>. Information about the locations of Google data centres is available at <a href="https://www.google.com/about/datacenters/locations/" rel="noopener noreferrer" target="_blank">www.google.com/about/datacenters/locations/</a>.</p> </div> </div> </div> <div class="content-block"> <h2 class="glue-headline glue-headline--headline-3 title-break glue-mod-spacer-4-bottom"> <span class="oneline-section-heading"><span>11.</span> Subprocessors</span> </h2> <div class="text-block"> <div class="section-content"> <p> <span>11.1</span> <strong>Consent to Subprocessor Engagement</strong>. 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 (“<strong>New Subprocessors</strong>”). </p> <p> <span>11.2</span> <strong>Information about Subprocessors</strong>. Information about Subprocessors is available at <a href="../adssubprocessors/">business.safety.google/adssubprocessors</a>. </p> <p> <span>11.3</span> <strong>Requirements for Subprocessor Engagement</strong>. When engaging any Subprocessor, Google will: </p> <div class="sub-section-content"> <p> <span>(a)</span> ensure via a written contract that the Subprocessor only accesses and uses Customer Personal Data to the extent required to perform the obligations subcontracted to it, and does so in accordance with the Agreement (including these Data Processing Terms); and </p> <p> <span>(b)</span> remain fully liable for all obligations subcontracted to, and all acts and omissions of, the Subprocessor. </p> </div> <p> <span>11.4</span> <strong>Opportunity to Object to Subprocessor Changes</strong>. </p> <div class="sub-section-content"> <p> <span>(a)</span> 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. </p> <p> <span>(b)</span> 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 as described in Section 11.4(a). </p> </div> </div> </div> </div> <div class="content-block"> <h2 class="glue-headline glue-headline--headline-3 title-break glue-mod-spacer-4-bottom"> <span class="oneline-section-heading"><span>12.</span>Contacting Google; Processing Records</span> </h2> <div class="text-block"> <div class="section-content"> <p> <span>12.1</span> <strong>Contacting Google</strong>. Customer may contact Google in relation to the exercise of its rights under these Data Processing Terms via the methods described at <a href="https://support.google.com/policies/troubleshooter/9009584" rel="noopener noreferrer" target="_blank">privacy.google.com/businesses/processorsupport</a> or via such other means as may be provided by Google from time to time. Google will provide prompt and reasonable assistance with Customer queries Google receives via such means, and that relate to the processing of Customer Personal Data under the Agreement. </p> <p> <span>12.2</span> <strong>Google’s Processing Records</strong>. Google will keep appropriate documentation of its processing activities as required by Applicable Data Protection Legislation. </p> <p> <span>12.3</span> <strong>Controller Requests</strong>. If Google receives a request or instruction via the methods described in Section 12.1 (or any other method) from a third party purporting to be a controller of Customer Personal Data, Google will advise the third party to contact Customer. </p> </div> </div> </div> <div class="content-block"> <h2 class="glue-headline glue-headline--headline-3 title-break glue-mod-spacer-4-bottom"> <span class="oneline-section-heading"><span>13.</span>Liability</span> </h2> <div class="text-block"> <p> If the Agreement is governed by the laws of: </p> <div class="section-content"> <p> <span>(a)</span> a state of the United States of America, then, regardless of anything else in the Agreement, the total liability of either party towards the other party under or in connection with these Data Processing Terms will be limited to the maximum monetary or payment-based amount at which that party’s liability is capped under the Agreement (and therefore, any exclusion of indemnification claims from the Agreement’s limitation of liability will not apply to indemnification claims under the Agreement relating to the Applicable Data Protection Legislation); or </p> <p> <span>(b)</span> a jurisdiction that is not a state of the United States of America, then the liability of the parties under or in connection with these Data Processing Terms will be subject to the exclusions and limitations of liability in the Agreement. </p> </div> </div> </div> <div class="content-block"> <h2 class="glue-headline glue-headline--headline-3 title-break glue-mod-spacer-4-bottom"> <span class="oneline-section-heading"><span>14.</span> Effect of these Data Processing Terms</span> </h2> <div class="text-block"> <div class="section-content"> <p> <span>14.1</span> <strong>Order of Precedence</strong>. If there is any conflict or inconsistency between the Additional Terms, the remainder of these Data Processing Terms and/or the remainder of the Agreement, then the following order of precedence will apply: </p> <div class="sub-section-content"> <p><span>(a)</span> the Additional Terms (if applicable);</p> <p><span>(b)</span> the remainder of these Data Processing Terms; and</p> <p><span>(c)</span> the remainder of the Agreement.</p> </div> <p>Subject to the amendments in these Data Processing Terms, the Agreement remains in full force and effect.</p> <p> <span>14.2</span> <strong>No Effect on Controller Terms</strong>. These Data Processing Terms will not affect any separate terms between Google and Customer reflecting a controller-controller relationship for a service other than the Processor Services. </p> </div> </div> </div> <div class="content-block"> <h2 class="glue-headline glue-headline--headline-3 title-break glue-mod-spacer-4-bottom"> <span class="oneline-section-heading"><span>15.</span> Changes to these Data Processing Terms</span> </h2> <div class="text-block"> <div class="section-content"> <p> <span>15.1</span> <strong>Changes to URLs</strong>. From time to time, Google may change any URL referenced in these Data Processing Terms and the content at any such URL, except that Google may only change the list of potential Processor Services at <a href="../adsservices/">business.safety.google/adsservices</a>: </p> <div class="sub-section-content"> <p> <span>(a)</span> to reflect a change to the name of a service; </p> <p> <span>(b)</span> to add a new service; or </p> <p> <span>(c)</span> to remove a service (or a feature of a service) where either: (i) all contracts for the provision of that service are terminated; (ii) Google has Customer’s consent; or (iii) the service, or a certain feature of the service, has been recategorised as a controller service. </p> </div> <p> <span>15.2</span> <strong>Changes to Data Processing Terms.</strong> Google may change these Data Processing Terms if the change: </p> <div class="sub-section-content"> <p> <span>(a)</span> is expressly permitted by these Data Processing Terms, including as described in Section 15.1 (Changes to URLs); </p> <p> <span>(b)</span> reflects a change in the name or form of a legal entity; </p> <p> <span>(c)</span> is required to comply with applicable law, applicable regulation, a court order or guidance issued by a governmental regulator or agency, or reflects Google’s adoption of an Alternative Transfer Solution (as defined in Appendix 3A); or </p> <p> <span>(d)</span> does not: (i) result in a degradation of the overall security of the Processor Services; (ii) expand the scope of, or remove any restrictions on, (x) in the case of the Additional Terms, Google’s rights to use or otherwise process the data in scope of the Additional Terms or (y) in the case of the remainder of these Data Processing Terms, Google’s processing of Customer Personal Data, as described in Section 5.3 (Google’s Compliance with Instructions); and (iii) otherwise have a material adverse impact on Customer’s rights under these Data Processing Terms, as reasonably determined by Google. </p> </div> <p> <span>15.3</span> <strong>Notification of Changes</strong>. If Google intends to change these Data Processing Terms under Section 15.2(c) or (d), Google will inform Customer at least 30 days (or such shorter period as may be required to comply with applicable law, applicable regulation, a court order or guidance issued by a governmental regulator or agency) before the change will take effect by either: (a) sending an email to the Notification Email Address; or (b) alerting Customer via the user interface for the Processor Services. If Customer objects to any such change, Customer may immediately terminate the Agreement for convenience by giving written notice to Google within 90 days of being informed by Google of the change. </p> </div> </div> </div> <div class="content-block"> <h2 class="glue-headline glue-headline--headline-3 title-break glue-mod-spacer-4-bottom"> <span class="section-heading">Appendix 1: Subject Matter and Details of the Data Processing</span> </h2> <div class="text-block-start"> <p class="inner-point-heading"> Subject Matter </p> <p> Google’s provision of the Processor Services and any related technical support to Customer. </p> <p class="inner-point-heading"> Duration of the Processing </p> <p> The Term plus the period from the end of the Term until deletion of all Customer Personal Data by Google in accordance with these Data Processing Terms. </p> <p class="inner-point-heading"> Nature and Purpose of the Processing </p> <p> Google will process (including, as applicable to the Processor Services and the Instructions collecting, recording, organising, structuring, storing, altering, retrieving, using, disclosing, combining, erasing and destroying) Customer Personal Data for the purpose of providing the Processor Services and any related technical support to Customer in accordance with these Data Processing Terms. </p> <p class="inner-point-heading"> Types of Personal Data </p> <p> Customer Personal Data may include the types of personal data described at <a href="/adsservices/">business.safety.google/adsservices</a>. </p> <p class="inner-point-heading"> Categories of Data Subjects </p> <p> Customer Personal Data will concern the following categories of data subjects: </p> <div class="sub-section-list"> <ul> <li> <p>data subjects about whom Google collects personal data in its provision of the Processor Services; and/or</p> </li> <li> <p>data subjects about whom personal data is transferred to Google in connection with the Processor Services by, at the direction of, or on behalf of Customer.</p> </li> </ul> </div> <p> Depending on the nature of the Processor Services, these data subjects may include individuals: (a) to whom online advertising has been, or will be, directed; (b) who have visited specific websites or applications in respect of which Google provides the Processor Services; and/or (c) who are customers or users of Customer’s products or services. </p> </div> </div> <div class="content-block"> <h2 class="glue-headline glue-headline--headline-3 title-break glue-mod-spacer-4-bottom"> <span class="section-heading">Appendix 2: Security Measures</span> </h2> <div class="text-block-start"> <p> As from the Terms Effective Date, Google will implement and maintain the Security Measures set out in this Appendix 2. Google may update or modify such Security Measures from time to time, provided that such updates and modifications do not result in the degradation of the overall security of the Processor Services. </p> <div class="sub-section-content"> <p class="inner-point-heading"> <span>1.</span> Data Centre & Network Security </p> <div class="sub-section-content"> <p> <span>(a)</span> <strong>Data Centres</strong>. </p> <p> <strong>Infrastructure</strong>. Google maintains geographically distributed data centres. Google stores all production data in physically secure data centres. </p> <p> <strong>Redundancy</strong>. Infrastructure systems have been designed to eliminate single points of failure and minimise the impact of anticipated environmental risks. Dual circuits, switches, networks or other necessary devices help provide this redundancy. The Processor Services are designed to allow Google to perform certain types of preventative and corrective maintenance without interruption. All environmental equipment and facilities have documented preventative maintenance procedures that detail the process for and frequency of performance in accordance with the manufacturer's or internal specifications. Preventative and corrective maintenance of the data centre equipment is scheduled through a standard process according to documented procedures. </p> <p> <strong>Power</strong>. The data centre electrical power systems are designed to be redundant and maintainable without impact to continuous operations, 24 hours a day, and 7 days a week. In most cases, a primary as well as an alternate power source, each with equal capacity, is provided for critical infrastructure components in the data centre. Backup power is provided by various mechanisms such as uninterruptible power supply (UPS) batteries, which supply consistently reliable power protection during utility brownouts, blackouts, over voltage, under voltage, and out-of-tolerance frequency conditions. If utility power is interrupted, backup power is designed to provide transitory power to the data centre, at full capacity, for up to 10 minutes until the backup generator systems take over. The backup generators are capable of automatically starting up within seconds to provide enough emergency electrical power to run the data centre at full capacity typically for a period of days. </p> <p> <strong>Server Operating Systems</strong>. Google servers use hardened operating systems which are customised for the unique server needs of the business. Data is stored using proprietary algorithms to augment data security and redundancy. Google employs a code review process to increase the security of the code used to provide the Processor Services and enhance the security products in production environments. </p> <p> <strong>Business Continuity</strong>. Google replicates data over multiple systems to help to protect against accidental destruction or loss. Google has designed and regularly plans and tests its business continuity planning/disaster recovery programs. </p> <p> <strong>Encryption Technologies</strong>. Google’s security policies mandate encryption at rest for all user data, including personal data. Data is often encrypted at multiple levels in Google’s production storage stack in data centres, including at the hardware level, without requiring any action by customers. Using multiple layers of encryption adds redundant data protection and allows Google to select the optimal approach based on application requirements. All personal data is encrypted at the storage level, generally using AES256. Google uses common cryptographic libraries which incorporate Google’s FIPS 140-2 validated module, to implement encryption consistently across the Processor Services. </p> <p> <span>(b)</span> <strong>Networks & Transmission</strong>. </p> <p> <strong>Data Transmission</strong>. Data centres are typically connected via high-speed private links to provide secure and fast data transfer between data centres. Further, Google encrypts data transmitted between data centres. This is designed to prevent data from being read, copied, altered or removed without authorisation during electronic transport. Google transfers data via Internet standard protocols. </p> <p> <strong>External Attack Surface</strong>. Google employs multiple layers of network devices and intrusion detection to protect its external attack surface. Google considers potential attack vectors and incorporates appropriate purpose built technologies into external facing systems. </p> <p> <strong>Intrusion Detection</strong>. Intrusion detection is intended to provide insight into ongoing attack activities and provide adequate information to respond to incidents. Google’s intrusion detection involves: </p> <div class="sub-section-content"> <p> <span>1.</span> Tightly controlling the size and make-up of Google’s attack surface through preventative measures; </p> <p> <span>2.</span> Employing intelligent detection controls at data entry points; and </p> <p> <span>3.</span> Employing technologies that automatically remedy certain dangerous situations. </p> </div> <p> <strong>Incident Response</strong>. Google monitors a variety of communication channels for security incidents, and Google’s security personnel will react promptly to known incidents. </p> <p> <strong>Encryption Technologies</strong>. Google makes HTTPS encryption (also referred to as TLS connection) available. Google servers support ephemeral elliptic curve Diffie Hellman cryptographic key exchange signed with RSA and ECDSA. These perfect forward secrecy (PFS) methods help protect traffic and minimise the impact of a compromised key, or a cryptographic breakthrough. </p> </div> <p class="inner-point-heading"> <span>2.</span> Access and Site Controls </p> <div class="sub-section-content"> <p> <span>(a)</span> <strong>Site Controls</strong>. </p> <p> <strong>On-site Data Centre Security Operation</strong>. Google’s data centres maintain an on-site security operation responsible for all physical data centre security functions 24 hours a day, 7 days a week. The on-site security operations personnel monitor Closed Circuit TV (“<strong>CCTV</strong>”) cameras and all alarm systems. On-site security operation personnel perform internal and external patrols of the data centre regularly. </p> <p> <strong>Data Centre Access Procedures</strong>. Google maintains formal access procedures for allowing physical access to the data centres. The data centres are housed in facilities that require electronic card key access, with alarms that are linked to the on-site security operation. All entrants to the data centre are required to identify themselves as well as show proof of identity to on-site security operations. Only authorised employees, contractors and visitors are allowed entry to the data centres. Only authorised employees and contractors are permitted to request electronic card key access to these facilities. Data centre electronic card key access requests must be made in advance and in writing, and require the approval of authorised data centre personnel. All other entrants requiring temporary data centre access must: (i) obtain approval in advance from authorised data centre personnel for the specific data centre and internal areas they wish to visit; (ii) sign in at on-site security operations; and (iii) reference an approved data centre access record identifying the individual as approved. </p> <p> <strong>On-site Data Centre Security Devices</strong>. Google’s data centres employ an electronic card key and biometric access control system that is linked to a system alarm. The access control system monitors and records each individual’s electronic card key and when they access perimeter doors, shipping and receiving, and other critical areas. Unauthorised activity and failed access attempts are logged by the access control system and investigated, as appropriate. Authorised access throughout the business operations and data centres is restricted based on zones and the individual’s job responsibilities. The fire doors at the data centres are alarmed. CCTV cameras are in operation both inside and outside the data centres. The positioning of the cameras has been designed to cover strategic areas including, among others, the perimeter, doors to the data centre building, and shipping/receiving. On-site security operations personnel manage the CCTV monitoring, recording and control equipment. Secure cables throughout the data centres connect the CCTV equipment. Cameras record on-site via digital video recorders 24 hours a day, 7 days a week. The surveillance records are retained for at least 7 days based on activity. </p> <p> <span>(b)</span> <strong>Access Control</strong>. </p> <p> <strong>Infrastructure Security Personnel</strong>. Google has, and maintains, a security policy for its personnel, and requires security training as part of the training package for its personnel. Google’s infrastructure security personnel are responsible for the ongoing monitoring of Google’s security infrastructure, the review of the Processor Services, and responding to security incidents. </p> <p> <strong>Access Control and Privilege Management</strong>. Customer's administrators and users must authenticate themselves via a central authentication system or via a single sign on system in order to use the Processor Services. </p> <p> <strong>Internal Data Access Processes and Policies – Access Policy</strong>. Google’s internal data access processes and policies are designed to prevent unauthorised persons and/or systems from gaining access to systems used to process personal data. Google aims to design its systems to: (i) only allow authorised persons to access data they are authorised to access; and (ii) ensure that personal data cannot be read, copied, altered or removed without authorisation during processing, use and after recording. The systems are designed to detect any inappropriate access. Google employs a centralised access management system to control personnel access to production servers, and only provides access to a limited number of authorised personnel. LDAP, Kerberos and a proprietary system utilising digital certificates are designed to provide Google with secure and flexible access mechanisms. These mechanisms are designed to grant only approved access rights to site hosts, logs, data and configuration information. Google requires the use of unique user IDs, strong passwords, two factor authentication and carefully monitored access lists to minimise the potential for unauthorised account use. The granting or modification of access rights is based on: the authorised personnel’s job responsibilities; job duty requirements necessary to perform authorised tasks; and a need to know basis. The granting or modification of access rights must also be in accordance with Google’s internal data access policies and training. Approvals are managed by workflow tools that maintain audit records of all changes. Access to systems is logged to create an audit trail for accountability. Where passwords are employed for authentication (e.g. login to workstations), password policies that follow at least industry standard practices are implemented. These standards include restrictions on password reuse and sufficient password strength. </p> </div> <p class="inner-point-heading"> <span>3.</span> Data </p> <div class="sub-section-content"> <p> <span>(a)</span> <strong>Data Storage, Isolation & Authentication</strong>. </p> <p> Google stores data in a multi-tenant environment on Google-owned servers. Data, the Processor Services database and file system architecture are replicated between multiple geographically dispersed data centres. Google logically isolates each customer's data. A central authentication system is used across all Processor Services to increase uniform security of data. </p> <p> <span>(b)</span> <strong>Decommissioned Disks and Disk Destruction Guidelines</strong>. </p> <p> Certain disks containing data may experience performance issues, errors or hardware failure that lead them to be decommissioned (“<strong>Decommissioned Disk</strong>”). Every Decommissioned Disk is subject to a series of data destruction processes (the “<strong>Data Destruction Guidelines</strong>”) before leaving Google’s premises either for reuse or destruction. Decommissioned Disks are erased in a multi-step process and verified complete by at least two independent validators. The erase results are logged by the Decommissioned Disk’s serial number for tracking. Finally, the erased Decommissioned Disk is released to inventory for reuse and redeployment. If, due to hardware failure, the Decommissioned Disk cannot be erased, it is securely stored until it can be destroyed. Each facility is audited regularly to monitor compliance with the Data Destruction Guidelines. </p> <p> <span>(c)</span> <strong>Pseudonymous Data</strong>. </p> <p> Online advertising data are commonly associated with online identifiers which on their own are considered ’pseudonymous’ (i.e. they cannot be attributed to a specific individual without the use of additional information). Google has a robust set of policies and technical and organisational controls in place to ensure the separation between pseudonymous data and personally identifiable user information (i.e. information that could be used on its own to directly identify, contact, or precisely locate an individual), such as a user’s Google account data. Google policies only allow for information flows between pseudonymous and personally identifiable data in strictly limited circumstances. </p> <p> <span>(d)</span> <strong>Launch reviews</strong>. </p> <p> Google conducts launch reviews for new products and features prior to launch. This includes a privacy review conducted by specially trained privacy engineers. In privacy reviews, privacy engineers ensure that all applicable Google policies and guidelines are followed, including but not limited to policies relating to pseudonymisation and data retention and deletion. </p> </div> <p class="inner-point-heading"> <span>4.</span> Personnel Security </p> <p> Google personnel are required to conduct themselves in a manner consistent with the company’s guidelines regarding confidentiality, business ethics, appropriate usage, and professional standards. Google conducts reasonably appropriate background checks to the extent legally permissible and in accordance with applicable local labor law and statutory regulations. </p> <p> Personnel are required to execute a confidentiality agreement and must acknowledge receipt of, and compliance with, Google’s confidentiality and privacy policies. Personnel are provided with security training. Personnel handling Customer Personal Data are required to complete additional requirements appropriate to their role. Google’s personnel will not process Customer Personal Data without authorisation. </p> <p class="inner-point-heading"> <span>5.</span> Subprocessor Security </p> <p> Before onboarding Subprocessors, Google conducts an audit of the security and privacy practices of Subprocessors to ensure Subprocessors provide a level of security and privacy appropriate to their access to data and the scope of the services they are engaged to provide. Once Google has assessed the risks presented by the Subprocessor, the Subprocessor is required to enter into appropriate security, confidentiality and privacy contract terms, subject to the requirements set out in Section 11.3 (Requirements for Subprocessor Engagement). </p> </div> </div> </div> <div class="content-block"> <h2 class="glue-headline glue-headline--headline-3 title-break glue-mod-spacer-4-bottom"> <span class="section-heading">Appendix 3: Additional Terms for Applicable Data Protection Legislation</span> </h2> <div class="text-block-start"> <p><strong>PART A - ADDITIONAL TERMS FOR EUROPEAN DATA PROTECTION LEGISLATION</strong></p> <div class="sub-section-content"> <p class="inner-point-heading"> <span>1.</span> Introduction </p> <p> This Appendix 3A will only apply to the extent that the European Data Protection Legislation applies to the processing of Customer Personal Data. </p> <p class="inner-point-heading"> <span>2.</span> Additional Definitions </p> <div class="sub-section-content"> <p><span>2.1</span> In this Appendix 3A:</p> <p>“<strong>Adequate Country</strong>” means: </p> <div class="sub-section-content"> <p> <span>(a)</span> for data processed subject to the EU GDPR: the EEA, or a country or territory recognized as ensuring adequate protection under the EU GDPR; </p> <p> <span>(b)</span> for data processed subject to the UK GDPR: the UK, or a country or territory recognized as ensuring adequate protection under the UK GDPR and the Data Protection Act 2018; and/or </p> <p> <span>(c)</span> for data processed subject to the Swiss FDPA: Switzerland, or a country or territory that is: (i) included in the list of the states whose legislation ensures adequate protection as published by the Swiss Federal Data Protection and Information Commissioner, or (ii) recognized as ensuring adequate protection by the Swiss Federal Council under the Swiss FDPA, </p> </div> <p>in each case, other than on the basis of an optional data protection framework.</p> <p>“<strong>Alternative Transfer Solution</strong>” means a solution, other than SCCs, that enables the lawful transfer of personal data to a third country in accordance with European Data Protection Legislation, for example a data protection framework recognized as ensuring that participating entities provide adequate protection.</p> <p>“<strong>Customer SCCs</strong>” means the SCCs (Controller-to-Processor), the SCCs (Processor-to-Controller), and/or the SCCs (Processor-to-Processor), as applicable.</p> <p>“<strong>EEA</strong>” means the European Economic Area.</p> <p>“<strong>European Laws</strong>” means, as applicable: (a) EU or EU Member State law (if the EU GDPR applies to the processing of Customer Personal Data); (b) the law of the UK or a part of the UK (if the UK GDPR applies to the processing of Customer Personal Data); and (c) the law of Switzerland (if the Swiss FDPA applies to the processing of Customer Personal Data). </p> <p>“<strong>SCCs</strong>” means the Customer SCCs and/or SCCs (Processor-to-Processor, Google Exporter), as applicable.</p> <p>“<strong>SCCs (Controller-to-Processor)</strong>” means the terms at <a href="/adsprocessorterms/sccs/c2p/">business.safety.google/adsprocessorterms/sccs/c2p</a>.</p> <p>“<strong>SCCs (Processor-to-Controller)</strong>” means the terms at <a href="/adsprocessorterms/sccs/p2c/">business.safety.google/adsprocessorterms/sccs/p2c</a>.</p> <p>“<strong>SCCs (Processor-to-Processor)</strong>” means the terms at <a href="/adsprocessorterms/sccs/p2p/">business.safety.google/adsprocessorterms/sccs/p2p</a>.</p> <p>“<strong>SCCs (Processor-to-Processor, Google Exporter)</strong>” means the terms at <a href="/adsprocessorterms/sccs/p2p-intra-group/">business.safety.google/adsprocessorterms/sccs/p2p-intra-group</a>. </p> <p>“<strong>Supervisory Authority</strong>” means, as applicable: (a) a “supervisory authority” as defined in the EU GDPR; and/or (b) the “Commissioner” as defined in the UK GDPR and/or the Swiss FDPA.</p> </div> <div class="sub-section-content"> <p><span>2.2</span>The terms “<strong>data importer</strong>” and “<strong>data exporter</strong>” have the meanings given in the applicable SCCs.</p> </div> <p> <strong><span>3.</span>Processor Customers.</strong> If Customer is a processor, Customer will forward to the relevant controller promptly and without undue delay, any notice that refers to any SCCs. </p> <p> <strong><span>4.</span>European Laws.</strong> Where European Data Protection Legislation applies to Google’s processing of Customer Personal Data, references to “applicable laws” in Sections 5.3 (Google’s Compliance with Instructions), 6.1.1 (Processor Services with Deletion Functionality), 6.1.2(a) (Processor Services without Deletion Functionality) and Section 6.2 (Deletion on Term Expiry), means “European Laws.” </p> <p> <strong><span>5.</span>Instruction Notifications.</strong> Google will immediately notify Customer if, in Google’s opinion: (a) European Laws prohibit Google from complying with an Instruction; (b) an Instruction does not comply with European Data Protection Legislation; or (c) Google is otherwise unable to comply with an Instruction, in each case unless such notice is prohibited by European Law. If Customer is a processor, Customer will immediately forward to the relevant controller any notice provided by Google under this paragraph. This paragraph 5 (Instruction Notifications) does not reduce either party’s rights and obligations elsewhere in the Agreement. </p> <p class="inner-point-heading"> <span>6.</span>Audits of Compliance </p> <div class="sub-section-content"> <p> <span>6.1</span><strong> Customer’s Audit Rights</strong>. </p> <div class="sub-section-content"> <p> <span>(a)</span> Google will allow Customer or a third party auditor appointed by Customer to conduct audits (including inspections) to verify Google’s compliance with its obligations under these Data Processing Terms in accordance with paragraph 6.2 (Additional Business Terms for Audits) of this Appendix 3A. During an audit, Google will make available all information necessary to demonstrate such compliance and contribute to the audits as described in Section 7.4 (Security Certification) and paragraph 6 (Audits of Compliance) of this Appendix 3A. </p> <p> <span>(b)</span> If the SCCs apply under paragraph 7.1 (Restricted European Transfers) of this Appendix 3A, Google will allow Customer (or a third-party auditor appointed by Customer) to conduct audits as described in the SCCs and, during the audit, make available all information required by the SCCs, each in accordance with paragraph 6.2 (Additional Business Terms for Audits) of this Appendix 3A . </p> </div> <p> <span>6.2</span><strong> Additional Business Terms for Audits</strong>. </p> <div class="sub-section-content"> <p> <span>(a)</span> Customer will send any request for an audit under paragraph 6.1(a) or 6.1(b) of this Appendix 3A to Google as described in Section 12.1 (Contacting Google). </p> <p> <span>(b)</span> Following receipt by Google of a request under paragraph 6.2(a) of this Appendix 3A, Google and Customer will discuss and agree in advance on the reasonable start date, scope and duration of, and security and confidentiality controls applicable to, any audit under paragraphs 6.1(a) or 6.1(b) of this Appendix 3A. </p> <p> <span>(c)</span> Google may charge a fee (based on Google’s reasonable costs) for any audit under paragraphs 6.1(a) or 6.1(b) of this Appendix 3A. Google will provide Customer with further details of any applicable fee, and the basis of its calculation, in advance of any such audit. Customer will be responsible for any fees charged by any third party auditor appointed by Customer to execute any such audit. </p> <p> <span>(d)</span> Google may object to any third party auditor appointed by Customer to conduct any audit under paragraph 6.1(a) or 6.1(b) of this Appendix 3A if the auditor is, in Google’s reasonable opinion, not suitably qualified or independent, a competitor of Google or otherwise manifestly unsuitable. Any such objection by Google will require Customer to appoint another auditor or conduct the audit itself. </p> <p> <span>(e)</span> Nothing in these Data Processing Terms will require Google either to disclose to Customer or its third party auditor, or to allow Customer or its third party auditor to access: (i) any data of any other customer of a Google Entity; (ii) any Google Entity’s internal accounting or financial information; (iii) any trade secret of a Google Entity; (iv) any information that, in Google's reasonable opinion, could: (A) compromise the security of any Google Entity’s systems or premises; or (B) cause any Google Entity to breach its obligations under the European Data Protection Legislation or its security and/or privacy obligations to Customer or any third party; or (v) any information that Customer or its third party auditor seeks to access for any reason other than the good faith fulfilment of Customer’s obligations under the European Data Protection Legislation. </p> </div> </div> <p class="inner-point-heading"> <span>7.</span>Data Transfers </p> <div class="sub-section-content"> <p> <span>7.1</span><strong> Restricted European Transfers</strong>. The parties acknowledge that European Data Protection Legislation does not require SCCs or an Alternative Transfer Solution in order to process Customer Personal Data in or transfer it to an Adequate Country. If Customer Personal Data is transferred to any other country, and European Data Protection Legislation applies to the transfers (“<strong>Restricted European Transfers</strong>”), then: </p> <div class="sub-section-content"> <p> <span>(a)</span> if Google has adopted an Alternative Transfer Solution for any Restricted European Transfers, then Google will inform Customer of the relevant solution and ensure that such Restricted European Transfers are made in accordance with that solution; and/or </p> <p> <span>(b)</span> if Google has not adopted, or informs Customer that Google is no longer adopting an Alternative Transfer Solution for any Restricted European Transfers, then: </p> <div class="sub-section-content"> <p> <span>(i)</span> if Google’s address is in an Adequate Country: </p> <div class="sub-section-content"> <p> <span>(A)</span> the SCCs (Processor-to-Processor, Google Exporter) will apply with respect to such Restricted European Transfers from Google to Subprocessors; and </p> <p> <span>(B)</span> in addition, if Customer’s address is not in an Adequate Country, the SCCs (Processor-to-Controller) will apply with respect to Restricted European Transfers between Google and Customer (regardless of whether Customer is a controller and/or a processor); or </p> </div> <p> <span>(ii)</span> if Google’s address is not in an Adequate Country, the SCCs (Controller-to-Processor) and/or SCCs (Processor-to-Processor) will apply (according to whether Customer is a controller and/or processor) with respect to such Restricted European Transfers between Customer and Google. </p> </div> </div> <p> <span>7.2</span><strong>Supplementary Measures and Information</strong>. Google will provide Customer with information relevant to Restricted European Transfers, including information about supplementary measures to protect Customer Personal Data, as described in Section 7.5 (Verifying Compliance), Appendix 2 (Security Measures) and other materials concerning the nature of the Processor Services and the processing of Customer Personal Data (for example, help centre articles). </p> <p> <span>7.3</span><strong>Termination</strong>. If Customer concludes, based on its current or intended use of the Processor Services, that the Alternative Transfer Solution and/or SCCs, as applicable, do not provide appropriate safeguards for Customer Personal Data, then Customer may immediately terminate the Agreement for convenience by notifying Google in writing. </p> <p> <span>7.4</span><strong>Alternative Transfer Solution Adoption and Certification</strong>. Information about Google and/or its Affiliates’ adoption of, or certification under, any Alternative Transfer Solutions can be found at <a href="/adsdatatransfers"> https://business.safety.google/adsdatatransfers</a>. </p> </div> <p> <strong><span>8.</span>Subprocessors</strong>. When engaging any Subprocessor, Google will ensure via a written contract that if the processing of Customer Personal Data is subject to European Data Protection Legislation, the data protection obligations in these Data Processing Terms (as referred to in Article 28(3) of the GDPR, if applicable) are imposed on the Subprocessor. </p> <p class="inner-point-heading"> <span>9.</span> Google’s Processing Records. </p> <p> Customer acknowledges that Google is required under the GDPR to: </p> <div class="sub-section-content"> <p> <span>(a)</span> collect and maintain records of certain information, including: (i) the name and contact details of each processor and/or controller on behalf of which Google is acting and (if applicable) of such processor’s or controller's local representative and data protection officer, and (ii) if applicable under the Customer SCCs, Customer’s Supervisory Authority; and </p> <p> <span>(b)</span> make such information available to any Supervisory Authority. Accordingly, Customer will, where requested and as applicable to Customer, provide such information to Google via the user interface of the Processor Services or via such other means as may be provided by Google, and will use such user interface or other means to ensure that all information provided is kept accurate and up-to-date. </p> </div> <p class="inner-point-heading"> <span>10.</span> SCCs </p> <div class="sub-section-content"> <p> <span>10.1</span><strong>Order of Precedence</strong>. If there is any conflict or inconsistency between the Customer SCCs and this Appendix 3A, the remainder of these Data Processing Terms or the remainder of the Agreement, then the Customer SCCs will prevail. </p> <p> <span>10.2</span><strong>No Modification of SCCs</strong>. Nothing in the Agreement (including these Data Processing Terms) is intended to modify or contradict any SCCs or prejudice the fundamental rights or freedoms of data subjects under the European Data Protection Legislation. </p> </div> <p> <strong><span>11.</span>Changes to SCCs</strong>. Google may only change the SCCs in accordance with Sections 15.2(b) - 15.2(d) (Changes to Data Processing Terms) or to incorporate any new version of the SCCs that may be adopted under the European Data Protection Legislation, in each case in a manner that does not affect the validity of the SCCs under the European Data Protection Legislation. </p> </div> <p><strong>PART B - ADDITIONAL TERMS FOR US STATE PRIVACY LAWS</strong></p> <div class="sub-section-content"> <p class="inner-point-heading"> <span>1.</span> Introduction </p> <p> Google may offer and Customer may enable certain in-product settings, configurations or other functionality for the Processor Services relating to restricted data processing, as described in supporting documentation available at <a href="/rdp/">business.safety.google/rdp</a>, as updated from time to time (“<strong>Restricted Data Processing</strong>”). This Appendix 3B reflects the parties’ agreement on the processing of Customer Personal Data and Deidentified Data (as defined below) pursuant to the Agreement in connection with the US State Privacy Laws, and is effective solely to the extent each US State Privacy Law applies. </p> <p class="inner-point-heading"> <span>2.</span> Additional Definitions and Interpretation </p> <p> In this Appendix 3B: </p> <div class="sub-section-content"> <p> <span>(a)</span>“<strong>Deidentified Data</strong>” means data information that is “deidentified” (as that term is defined by the CCPA) and “de-identified data” (as defined by other US State Privacy Laws), when disclosed by one party to the other. </p> <p> <span>(b)</span>“<strong>RDP Instructions</strong>” means, collectively, the Instructions (as defined in these Data Processing Terms) and Customer’s instructions to Google to process Customer Personal Data as permitted under US State Privacy Laws for service providers and processors. </p> <p> <span>(c)</span>“<strong>RDP Services</strong>” means Processor Services operating under Restricted Data Processing. </p> <p> <span>(d)</span> the terms “<strong>business</strong>”, “<strong>consumer</strong>”, “<strong>personal information</strong>”, “<strong>sale(s)</strong>”, “<strong>sell</strong>”, “<strong>service provider</strong>”, and “<strong>share</strong>” as used in this Appendix 3B have the meanings given in the applicable US State Privacy Laws. </p> <p> <span>(e)</span> Customer is solely liable for its compliance with each of the US State Privacy Laws in its use of Google services, including Restricted Data Processing. </p> </div> <p class="inner-point-heading"> <span>3.</span> Applicable State Privacy Law Terms (under Restricted Data Processing). </p> <div class="sub-section-content"> <p> <span>3.1</span>With respect to Customer Personal Data processed under Restricted Data Processing, and to the extent that one or more of the US State Privacy Laws applies to the processing of Customer Personal Data: </p> <div class="sub-section-content"> <span>3.1.1</span><strong>Roles and Regulatory Compliance; Authorization.</strong> <div class="sub-section-content"> <p> <span>(a)</span><strong>Processor and Controller Responsibilities.</strong>The parties acknowledge and agree that: </p> <div class="sub-section-content"> <p> <span>(i)</span>Appendix 1 of these Data Processing Terms describes the subject matter and details of the processing of Customer Personal Data, subject to the following modifications: </p> <div class="sub-section-content"> <p><span>(1)</span>All references to “Processor Services” are replaced with “RDP Services”; and</p> <p><span>(2)</span>The “Types of Personal Data” section is replaced with the following language: “Customer Personal Data may include the types of personal data described under the US State Privacy Laws.”</p> </div> <p> <span>(ii)</span>Google is a service provider and processor of Customer Personal Data under the US State Privacy Laws; and </p> <p> <span>(iii)</span>Customer is a controller or processor, as applicable, of Customer Personal Data under the US State Privacy Laws. </p> </div> <p> <span>(b)</span><strong>Processor Customers.</strong> If Customer is a processor: </p> <div class="sub-section-content"> <p> <span>(i)</span>Customer warrants on an ongoing basis that the relevant controller has authorized: (A) the Instructions, (B) Customer’s appointment of Google as another processor, and (C) Google’s engagement of subcontractors as described in paragraph 3.4 (Subcontractors) of this Appendix 3B. </p> <p> <span>(ii)</span>Customer will immediately forward to the relevant controller any notice provided by Google under Section 7.2.1 (Incident Notification) of these Data Protection Terms and paragraph 3.4 (Subcontractors) of this Appendix 3B. </p> <p> <span>(iii)</span>Customer may make available to the relevant controller any information made available by Google under paragraphs 3.2(b) (Customer’s Audit Rights) and 3.4 (Subcontractors) of this Appendix 3B. </p> </div> </div> <p> <span>3.1.2</span><strong>Customer’s Instructions for RDP Services.</strong> By entering into this Appendix 3B, and with respect to the RDP Services, Customer instructs Google to process Customer Personal Data only in accordance with the RDP Instructions. </p> <p> <span>3.1.3</span><strong>Google’s Compliance with RDP Instructions.</strong> With respect to the RDP Services, Google will comply with the RDP Instructions unless prohibited under the US State Privacy Laws. </p> <p> <span>3.1.4</span><strong> Additional Products. </strong> If Customer uses any product, service or application provided by Google or a third party that: (a) is not part of the RDP Services; and (b) is accessible for use within the user interface of the RDP Services or is otherwise integrated with the RDP Services (an “<strong>Additional Product</strong>”), the RDP Services may allow that Additional Product to access Customer Personal Data as required for the interoperation of the Additional Product with the RDP Services. For clarity, this Appendix 3B does not apply to the processing of personal data in connection with the provision of any Additional Product used by Customer, including personal data transmitted to or from that Additional Product. </p> </div> </div> <div class="sub-section-content"> <p> <span>3.2</span><strong>Data Security</strong> </p> <div class="sub-section-content"> <span>3.2.1</span><strong>Customer’s Security Responsibilities and Assessment.</strong> <div class="sub-section-content"> <p> <span>(a)</span><strong>Customer’s Security Responsibilities.</strong> In addition to Customer’s security responsibilities under Section 7.3.1 of these Data Processing Terms, Customer agrees that, without prejudice to Google’s obligations under Sections 7.1 (Google’s Security Measures and Assistance) and 7.2 (Data Incidents) of these Data Processing Terms, Customer is responsible for its use of the RDP Services, including: (1) making appropriate use of the RDP Services to ensure a level of security appropriate to the risk in respect of Customer Personal Data; and (2) securing the account authentication credentials, systems and devices Customer uses to access the RDP Services. </p> <p> <span>(b)</span><strong>Customer’s Audit Rights.</strong> </p> <div class="sub-section-content"> <p> <span>(i)</span>Customer may conduct an audit to verify Google’s compliance with its obligations under this Appendix 3B by requesting and reviewing (1) a certificate issued for security verification reflecting the outcome of an audit conducted by a third party auditor (e.g., SOC 2 Type II or ISO/IEC 27001 certification or a comparable certification or other security certification of an audit conducted by a third-party auditor agreed by Customer and Google) within 12 months as of the date of Customer’s request and (2) any other information Google determines is reasonably necessary for Customer to verify such compliance. </p> <p> <span>(ii)</span>Alternatively, Google may, at its sole discretion and in response to a request by Customer, initiate a third-party audit to verify Google’s compliance with its obligations under this Appendix 3B. During such an audit, Google will make available to the third-party auditor all information necessary to demonstrate such compliance. Where Customer requests such an audit, Google may charge a fee (based on Google’s reasonable costs) for any audit. Google will provide Customer with further details of any applicable fee, and the basis of its calculation, in advance of any such audit. Customer will be responsible for any fees charged by any third-party auditor appointed by Customer to execute any such audit. </p> <p> <span>(iii)</span>Nothing in this Appendix 3B will require Google either to disclose to Customer or its third-party auditor, or to allow Customer or its third-party auditor to access: </p> <div class="sub-section-content"> <p> <span>(1)</span>any data of any other customer of a Google Entity; </p> <p> <span>(2)</span>any Google Entity’s internal accounting or financial information; </p> <p> <span>(3)</span>any trade secret of a Google Entity; </p> <p> <span>(4)</span>any information that, in Google's reasonable opinion, could: (A) compromise the security of any Google Entity’s systems or premises; or (B) cause any Google Entity to breach its obligations under the US State Privacy Laws or its security and/or privacy obligations to Customer or any third party; or </p> <p> <span>(5)</span>any information that Customer or its third party auditor seeks to access for any reason other than the good faith fulfillment of Customer’s obligations under the US State Privacy Laws. </p> </div> </div> </div> </div> <p> <span>3.3</span><strong>Data Subject Rights.</strong> For the purposes of this Appendix 3B, Google will adhere to the procedures set forth under Section 9 (Data Subject Requests) to the extent such requests, requests for assistance, or rectification is applicable to the RDP Services. </p> <p> <span>3.4</span><strong>Subcontractors.</strong> </p> <div class="sub-section-content"> <p> <span>(a)</span> Customer generally authorizes Google to engage other entities as subcontractors in connection with the provision of the RDP Services. When engaging any subcontractor, Google will: </p> <div class="sub-section-content"> <p> <span>(i)</span> ensure via a written contract that: (A) the subcontractor only accesses and uses Customer Personal Data to the extent required to perform the obligations subcontracted to it, and does so in accordance with the Agreement (including this Appendix 3B); and (B) if the processing of Customer Personal Data is subject to the US State Privacy Laws, ensure that the data protection obligations in this Appendix 3B are imposed on the subcontractor; </p> <p> <span>(ii)</span> when engaging any new subcontractors, provide notice of such new subcontractors where required by US State Privacy Laws, and, where required by US State Privacy Laws, further provide an opportunity for Customer to object to such subcontractors; and </p> <p> <span>(iii)</span> remain fully liable for all obligations subcontracted to, and all acts and omissions of, the subcontractor. </p> </div> <p> <span>(b)</span> Customer may object to any new subcontractor 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 subcontractor as described in paragraph 3.4(a)(ii) herein. </p> </div> </div> <p class="inner-point-heading"> <span>4.</span> US State Privacy Law Terms </p> <div class="sub-section-content"> <p> <span>4.1</span><strong>Deidentified Data.</strong> With respect to Customer Personal Data processed with or without Restricted Data Processing enabled, and to the extent that one or more of the US State Privacy Laws applies to the processing of Customer Personal Data, each party will comply with the requirements for processing Deidentified Data set out in the US State Privacy Laws, with respect to any Deidentified Data it receives from the other party pursuant to the Agreement. For purposes of this paragraph 4.1 (Deidentified Data), Customer Personal Data means any personal data that is processed by a party under the Agreement in connection with its provision or use of the Processor Services. </p> </div> <p class="inner-point-heading"> <span>5.</span> Google’s CCPA Obligations. </p> <div class="sub-section-content"> <p> <span>5.1</span>With respect to Customer Personal Data processed under Restricted Data Processing and to the extent that CCPA applies to such processing of Customer Personal Data, Google will act as Customer’s service provider, and as such, unless otherwise permitted for service providers under CCPA, as reasonably determined by Google: </p> <div class="sub-section-content"> <p> <span>(i)</span>Google will not sell or share any Customer Personal Data that it obtains from Customer in connection with the Agreement; </p> <p> <span>(ii)</span>Google will not retain, use or disclose Customer Personal Data (including outside of the direct business relationship between Google and Customer), other than for a business purpose under the CCPA on behalf of Customer and the specific purpose of performing the RDP Services, as further described in supporting documentation available at <a href="/rdp/">business.safety.google/rdp</a>, as updated from time to time; </p> <p> <span>(iii)</span>Google will not combine Customer Personal Data that Google receives from, or on behalf of, Customer with (a) personal information that Google receives from, or on behalf of, another person or persons or (b) personal information collected from Google’s own interaction with a consumer, as further described in supporting documentation available at <a href="/rdp/">business.safety.google/rdp</a> except to the extent permitted under CCPA; </p> <p> <span>(iv)</span>Google will process such Customer Personal Data for the specific purpose of performing the RDP Services, as further described in the Agreement and supporting documentation (e.g., help center articles), or as otherwise permitted under the CCPA, and the parties agree that Customer is making such Customer Personal Data available to Google for such purposes; </p> <p> <span>(v)</span>Google will allow audits to verify Google’s compliance with its obligations under this Appendix 3B in accordance with paragraph 3.2.1(b) (Customer’s Audit Rights) of this Appendix 3B; </p> <p> <span>(vi)</span>Google will notify Customer if Google makes a determination that it can no longer meet its obligations under the CCPA. This paragraph 5.1(vi) does not reduce either party’s rights and obligations elsewhere in the Agreement; </p> <p> <span>(vii)</span>If Customer reasonably believes that Google is processing Customer Personal Data in an unauthorized manner, Customer has the right to notify Google of such belief via the methods described at <a href="https://support.google.com/policies/troubleshooter/9009584" rel="noopener noreferrer" target="_blank">privacy.google.com/businesses/processorsupport</a>, and the parties will work together in good faith to remediate the allegedly violative processing activities, if necessary; and </p> <p> <span>(viii)</span>Google will comply with applicable obligations under CCPA and will provide the same level of privacy protection as is required by CCPA. </p> </div> <p> <span>5.2</span> With respect to Customer Personal Data processed without Restricted Data Processing enabled, and to the extent that CCPA applies to the processing of Customer Personal Data: </p> <div class="sub-section-content"> <p> <span>(i)</span>Google will process such Customer Personal Data for the specific purpose of performing the Processor Services, as further described in the Agreement and supporting documentation (e.g., help center articles), or as otherwise permitted under the CCPA, and the parties agree that Customer is making such Customer Personal Data available to Google for such purposes; </p> <p> <span>(ii)</span>Google will allow audits to verify Google’s compliance with its obligations under this Appendix 3B in accordance with paragraph 3.2.1(b) (Customer’s Audit Rights) herein. </p> <p> <span>(iii)</span>Google will notify Customer if Google makes a determination that it can no longer meet its obligations under the CCPA; </p> <p> <span>(iv)</span>If Customer reasonably believes that Google is processing Customer Personal Data in an unauthorized manner, Customer has the right to notify Google of such belief via the methods described at <a href="https://support.google.com/policies/troubleshooter/9009584" rel="noopener noreferrer" target="_blank">privacy.google.com/businesses/processorsupport</a>, and the parties will work together in good faith to remediate the allegedly violative processing activities, if necessary; and </p> <p> <span>(v)</span>Google will comply with applicable obligations under CCPA and will provide the same level of privacy protection as is required by CCPA. </p> </div> </div> <p> <span>6.</span><strong> Changes to this Appendix 3B.</strong> In addition to Section 15 of the Data Processing Terms (Changes to these Data Processing Terms), Google may change this Appendix 3B without notice if the change (a) is based on applicable law, applicable regulation, a court order, or guidance issued by a governmental regulator or agency or (b) does not have a material adverse impact on Customer under the US State Privacy Laws, as reasonably determined by Google. </p> </div> </div> </div> <div class="content-block"> <div class="text-block-start"> <div> <p> <em>Google Ads Data Processing Terms, Version 8.0</em> </p> <p> <em>30 May 2024</em> </p> <p class="previous-text" id="previous-versions"> <strong>Previous Versions</strong> </p> </div> </div> </div> <div class="list-spacing"> <ul> <li> <a href="https://kstatic.googleusercontent.com/files/37102bb611b6527b5f0f50d036a6dec5f9fc21b6df9a3fb4b36fc34ff156d3dddc0ca6392126d8fd6258d91d527e3ba4d8e8d8be88ee1a9ebda40c8420df8a34 " aria-label="1 September 2023" target="_blank" rel="noopener noreferrer"> 1 September 2023 </a> </li> <li> <a href="https://kstatic.googleusercontent.com/files/c0b55bfe1a6947dfba9722292599e93a68c8db3ba9014681e02d7ec3930a58c4f713ff1743e04c4db7112de3eeca02bf333bce0ba155a71a0373a647f97f430d " aria-label="1 July 2023" target="_blank" rel="noopener noreferrer"> 1 July 2023 </a> </li> <li> <a href="https://kstatic.googleusercontent.com/files/f92144b084f3127939d03bb4c9bc8d3d02a691cb814f794b6e58252785939b298b3a4b7c4567b77573ad7ee5371f02854445d2d983224b4351c039a33a52d9c6 " aria-label="1 January 2023" target="_blank" rel="noopener noreferrer"> 1 January 2023 </a> </li> <li> <a href="https://kstatic.googleusercontent.com/files/baf7b2323f74430725d717b9d5e9e3b8ffc0d7cc44cb30133b28d3e39ef7e83268e5edf34e757eabe35287be5897268746e55fda9d4da6d6fc4ecec6b5615cf5 " aria-label="21 September 2022" target="_blank" rel="noopener noreferrer"> 21 September 2022 </a> </li> <li> <a href="/static/assets/pdf/adsprocessorterms-20210927.pdf" aria-label="27 September 2021"> 27 September 2021 </a> </li> <li> <a href="/adsprocessorterms-20200816/" aria-label="16 August 2020" target="_blank" rel="noopener noreferrer"> 16 August 2020 </a> </li> <li> <a href="/static/assets/pdf/adsprocessorterms-20200812.pdf" aria-label="12 August 2020" target="_blank" rel="noopener noreferrer"> 12 August 2020 </a> </li> <li> <a href="/static/assets/pdf/adsprocessorterms-20200101.pdf" aria-label="1 January 2020" target="_blank" rel="noopener noreferrer"> 1 January 2020 </a> </li> <li> <a href="/static/assets/pdf/adsprocessorterms-20191031.pdf" aria-label="31 October 2019" target="_blank" rel="noopener noreferrer"> 31 October 2019 </a> </li> <li> <a href="/static/assets/pdf/adsprocessorterms-20171012.pdf" aria-label="12 October 2017" target="_blank" rel="noopener noreferrer"> 12 October 2017 </a> </li> </ul> </div> </div> <div class="glue-grid__col glue-grid__col--span-0-md glue-grid__col--span-1-lg glue-grid__col--span-1-xl hide-mobile"> </div> </section> </main> <footer class="glue-footer"> <h2 class="glue-mod-visually-hidden">Footer links</h2> <section class="glue-footer__global"> <div class="glue-footer__logo"> <a class="false" href="https://www.google.com" rel="noopener noreferrer" target="_blank" title="Google"> <svg aria-hidden="true" class="glue-footer__logo-img" role="presentation"> <use xlink:href="/static/assets/img/glue-icons.svg#google-solid-logo"></use> </svg> </a> </div> <ul class="glue-footer__global-links glue-no-bullet" role="list"> <li class="glue-footer__global-links-list-item"> <a class="glue-footer__link" href="https://about.google/" aria-label="About Google" rel="noopener noreferrer" target="_blank"> About Google </a> </li> <li class="glue-footer__global-links-list-item"> <a class="glue-footer__link" href="https://about.google/products/" aria-label="Google Products" rel="noopener noreferrer" target="_blank"> Google Products </a> </li> <li class="glue-footer__global-links-list-item"> <a class="glue-footer__link" href="https://policies.google.com/privacy" aria-label="Privacy" rel="noopener noreferrer" target="_blank"> Privacy </a> </li> <li class="glue-footer__global-links-list-item"> <a class="glue-footer__link" href="https://policies.google.com/terms" aria-label="Terms" rel="noopener noreferrer" target="_blank"> Terms </a> </li> </ul> <ul class="glue-footer__global-links glue-footer__global-links--extra glue-no-bullet" role="list"> <li class="glue-footer__global-links-list-item glue-footer__global-links-list-item--extra"> <a class="glue-footer__link false" href="https://support.google.com/" target="_blank" rel="noopener noreferrer"> <svg aria-hidden="true" class="glue-icon glue-icon--24px glue-icon--footer-help" role="img" alt=""> <use xlink:href="/static/assets/img/glue-icons.svg#help"></use> </svg> Help </a> </li> <li class="glue-footer__global-links-list-item glue-footer__global-links-list-item--extra"> <select aria-label="Change Language" name="lang-selector" id="lang-selector" class="glue-form__dropdown glue-footer__lang-dropdown"> <option value="/adsprocessorterms/" selected>English</option> <option value="/intl/de/adsprocessorterms/">Deutsch</option> <option value="/intl/es/adsprocessorterms/">Español</option> <option value="/intl/fr/adsprocessorterms/">Français</option> <option value="/intl/it/adsprocessorterms/">Italiano</option> <option value="/intl/ja/adsprocessorterms/">日本語</option> <option value="/intl/nl/adsprocessorterms/">Nederlands</option> <option value="/intl/pt-BR/adsprocessorterms/">Português (Brasil)</option> </select> </li> </ul> </section> </footer> <script src="/static/compiled/index.min.js?cache=0f654b5" nonce="VjdPCupRCLdoDNcXjoUT9Q"></script> <script src="https://www.gstatic.com/glue/cookienotificationbar/cookienotificationbar.min.js" data-glue-cookie-notification-bar-category="2B" data-glue-cookie-notification-bar-language="en" data-glue-cookie-notification-bar-site-id="business.safety.google" nonce="VjdPCupRCLdoDNcXjoUT9Q"> </script> </body> </html>

CINXE.COM

Google Ads Data Processing Terms