CINXE.COM

<!DOCTYPE html><html lang="en" dir="ltr"><head><script type="text/javascript" src="/_static/js/bundle-playback.js?v=HxkREWBo" charset="utf-8"></script> <script type="text/javascript" src="/_static/js/wombat.js?v=txqj7nKC" charset="utf-8"></script> <script type="text/javascript"> __wm.init("http://web.archive.org/web"); __wm.wombat("https://www.youtube.com/t/terms_dataprocessing","20230305211917","http://web.archive.org/","web","/_static/", "1678051157"); </script> <link rel="stylesheet" type="text/css" href="/_static/css/banner-styles.css?v=S1zqJCYt" /> <link rel="stylesheet" type="text/css" href="/_static/css/iconochive.css?v=3PDvdIFv" />  <script type="text/javascript" src="/_static/js/jwplayer/jwplayer.js?v=hiYhl5rb" charset="utf-8"></script> <script type="text/javascript" src="/_static/js/bundle-video.js?v=TFNEreMA" charset="utf-8"></script> <script type="text/javascript"> _wmVideos_.init({ prefix:"/web" }); </script>  <base href="http://web.archive.org/web/20230305211917/https://www.youtube.com/"><link rel="shortcut icon" href="http://web.archive.org/web/20230305211917im_/https://www.youtube.com/img/favicon.ico" type="image/x-icon"><link rel="icon" href="http://web.archive.org/web/20230305211917im_/https://www.youtube.com/img/favicon_32.png" sizes="32x32"><link rel="icon" href="http://web.archive.org/web/20230305211917im_/https://www.youtube.com/img/favicon_48.png" sizes="48x48"><link rel="icon" href="http://web.archive.org/web/20230305211917im_/https://www.youtube.com/img/favicon_96.png" sizes="96x96"><link rel="icon" href="http://web.archive.org/web/20230305211917im_/https://www.youtube.com/img/favicon_144.png" sizes="144x144"><link href="http://web.archive.org/web/20230305211917cs_/https://fonts.googleapis.com/css?family=YouTube+Sans:600" rel="stylesheet" nonce="9oj8Zp0rf2WF1SR32F7Feg"/><link href="http://web.archive.org/web/20230305211917cs_/https://fonts.googleapis.com/css?family=Roboto:400,500" rel="stylesheet" nonce="9oj8Zp0rf2WF1SR32F7Feg"/><style nonce="9oj8Zp0rf2WF1SR32F7Feg">*{box-sizing:border-box}a,body,div,h1,h2,h3,h4,h5,h6,html,img,li,ol,p,span,ul{margin:0;padding:0;border:0;font-size:100%;background:transparent}html,body,#body-wrapper{height:100%}body{background:white;color:#0d0d0d;font-family:'Roboto',sans-serif;font-weight:400;white-space:inherit;overflow:inherit;text-overflow:inherit;text-decoration:none;text-rendering:optimizeLegibility}#body-wrapper{height:auto;min-height:100%;padding-bottom:65px;position:relative}#header{height:56px;padding:16px 24px;background-color:rgba(256,256,256,0.98);position:relative}#logo-icon{top:18px;left:24px}.rtl #logo-icon{left:initial;right:24px}.country-code{font-size:10px;margin:0 2px 0}#main-content{max-width:768px;position:absolute;margin-left:300px;margin-top:-20px;padding-bottom:48px}.rtl #main-content{margin-left:initial;margin-right:300px}#main-sidebar{float:left;width:300px;padding-top:48px;padding-right:24px}.rtl #main-sidebar{float:right;padding-left:24px;padding-right:initial}#main-sidebar ul{list-style:none}#chromeless-content{padding:32px;margin-top:-40px}#chromeless-footer{padding:0 32px}#chromeless-footer p{border-top:1px solid #ccc;padding:20px 32px;margin-bottom:0}h1.title{font-family:'YouTube Sans',sans-serif;font-weight:600;margin-bottom:16px;font-size:48px;line-height:56px}h1{font-family:'YouTube Sans',sans-serif;font-size:24px;font-weight:600;line-height:30px;margin-bottom:24px}h2,h3{font-family:'YouTube Sans',sans-serif;font-size:16px;font-weight:600;line-height:24px;margin-bottom:16px}h4{font-size:16px;font-weight:500;line-height:24px;margin-bottom:12px}p,ul,ol,li{font-size:16px;font-weight:400;line-height:24px}li{margin-left:32px;margin-bottom:12px}.rtl li{margin-left:initial;margin-right:32px}p,ul,ol{margin-bottom:24px}a{text-decoration:none;cursor:pointer}b,strong{font-weight:500}.summary,.banner{background:#e9e9e9;border:1px solid #535353;padding:12px;margin-bottom:24px}</style><title lang="en" dir="ltr">YouTube Data Processing Terms</title></head><body class="ltr"><div id="body-wrapper"><div id="header"><a id="logo" href="/web/20230305211917/https://www.youtube.com/" alt="YouTube home" title="YouTube home"><img id="logo-icon" height="20px" src="http://web.archive.org/web/20230305211917im_/https://www.youtube.com/img/desktop/supported_browsers/yt_logo_rgb_light.png" alt="YouTube"/></a></div><div id="main-sidebar"><ul><li><a href="/web/20230305211917/https://www.youtube.com/t/terms">Terms of Service</a></li><li><a href="/web/20230305211917/https://www.youtube.com/t/terms_paidservice">Paid Service Terms of Service</a></li><li><a href="/web/20230305211917/https://www.youtube.com/t/usage_paycontent">Paid Service Usage Rules</a></li><li><a href="/web/20230305211917/https://www.youtube.com/t/policy_cns">Collecting Society Notices</a></li><li><a href="/web/20230305211917/https://www.youtube.com/t/copyright_notice">Copyright Notices</a></li><li><a href="/web/20230305211917/https://www.youtube.com/t/community_guidelines">Community Guidelines</a></li></ul></div><div id="main-content" lang="en" dir="ltr"><h1 class="title">YouTube Data Processing Terms</h1><div> <h4>Effective as of November 24, 2020 (<a href="http://web.archive.org/web/20230305211917/https://www.youtube.com/t/terms_dataprocessing?archive=20200131">view previous version</a>)</h4><div class="banner"> We have updated our YouTube Data Processing Terms on November 24 2020 to address a recent ruling of the Court of Justice of the European Union on data transfers. </div> These YouTube Data Processing Terms (including the appendices, “Data Processing Terms”) will apply to the processing of Customer Personal Data. These terms serve as an addendum to the agreement between you (“Customer”) and Google regarding your use of the YouTube service (“Agreement”). Such Agreement may include the YouTube Terms of Service or a content license agreement, as applicable to Customer. Please take the time to read these Data Processing Terms carefully. <h3>1. Introduction</h3> These Data Processing Terms reflect the parties’ agreement on the terms governing the processing and security of Customer Personal Data in connection with the European Data Protection Legislation. <h3>2. Definitions and Interpretation</h3> 2.1 In these Data Processing Terms: “Affiliate,” if not already defined in the Agreement, means an entity that directly or indirectly controls, is controlled by, or is under common control with, a party. “Customer Personal Data” means audio and audiovisual content that is uploaded by Customer to YouTube under the terms of the Agreement and processed by Google on behalf of Customer in Google’s provision of the Processor Services. “Data Incident” 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. “Data Subject Tool” means a tool (if any) made available by Google 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). “EEA” means the European Economic Area. “EU GDPR” 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. “European Data Protection Legislation” means, as applicable: (a) the GDPR; (b) the Federal Data Protection Act of 19 June 1992 (Switzerland); (c) the Brazilian Data Protection General Law (Law No. 13709/2018); and/or (d) any other applicable data protection laws or regulations modeled on the General Data Protection Regulation. “European or National Laws” means, as applicable: (a) EU or EU Member State law (if the EU GDPR applies to the processing of Customer Personal Data); and/or (b) the law of the UK or a part of the UK (if the UK GDPR applies to the processing of Customer Personal Data). “GDPR” means, as applicable: (a) the EU GDPR; and/or (b) the UK GDPR. “Google” means the Google Entity that is party to your Agreement. “Google Affiliate Subprocessors” has the meaning given in Section 11.1 (Consent to Subprocessor Engagement). “Google Entity” means Google LLC (formerly known as Google Inc.), Google Ireland Limited, YouTube, LLC or any other Affiliate of Google LLC. “ISO 27001 Certification” means ISO/IEC 27001:2013 certification or a comparable certification for the Processor Services. “Notification Email Address” means the email address (if any) 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. “Processor Services” means the processing of Customer Personal Data in accordance with these Data Processing Terms. “Security Documentation” means the certificate issued for the ISO 27001 Certification, if any, and any other security certifications or documentation that Google may make available in respect of the Processor Services. “Security Measures” has the meaning given in Section 7.1.1 (Google’s Security Measures). “Standard Contractual Clauses” means the European Commission’s standard contractual clauses at<a href="http://web.archive.org/web/20230305211917/https://privacy.google.com/businesses/gdprprocessorterms/sccs/"> </a><a href="http://web.archive.org/web/20230305211917/https://privacy.google.com/businesses/gdprprocessorterms/sccs/">https://privacy.google.com/businesses/gdprprocessorterms/sccs/</a>, which are standard data protection terms for the transfer of personal data to processors established in third countries that do not ensure an adequate level of data protection, as described in Article 46 of the EU GDPR. “Subprocessors” 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. “Supervisory Authority” means, as applicable: (a) a “supervisory authority” as defined in the EU GDPR; and/or (b) the “Commissioner” as defined in the UK GDPR. “Third Party Subprocessors” has the meaning given in Section 11.1 (Consent to Subprocessor Engagement). “UK GDPR” means the EU GDPR as amended and incorporated into UK law under the UK European Union (Withdrawal) Act 2018, if in force 2.2 The terms “controller”, “data subject”, “personal data”, “processing” and “processor” as used in these Data Processing Terms have the meanings given in the GDPR, and the terms “data importer” and “data exporter” have the meanings given in the Standard Contractual Clauses. 2.3 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. 2.4 If these Data Processing Terms are translated into any other language, and there is a discrepancy between the English text and the translated text, the English text will govern. <h3>3. Duration of these Data Processing Terms</h3> The term (“Term”) of these Data Processing Terms, and Google’s provision of the Processor Services, will begin on May 25, 2018 (or the date of the Agreement if after May 25, 2018) (“Terms Effective Date”) and will continue until deletion of all Customer Personal Data by Google as described in these Data Processing Terms. <h3>4. Application of these Data Processing Terms</h3> 4.1 Application of European Data Protection Legislation. These Data Processing Terms will only apply to the extent that the European Data Protection Legislation applies to the processing of Customer Personal Data, including if: (a) the processing is in the context of the activities of an establishment of Customer in the EEA or the UK; and/or (b) Customer Personal Data is personal data relating to data subjects who are in the EEA or the UK and the processing relates to the offering to them of goods or services or the monitoring of their behaviour in the EEA or the UK. <h3>5. Processing of Data</h3> 5.1 Roles and Regulatory Compliance; Authorisation. 5.1.1 Processor and Controller Responsibilities. (a) These Data Processing Terms describe the subject matter and details of the processing of Customer Personal Data; (b) Google is a processor of Customer Personal Data under the Data Protection Legislation; (c) Customer is a controller or processor, as applicable, of Customer Personal Data under the Data Protection Legislation; and (d) each party will comply with the obligations applicable to it under the Data Protection Legislation with respect to the processing of Customer Personal Data. 5.1.2 Authorisation by Third Party Controller. If Customer is a processor, Customer warrants to Google that Customer’s instructions and actions with respect to Customer Personal Data, including its appointment of Google as another processor, have been authorised by the relevant controller. 5.2 Customer’s Instructions. Customer instructs Google to process Customer Personal Data only in accordance with applicable law and these Data Processing Terms: (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; and (c) as documented in the form of the Agreement, including these Data Processing Terms. 5.3 Google’s Compliance with Instructions. Google will comply with the instructions described in Section 5.2 (Customer’s Instructions) (including with regard to data transfers) unless European or National Laws to which Google is subject requires other processing of Customer Personal Data by Google, in which case Google will inform Customer (unless any such law prohibits Google from doing so on important grounds of public interest). <h3>6. Data Deletion</h3> 6.1 Deletion During Term. 6.1.1 Processor Services With Deletion Functionality. During the Term, if: (a) the functionality of the Processor Services includes the option for Customer to delete Customer Personal Data; (b) Customer uses the Processor Services to delete certain Customer Personal Data; and (c) the deleted Customer Personal Data cannot be recovered by Customer (for example, from the “trash”), then Google will delete such Customer Personal Data from its systems as soon as reasonably practicable, unless European or National Laws require storage. 6.1.2 Processor Services Without Deletion Functionality. 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 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 European or National Laws require storage. Google may charge a fee (based on Google’s reasonable costs) for any data deletion under this Section 6.1.2 (Processor Services Without Deletion Functionality). Google will provide Customer with further details of any applicable fee, and the basis of its calculation, in advance of any such data deletion. 6.2 Deletion on Agreement Expiry. On expiry or termination of the Agreement, Customer instructs Google to delete all Customer Personal Data (including existing copies) from Google’s systems in accordance with applicable law. Google will comply with this instruction as soon as reasonably practicable unless: (i) European or National Laws require storage; or (ii) the Agreement is superseded by a new agreement or terms between Customer and Google regarding Customer's use of the YouTube service and Customer confirms that the Customer Personal Data (including existing copies already uploaded to the YouTube Service) should continue to be processed in accordance with these Data Processing Terms. <h3>7. Data Security</h3> 7.1 Google’s Security Measures and Assistance. 7.1.1 Google’s Security Measures. 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 “Security Measures”). 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. 7.1.2 Security Compliance by Google Staff. Google will ensure that all persons authorised to process Customer Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality. 7.1.3 Google’s Security Assistance. 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 any obligations of Customer in respect of security of personal data and personal data breaches, including (if applicable) Customer’s obligations pursuant to Articles 32 to 34 (inclusive) of the GDPR, by: (a) implementing and maintaining the Security Measures in accordance with Section 7.1.1 (Google’s Security Measures); (b) complying with the terms of Section 7.2 (Data Incidents); and (c) providing Customer with the Security Documentation in accordance with Section 7.5.1 (Reviews of Security Documentation) and the information contained in these Data Processing Terms. 7.2 Data Incidents. 7.2.1 Incident Notification. If Google becomes aware of a Data Incident, Google will: (a) notify Customer of the Data Incident promptly and without undue delay; and (b) promptly take reasonable steps to minimise harm and secure Customer Personal Data. 7.2.2 Details of Data Incident. Notifications made under Section 7.2.1 (Incident Notification) will describe, to the extent possible, details of the Data Incident, including steps taken to mitigate the potential risks and steps Google recommends Customer take to address the Data Incident. 7.2.3 Delivery of Notification. Google will deliver its notification of any Data Incident to the Notification Email Address or by other direct communication (for example, by phone call or an in-person meeting). Customer will take all reasonable steps to provide the Notification Email Address and ensure that the Notification Email Address is current and valid. 7.2.4 Third Party Notifications. 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. 7.2.5 No Acknowledgement of Fault by Google. 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. 7.3 Customer’s Security Responsibilities and Assessment. 7.3.1 Customer’s Security Responsibilities. Without prejudice to Google’s obligations under Sections 7.1 (Google’s Security Measures and Assistance) and 7.2 (Data Incidents): (a) Customer is responsible for its use of the Processor Services, including: (i) making appropriate use of the Processor Services to ensure a level of security appropriate to the risk in respect of Customer Personal Data; and (ii) securing the account authentication credentials, systems, and devices Customer uses to access the Processor Services; and (b) Google has no obligation to protect Customer Personal Data that Customer elects to store or transfer outside of Google’s and its Subprocessors’ systems. 7.3.2 Customer’s Security Assessment. Customer acknowledges and agrees that (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) 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. 7.4 Security Certification. To evaluate and help ensure the continued effectiveness of the Security Measures, from time to time, Google may obtain the ISO 27001 Certification. 7.5 Reviews and Audits of Compliance. 7.5.1 Reviews of Security Documentation. To demonstrate compliance by Google with its obligations under these Data Processing Terms, Google will make the Security Documentation available for review by Customer. 7.5.2 Customer’s Audit Rights. (a) 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 Section 7.5.3 (Additional Business Terms for Audits). Google will contribute to such audits as described in Section 7.4 (Security Certification) and this Section 7.5 (Reviews and Audits of Compliance). (b) If the Standard Contractual Clauses apply under Section 10.2 (Transfers of Data), Google will allow Customer or a third party auditor appointed by Customer to conduct audits as described in the Standard Contractual Clauses in accordance with Section 7.5.3 (Additional Business Terms for Audits). (c) Customer may also conduct an audit to 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), if such certification is available at the time of Customer’s request. 7.5.3 Additional Business Terms for Audits. (a) Customer will send any request for an audit under Section 7.5.2(a) or 7.5.2(b) to Google as described in Section 12.1 (Contacting Google). (b) Following receipt by Google of a request under Section 7.5.3(a), 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 Section 7.5.2(a) or 7.5.2(b). (c) Google may charge a fee (based on Google’s reasonable costs) for any audit under Section 7.5.2(a) or 7.5.2(b). 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. (d) Google may object to any third party auditor appointed by Customer to conduct any audit under Section 7.5.2(a) or 7.5.2(b) 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. (e) 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 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 Data Protection Legislation. 7.5.4 No Modification of Standard Contractual Clauses. If the Standard Contractual Clauses apply under Section 10.2 (Transfers of Data), nothing in this Section 7.5 (Reviews and Audits of Compliance) varies or modifies any rights or obligations of Customer or a Google Entity under the Standard Contractual Clauses. <h3>8. Impact Assessments and Consultations</h3> Google will (taking into account the nature of the processing and the information available to Google) assist Customer in ensuring compliance with any obligations of Customer in respect of data protection impact assessments and prior consultation, including (if applicable) Customer’s obligations pursuant to Articles 35 and 36 of the GDPR, by: (a) providing the Security Documentation in accordance with Section 7.5.1 (Reviews of Security Documentation); (b) providing the information contained in these Data Processing Terms; and (c) 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). <h3>9. Data Subject Rights</h3> 9.1 Responses to Data Subject Requests. If Google receives a request from a data subject in relation to Customer Personal Data, Google will: (a) if the request is made via a Data Subject Tool, respond directly to the data subject’s request in accordance with the standard functionality of that Data Subject Tool; or (b) if the request is not made via a Data Subject Tool, advise the data subject to submit his/her request to Customer, and Customer will be responsible for responding to such request. 9.2 Google’s Data Subject Request Assistance. Google will (taking into account the nature of the processing of Customer Personal Data and, if applicable, Article 11 of the GDPR) assist Customer in fulfilling any obligation of Customer to respond to requests by data subjects, including (if applicable) Customer’s obligation to respond to requests for exercising the data subject’s rights laid down in Chapter III of the GDPR, by: (a) providing the functionality of the Processor Services; (b) complying with the commitments set out in Section 9.1 (Responses to Data Subject Requests); and (c) if applicable to the Processor Services, making available Data Subject Tools. <h3>10. Data Transfers</h3> 10.1 Data Storage and Processing Facilities. Google may, subject to Section 10.2 (Transfers of Data), store and process Customer Personal Data in the United States of America and any other country in which Google or any of its Subprocessors maintains facilities. 10.2 Transfers of Data. If the storage and/or processing of Customer Personal Data involves transfers of Customer Personal Data from the EEA, Switzerland, or the UK to any third country that is not subject to an adequacy decision under the European Data Protection Legislation: (a) Customer (as data exporter) will be deemed to have entered into the Standard Contractual Clauses with Google LLC (as data importer); (b) the transfers will be subject to the Standard Contractual Clauses; and (c) Google will ensure that Google LLC complies with its obligations under such Standard Contractual Clauses regarding such transfers. 10.3 Data Centre Information. Information about the locations of Google data centres is available at: <a href="http://web.archive.org/web/20230305211917/https://www.google.com/about/datacenters/locations/">www.google.com/about/datacenters/inside/locations/index.html</a>. <h3>11. Subprocessors</h3> 11.1 Consent to Subprocessor Engagement. Customer specifically authorises the engagement of Google’s Affiliates as Subprocessors (“Google Affiliate Subprocessors”). In addition, Customer generally authorises the engagement of any other third parties as Subprocessors (“Third Party Subprocessors”). If the Standard Contractual Clauses apply under Section 10.2 (Transfers of Data), the above authorisations constitute Customer’s prior written consent to the subcontracting by Google LLC of the processing of Customer Personal Data. 11.2 Information about Subprocessors. Information about Subprocessors is available at privacy.google.com/businesses/subprocessors. 11.3 Requirements for Subprocessor Engagement. When engaging any Subprocessor, Google will: (a) ensure via a written contract that: (i) 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, if applicable under Section 10.2 (Transfers of Data), the Standard Contractual Clauses; and (ii) if the GDPR applies to the processing of Customer Personal Data, the data protection obligations set out in Article 28(3) of the GDPR are imposed on the Subprocessor; and (b) remain fully liable for all obligations subcontracted to, and all acts and omissions of, the Subprocessor. <h3>12. Contacting Google; Processing Records</h3> 12.1 Contacting Google. Customer may contact Google in relation to the exercise of its rights under these Data Processing Terms via the methods described at <a href="http://web.archive.org/web/20230305211917/https://support.google.com/youtube/answer/2801895?ref_topic=2803240">https://support.google.com/youtube/answer/2801895</a> or via such other means as may be provided by Google from time to time. 12.2 Google’s Processing Records. Customer acknowledges that Google is required under the GDPR to: (a) collect and maintain records of certain information, including 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 (b) 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. <h3>13. Liability</h3> 13.1 Liability Cap. Notwithstanding anything else in the Agreement, the total aggregate 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 (for clarity, any exclusion of confidentiality or indemnification claims from the Agreement’s limitation of liability will not apply to claims under the Agreement relating to the European Data Protection Legislation). Nothing in this Section 13 (Liability) will exclude or limit either party’s liability for: (a) death or personal injury resulting from its negligence or the negligence of its employees or agents; (b) fraud or fraudulent misrepresentation; or (c) matters for which liability cannot be excluded or limited under applicable law. 13.2 Liability if the Standard Contractual Clauses Apply. If the Standard Contractual Clauses apply under Section 10.2 (Transfers of Data), then the total combined liability of each party and its Affiliates towards the other party and its Affiliates under or in connection with the Agreement and the Standard Contractual Clauses combined will be subject to Section 13.1 (Liability Cap). <h3>14. Third Party Beneficiaries</h3> If a party’s Affiliate is a party to the Standard Contractual Clauses that apply under Section 10.2 (Transfers of Data), then that Affiliate will be a third party beneficiary of Sections 6.2 (Deletion on Agreement Expiry), 7.5 (Reviews and Audits of Compliance), 9.1 (Responses to Data Subject Requests), 10.2 (Transfers of Data), 11.1 (Consent to Subprocessor Engagement), and 13.2 (Liability if the Standard Contractual Clauses Apply). To the extent this Section 14 (Third Party Beneficiaries) conflicts or is inconsistent with any other clause in the Agreement, this Section 14 (Third Party Beneficiaries) will apply. <h3>15. Effect of these Data Processing Terms</h3> If there is any conflict or inconsistency between the Standard Contractual Clauses, the terms of these Data Processing Terms, and the remainder of the Agreement, then the following order of precedence will apply: (a) the Standard Contractual Clauses; (b) the remainder of these Data Processing Terms; and (c) the remainder of the Agreement. Subject to the amendments in these Data Processing Terms, the Agreement remains in full force and effect. <h3>16. Changes to these Data Processing Terms</h3> 16.1 Changes to Processor Services. Google may only change the list of potential Processor Services: (a) to reflect a change to the name of a service; (b) to add a new service; or (c) to remove a service where either: (i) all contracts for the provision of that service are terminated; or (ii) Google has Customer’s consent. 16.2 Changes to Data Processing Terms. Google may change these Data Processing Terms if the change: (a) is expressly permitted by these Data Processing Terms, including as described in Section 16.1 (Changes to Processor Services); (b) reflects a change in the name or form of a legal entity; (c) is required to comply with applicable law, applicable regulation, a court order or guidance issued by a governmental regulator or agency; or (d) 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 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. 16.3 Changes to Standard Contractual Clauses. Google may only change the Standard Contractual Clauses in accordance with Sections 16.2(b) - 16.2(d) (Changes to Data Processing Terms) or to incorporate any new version of the Standard Contractual Clauses that may be adopted under the European Data Protection Legislation, in each case in a manner that does not affect the validity of the Standard Contractual Clauses under the European Data Protection Legislation. <h2>Appendix 1: Subject Matter and Details of the Data Processing</h2> Subject Matter Google’s provision of the Processor Services and any related technical support to Customer. Duration of the Processing The Term plus the period from expiry of the Term until deletion of all Customer Personal Data by Google in accordance with these Data Processing Terms. Nature and Purpose of the Processing Google will process (including, as applicable to the Processor Services and the instructions described in Section 5.2 (Customer’s 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. Types of Personal Data The types of personal data that constitute Customer Personal Data are audio and audiovisual content that are uploaded by Customer to YouTube under the terms of the Agreement and processed by Google on behalf of Customer in Google’s provision of the Processor Services. <h2> Appendix 2: Security Measures</h2> 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. <h3>1. Data Centre & Network Security</h3> (a) Data Centres. Infrastructure. Google maintains geographically distributed data centres. Google stores all production data in physically secure data centres. Redundancy. 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. Power. 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 diesel generator systems take over. The diesel 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. Server Operating Systems. 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. Businesses Continuity. 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. (b) Networks & Transmission. Data Transmission. Data centres are typically connected via high-speed private links to provide secure and fast data transfer between data centres. This is designed to prevent data from being read, copied, altered or removed without authorisation during electronic transfer or transport or while being recorded onto data storage media. Google transfers data via Internet standard protocols. External Attack Surface. 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. Intrusion Detection. Intrusion detection is intended to provide insight into ongoing attack activities and provide adequate information to respond to incidents. Google’s intrusion detection involves: 1. Tightly controlling the size and make-up of Google’s attack surface through preventative measures; 2. Employing intelligent detection controls at data entry points; and 3. Employing technologies that automatically remedy certain dangerous situations. Incident Response. Google monitors a variety of communication channels for security incidents, and Google’s security personnel will react promptly to known incidents. Encryption Technologies. Google makes HTTPS encryption (also referred to as SSL or 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. <h3>2. Access and Site Controls</h3> (a) Site Controls. On-site Data Centre Security Operation. 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 operation personnel monitor Closed Circuit TV (“CCTV”) cameras and all alarm systems. On-site security operation personnel perform internal and external patrols of the data centre regularly. Data Centre Access Procedures. 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 the requestor’s manager and the data centre director. All other entrants requiring temporary data centre access must: (i) obtain approval in advance from the data centre managers 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. On-site Data Centre Security Devices. 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. (b) Access Control. Infrastructure Security Personnel. 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. Access Control and Privilege Management. 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. Internal Data Access Processes and Policies – Access Policy. 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 SSH 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. <h3>3. Data</h3> (a) Data Storage, Isolation & Authentication. 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. (b) Decommissioned Disks and Disk Destruction Guidelines. Certain disks containing data may experience performance issues, errors or hardware failure that lead them to be decommissioned (“Decommissioned Disk”). Every Decommissioned Disk is subject to a series of data destruction processes (the “Data Destruction Guidelines”) 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. <h3>4. Personnel Security</h3> 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 backgrounds checks to the extent legally permissible and in accordance with applicable local labor law and statutory regulations. 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. <h3>5. Subprocessor Security</h3> 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 then, subject always to the requirements set out in Section 11.3 (Requirements for Subprocessor Engagement), the Subprocessor is required to enter into appropriate security, confidentiality and privacy contract terms. </div> </div></div></body></html>