This Data Protection Addendum (“Addendum”) forms part of the agreement(s) between Customer and OneSignal covering Customer’s use of the Services (as defined below) (“Agreement”) and governs the use of Customer Personal Data (as defined below), by OneSignal.
Customer shall subscribe to updates to OneSignal’s list of subprocessors via the following link - https://onesignal.com/list-of-subprocessors (the “Subprocessor List”)
The following “Schedules” are incorporated into this DPA:
1. Definitions.
“Agreement” means the Agreement between Customer and Provider to which this DPA is appended.
“Audit” and “Audit Parameters” are defined in Section 9.3 below.
“Audit Report” is defined in Section 9.2 below.
“Controller” means the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of Processing of Personal Data.
“Customer Instructions” is defined in Section 3.1 below.
“Customer Personal Data” means Personal Data that Customer distributes or makes available via the Services.
“Data Protection Laws” means all laws and regulations applicable to the Processing of Customer Personal Data under the Agreement, including, as applicable: (i) the California Consumer Privacy Act, as amended by the California Privacy Rights Act, and any binding regulations promulgated thereunder (“CCPA”), (ii) the General Data Protection Regulation (Regulation (EU) 2016/679) (“EU GDPR” or “GDPR”), (iii) the Swiss Federal Act on Data Protection (“FADP”), (iv) the EU GDPR as it forms part of the law of England and Wales by virtue of section 3 of the European Union (Withdrawal) Act 2018 (the “UK GDPR”) and (v) the UK Data Protection Act 2018; in each case, as updated, amended or replaced from time to time.
“Data Subject” means the identified or identifiable natural person to whom Customer Personal Data relates.
“EEA” means European Economic Area.
“Personal Data” means any information related to an identified or identifiable natural person (e.g. first and last name) or codes including a unique device identifier (e.g. IP address, advertising identifier) that alone or in combination with other data elements (e.g. commercial information, date of birth, or employment information) could enable an individual or unique device to be identified, directly or indirectly, or as otherwise defined in applicable data protection and security laws.
“Processing” and inflections thereof refer to any operation or set of operations that is performed on Personal Data or on sets of Personal Data, whether or not by automated means, such as collection, recording, organization, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction.
“Processor” means a natural or legal person, public authority, agency or other body which Processes Personal Data on behalf of the Controller.
“Restricted Transfer” means: (i) where EU GDPR applies, a transfer of Customer Personal Data from the EEA to a country outside the EEA that is not subject to an adequacy determination, (ii) where UK GDPR applies, a transfer of Customer Personal Data from the United Kingdom to any other country that is not subject to an adequacy determination or (iii) where FADP applies, a transfer of Customer Personal Data from Switzerland to any other country that is not subject to an adequacy determination.
“Security Incident” means any breach of security that leads to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to, Customer Personal Data being Processed by Provider.
“Specified Notice Period” is 72 hours.
“Subprocessor” means any third party authorized by Provider to Process any Customer Personal Data.
2. Scope and Duration.
2.1. Roles of the Parties. This DPA applies to Provider as a Processor of Customer Personal Data and to Customer as a Controller or Processor of Customer Personal Data.
2.2. Scope of DPA. This DPA applies to Provider’s Processing of Customer Personal Data under the Agreement to the extent such Processing is subject to Data Protection Laws. This DPA is governed by the governing law of the Agreement unless otherwise required by Data Protection Laws.
2.3. Duration of DPA. This DPA commences on the Effective Date of the Agreement or other date as agreed by the parties, and terminates upon expiration or termination of the Agreement (or, if later, the date on which Provider has ceased all Processing of Customer Personal Data).
2.4. Order of Precedence. In the event of any conflict or inconsistency among the following documents, the order of precedence will be: (1) any Standard Contractual Clauses or other measures to which the parties have agreed in Schedule 3 (Cross-Border Transfer Mechanisms) or Schedule 4 (Region-Specific Terms), (2) this DPA and (3) the Agreement. To the fullest extent permitted by Data Protection Laws, any claims brought in connection with this DPA (including its Schedules) will be subject to the terms and conditions, including, but not limited to, the exclusions and limitations, set forth in the Agreement.
3. Processing of Personal Data.
3.1. Customer Instructions.
(a) Provider will Process Customer Personal Data as a Processor only: (i) in accordance with Customer Instructions or (ii) to comply with Provider’s obligations under applicable laws, subject to any notice requirements under Data Protection Laws.
(b) “Customer Instructions” means: (i) Processing to provide the Services and perform Provider’s obligations in the Agreement (including this DPA) and (ii) other reasonable documented instructions of Customer consistent with the terms of the Agreement.
(c) Details regarding the Processing of Customer Personal Data by Provider are set forth in Schedule 1 (Subject Matter and Details of Processing).
(d) Provider will notify Customer if it receives an instruction that Provider reasonably determines infringes Data Protection Laws (but Provider has no obligation to actively monitor Customer’s compliance with Data Protection Laws).
3.2. Confidentiality.
(a) Provider will protect Customer Personal Data in accordance with its confidentiality obligations as set forth in the Agreement.
(b) Provider will ensure personnel who Process Customer Personal Data either enter into written confidentiality agreements or are subject to statutory obligations of confidentiality.
3.3. Compliance with Laws.
(a) Provider and Customer will each comply with Data Protection Laws in their respective Processing of Customer Personal Data.
(b) Customer will comply with Data Protection Laws in its issuing of Customer Instructions to Provider. Customer will ensure that it has established all necessary lawful bases under Data Protection Laws to enable Provider to lawfully Process Customer Personal Data for the purposes contemplated by the Agreement (including this DPA), including, as applicable, by obtaining all necessary consents from, and giving all necessary notices to, Data Subjects.
3.4. Changes to Laws. The parties will work together in good faith to negotiate an amendment to this DPA as either party reasonably considers necessary to address the requirements of Data Protection Laws from time to time.
4. Subprocessors.
4.1. Use of Subprocessors.
(a) Customer generally authorizes Provider to engage Subprocessors to Process Customer Personal Data. Customer further agrees that Provider may engage its Affiliates as Subprocessors.
(b) Provider will: (i) enter into a written agreement with each Subprocessor imposing data Processing and protection obligations substantially the same as those set out in this DPA and (ii) remain liable for compliance with the obligations of this DPA and for any acts or omissions of a Subprocessor that cause Provider to breach any of its obligations under this DPA.
4.2. Subprocessor List. Provider will maintain an up-to-date list of its Subprocessors, including their functions and locations, as specified in the Subprocessor List.
4.3. Notice of New Subprocessors. Provider may update the Subprocessor List from time to time. At least 30 days before any new Subprocessor Processes any Customer Personal Data, Provider will add such Subprocessor to the Subprocessor List and notify Customer through email or subscription list.
4.4. Objection to New Subprocessors.
(a) If, within 30 days after notice of a new Subprocessor, Customer notifies Provider in writing that Customer objects to Provider’s appointment of such new Subprocessor based on reasonable data protection concerns, the parties will discuss such concerns in good faith.
(b) If the parties are unable to reach a mutually agreeable resolution to Customer’s objection to a new Subprocessor, Customer, as its sole and exclusive remedy, may terminate the Order for the affected Services for convenience and Provider will refund any prepaid, unused fees for the terminated portion of the Subscription Term.
5. Security.
5.1. Security Measures. Provider will implement and maintain reasonable and appropriate technical and organizational measures, procedures and practices, as appropriate to the nature of the Customer Personal Data, that are designed to protect the security, confidentiality, integrity and availability of Customer Personal Data and protect against Security Incidents, in accordance with Provider’s Security Measures referenced in the Agreement and as further described in Schedule 2 (Technical and Organizational Measures). Provider will regularly monitor its compliance with its Security Measures and Schedule 2 (Technical and Organizational Measures).
5.2. Incident Notice and Response.
(a) Provider will implement and follow procedures to detect and respond to Security Incidents.
(b) Provider will: (i) notify Customer without undue delay and, in any event, not later than the Specified Notice Period, after becoming aware of a Security Incident affecting Customer and (ii) make reasonable efforts to identify the cause of the Security Incident, mitigate the effects and remediate the cause to the extent within Provider’s reasonable control.
(c) Upon Customer’s request and taking into account the nature of the applicable Processing, Provider will assist Customer by providing, when available, information reasonably necessary for Customer to meet its Security Incident notification obligations under Data Protection Laws.
(d) Customer acknowledges that Provider’s notification of a Security Incident is not an acknowledgement by Provider of its fault or liability.
(e) Security Incidents do not include unsuccessful attempts or activities that do not compromise the security of Customer Personal Data, including unsuccessful login attempts, pings, port scans, denial of service attacks or other network attacks on firewalls or networked systems.
5.3. Customer Responsibilities.
(a) Customer is responsible for reviewing the information made available by Provider relating to data security and making an independent determination as to whether the Services meets Customer’s requirements and legal obligations under Data Protection Laws.
(b) Customer is solely responsible for complying with Security Incident notification laws applicable to Customer and fulfilling any obligations to give notices to government authorities, affected individuals or others relating to any Security Incidents.
6. Data Protection Impact Assessment. Upon Customer’s request and taking into account the nature of the applicable Processing, to the extent such information is available to Provider, Provider will assist Customer in fulfilling Customer’s obligations under Data Protection Laws to carry out a data protection impact or similar risk assessment related to Customer’s use of the Services, including, if required by Data Protection Laws, by assisting Customer in consultations with relevant government authorities.
7. Data Subject Requests.
7.1. Assisting Customer. Upon Customer’s request and taking into account the nature of the applicable Processing, Provider will assist Customer by appropriate technical and organizational measures, insofar as possible, in complying with Customer’s obligations under Data Protection Laws to respond to requests from individuals to exercise their rights under Data Protection Laws, provided that Customer cannot reasonably fulfill such requests independently (including through use of the Services).
7.2. Data Subject Requests. If Provider receives a request from a Data Subject in relation to the Data Subject’s Customer Personal Data, Provider will notify Customer and advise the Data Subject to submit the request to Customer (but not otherwise communicate with the Data Subject regarding the request except as may be required by Data Protection Laws), and Customer will be responsible for responding to any such request.
8. Data Return or Deletion.
8.1. During Subscription Term. During the Subscription Term, Customer may, through the features of the Services or such other means specified in the Agreement, access, return to itself or delete Customer Personal Data.
8.2. Post Termination.
(a) Following termination or expiration of the Agreement, Provider will, in accordance with its obligations under the Agreement, delete all Customer Personal Data from Provider’s systems.
(b) Deletion will be in accordance with industry-standard secure deletion practices. Provider will issue a certificate of deletion upon Customer’s request.
(c) Notwithstanding the foregoing, Provider may retain Customer Personal Data: (i) as required by Data Protection Laws or (ii) in accordance with its standard backup or record retention policies, provided that, in either case, Provider will (x) maintain the confidentiality of, and otherwise comply with the applicable provisions of this DPA with respect to, retained Customer Personal Data and (y) not further Process retained Customer Personal Data except for such purpose(s) and duration specified in such applicable Data Protection Laws.
9. Audits.
9.1. Provider Records Generally. Provider will keep records of its Processing in compliance with Data Protection Laws and, upon Customer’s request, make available to Customer any records reasonably necessary to demonstrate compliance with Provider’s obligations under this DPA and Data Protection Laws.
9.2. Third-Party Compliance Program.
(a) Provider will describe its third-party audit and certification programs (if any) and make summary copies of its audit reports (each, an “Audit Report”) available to Customer upon Customer’s written request at reasonable intervals (subject to confidentiality obligations).
(b) Customer may share a copy of Audit Reports with relevant government authorities as required upon their request.
(c) Customer agrees that any audit rights granted by Data Protection Laws will be satisfied by Audit Reports and the procedures of Section 9.3 (Customer Audit) below.
9.3. Customer Audit.
(a) Subject to the terms of this Section 9.3, Customer has the right, at Customer’s expense, to conduct an audit of reasonable scope and duration pursuant to a mutually agreed-upon audit plan with Provider that is consistent with the Audit Parameters (an “Audit”).
(b) Customer may exercise its Audit right: (i) to the extent Provider’s provision of an Audit Report does not provide sufficient information for Customer to verify Provider’s compliance with this DPA or the parties’ compliance with Data Protection Laws, (ii) as necessary for Customer to respond to a government authority audit or (iii) in connection with a Security Incident.
(c) Each Audit must conform to the following parameters (“Audit Parameters”): (i) be conducted by an independent third party that will enter into a confidentiality agreement with Provider, (ii) be limited in scope to matters reasonably required for Customer to assess Provider’s compliance with this DPA and the parties’ compliance with Data Protection Laws, (iii) occur at a mutually agreed date and time and only during Provider’s regular business hours, (iv) occur no more than once annually (unless required under Data Protection Laws or in connection with a Security Incident), (v) cover only facilities controlled by Provider, (vi) restrict findings to Customer Personal Data only and (vii) treat any results as confidential information to the fullest extent permitted by Data Protection Laws.
10. Cross-Border Transfers/Region-Specific Terms.
10.1. Cross-Border Data Transfers.
(a) Provider (and its Affiliates) may Process and transfer Customer Personal Data globally as necessary to provide the Services.
(b) If Provider engages in a Restricted Transfer, it will comply with Schedule 3 (Cross-Border Transfer Mechanisms).
10.2. Region-Specific Terms. To the extent that Provider Processes Customer Personal Data protected by Data Protection Laws in one of the regions listed in Schedule 4 (Region-Specific Terms), then the terms specified therein with respect to the applicable jurisdiction(s) will apply in addition to the terms of this DPA.
Schedule 1: Subject Matter and Details of Processing
Customer / ‘Data Exporter’ Details
Name: | The Customer set forth in Addendum or the Agreement |
Contact details for data protection: | The contact information set forth in the Addendum or the Agreement if no contact information is set forth in the Addendum. |
Main address: | The Customer’s address set forth in the Addendum or the Agreement if no address is set forth in the Addendum. |
Customer activities: | The activities related to the Services provided by the OneSignal pursuant to the Agreement. |
Role: | Controller |
Provider / ‘Data Importer’ Details
Name: | OneSignal, Inc. and its affiliates |
Contact details for data protection: | OneSignal Privacy Team - privacy@onesignal.com |
Main address: | 201 S. B St., Suite 200, San Mateo, CA 94401 |
Provider activities: | The Services provided by OneSignal to the Customer pursuant to the Agreement. |
Role: | Processor |
Details of Processing
Categories of Data Subjects: | Customer’s employees who use the Services End users of Customer’s mobile applications and/or websites |
Categories of Customer Personal Data: | The types and extent of Customer Personal Data Processed are determined and controlled by the Customer in its sole discretion; provided that no sensitive information or special categories of data will be shared with OneSignal. Customer Personal Data includes name, email, device ID, and IP address. |
Sensitive Categories of Data and additional associated restrictions/safeguards: | Not applicable |
Frequency of transfer: | Continuous |
Nature of the Processing: | OneSignal’s provision of the Services to Customer. |
Purpose of the Processing: | For OneSignal to provide the Services to Customer, including, specifically, delivering push notifications, in-app messaging, email messaging, and SMS messaging to the Customer’s intended recipients; and supporting and communicating with Customer’s employees who use the Services. |
Duration of Processing / retention period: | The duration of the Agreement and as set forth in Section 9.2 of the Addendum. |
Transfers to Subprocessors: | Our list of subprocessors is available here - https://onesignal.com/list-of-subprocessors |
Schedule 2: Technical and Organizational Measures
Description of the technical and organisational security measures implemented by the OneSignal (as the Processor / Data Importer) in accordance with Clauses 4(d) and 5(c) (or document/legislation attached):
OneSignal is responsible for implementing and maintaining technical and organisational measures to help secure Customer Personal Data against unauthorised data processing and accidental or unlawful loss, access or disclosure. It shall minimise security risks, including through risk assessment and regular testing.
OneSignal shall designate one or more employees to coordinate and be accountable for the information security programme. The information security programme will include the following measures:
Network Security: the computer network (servers, networking equipment, software systems etc. that are within OneSignal’s control) through which the Services are provided will be accessible to employees, contractors and any other person, all only to the extent necessary. OneSignal will maintain access controls and policies to manage what access is allowed (on a need to access basis) to the computer network, including the use of firewalls or functionally equivalent technology and authentication controls. OneSignal will maintain corrective action and incident response plans to respond to potential security threats.
Physical Security: physical components of the computer network are housed in facilities (the “Facilities”).
Access to the Facilities is managed via:
Implementation and maintenance of technical measures (e.g. to protect from the introduction of malicious computer programmes) to maintain the security of Customer Personal Data.
Implementation and maintenance of management and organisation measures, e.g. the appointment of an individual whose responsibility it is to look after such data; training staff as to their obligations; ensuring business continuity; ensuring periodic checks to ensure the organisation’s security measures remain appropriate and up to date; relevant policies to limit the personal use of equipment.
Separation of data: Customer data shall be kept separate from third party data to minimise the risk of unauthorised disclosure.
Authentication (SSO): OneSignal supports logging in to our service using email and password authentication. We also support single sign-on through Github or Google Apps (GSuite). Accounts are automatically protected from weak passwords, and 2-Factor Authentication is supported.
Physical Security: OneSignal’s servers are controlled by our cloud hosting provider Google Cloud and are housed in the Netherlands. This data center is highly secure, including ISO 27001, 27017, 27018 certifications and is SOC audited.
Network Security: OneSignal’s servers are connected to each other via a private local network. All internal servers have strict firewalls in place to prevent access from non-OneSignal hosts both within our datacenter and externally. Servers that do allow remote connections (our load-balancers, for instance) also have strict firewall rules and are closely monitored.
All connections to OneSignal’s public-facing services require TLS (HTTPS) encryption. Access to internal services is managed using Public-Private key authentication and is limited to key personnel.
Software Security: OneSignal regularly reviews our infrastructure to ensure that we are running up to date software across our infrastructure and that any CVEs or other software vulnerabilities are rapidly patched.
Modifications to OneSignal’s software or infrastructure undergo review by at least one senior engineer on OneSignal’s team to ensure best practices are followed and security vulnerabilities are not introduced. OneSignal also leverages thorough code testing and continuous integration to ensure that software security rules are working properly and regressions are not introduced.
Multi-Tenancy: OneSignal’s servers leverage multi-tenancy to maximize the efficiency of hardware utilization. To mitigate the possibility of data ever being leaked across clients, OneSignal employs multiple levels of security and safeguards:
First, OneSignal’s dashboard and API build upon a user permissions system that restricts access to data that users should not be able to reach. Next, OneSignal’s database leverages partitioning to separate client data across multiple tables on each database server. Finally, OneSignal has a strong code review process and automated testing in place to minimize the possibility of deploying code changes that could negatively affect the safeguards we have in place or overall system security.
For additional security, OneSignal recommends that Customers do not disclose Personal Data to our Services unless necessary.
Incident Response: OneSignal has detailed monitoring in place across all of its infrastructure. In the event of a service disruption or unusual activity, a senior member of OneSignal’s engineering and infrastructure team is immediately paged to investigate and resolve the problem.
OneSignal backs up Customer data at a frequency of at least once every 24 hours. In the event of a hardware failure that affects a database server, recovery can be performed in 3-4 hours. OneSignal also maintains detailed logs on system activity to identify infrastructure or security issues.
Certifications: OneSignal is SOC 2 certified. In addition, our data centers are also SOC or SSAE 16 certified. You can learn more about this from them here: https://cloud.google.com/security/compliance
Security Audits: OneSignal completes an annual comprehensive security assessment performed by Cherry Bekhaert. https://www.cbh.com/
Data Retention: API and automated message data is kept for 30 days and then deleted from our servers. Data stored on our dashboard is kept for the lifetime of the application.
Schedule 3: Cross-Border Transfer Mechanisms
- Definitions. Capitalized terms not defined in this Schedule are defined in the DPA.
“EU Standard Contractual Clauses” or “EU SCCs” means the Standard Contractual Clauses approved by the European Commission in decision 2021/914.
“UK International Data Transfer Agreement” means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the UK Information Commissioner, Version B1.0, in force as of March 21, 2022.
In addition:
“Designated EU Governing Law” means: | Irish |
“Designated EU Member State” means: | Ireland |
- EU Transfers. Where Customer Personal Data is protected by EU GDPR and is subject to a Restricted Transfer, the following applies:
- The EU SCCs are hereby incorporated by reference as follows:
Module 2 (Controller to Processor) applies where Customer is a Controller of Customer Personal Data and Provider is a Processor of Customer Personal Data;
Module 3 (Processor to Processor) applies where Customer is a Processor of Customer Personal Data (on behalf of a third-party Controller) and Provider is a Processor of Customer Personal Data;
Customer is the "data exporter" and Provider is the "data importer"; and
by entering into this DPA, each party is deemed to have signed the EU SCCs (including their Annexes) as of the Effective Date of the Agreement.
- For each Module, where applicable the following applies:
the optional docking clause in Clause 7 does not apply;
in Clause 9, Option 2 will apply, the minimum time period for prior notice of Subprocessor changes shall be as set out in Section 4.3 of this DPA, and Provider shall fulfill its notification obligations by notifying Customer of any Subprocessor changes in accordance with Section 4.3 of this DPA;
in Clause 11, the optional language does not apply;
in Clause 13, all square brackets are removed with the text remaining;
in Clause 17, Option 1 will apply, and the EU SCCs will be governed by Designated EU Governing Law;
in Clause 18(b), disputes will be resolved before the courts of the Designated EU Member State;
Schedule 1 (Subject Matter and Details of Processing) to this DPA contains the information required in Annex 1 of the EU SCCs; and
Schedule 2 (Technical and Organizational Measures) to this DPA contains the information required in Annex 2 of the EU SCCs.
Where context permits and requires, any reference in this DPA to the EU SCCs shall be read as a reference to the EU SCCs as modified in the manner set forth in this Section 2.
- The EU SCCs are hereby incorporated by reference as follows:
- Swiss Transfers. Where Customer Personal Data is protected by the FADP and is subject to a Restricted Transfer, the following applies:
- The EU SCCs apply as set forth in Section 2 (EU Transfers) of this Schedule 3 with the following modifications:
in Clause 13, the competent supervisory authority shall be the Swiss Federal Data Protection and Information Commissioner;
in Clause 17 (Option 1), the EU SCCs will be governed by the laws of Switzerland;
in Clause 18(b), disputes will be resolved before the courts of Switzerland;
the term Member State must not be interpreted in such a way as to exclude Data Subjects in Switzerland from enforcing their rights in their place of habitual residence in accordance with Clause 18(c); and
all references to the EU GDPR in this DPA are also deemed to refer to the FADP.
- The EU SCCs apply as set forth in Section 2 (EU Transfers) of this Schedule 3 with the following modifications:
- UK Transfers. Where Customer Personal Data is protected by the UK GDPR and is subject to a Restricted Transfer, the following applies:
- The EU SCCs apply as set forth in Section 2 (EU Transfers) of this Schedule 3 with the following modifications:
each party shall be deemed to have signed the “UK Addendum to the EU Standard Contractual Clauses” (“UK Addendum”) issued by the Information Commissioner’s Office under section 119 (A) of the Data Protection Act 2018;
the EU SCCs shall be deemed amended as specified by the UK Addendum in respect of the transfer of Customer Personal Data;
in Table 1 of the UK Addendum, the parties’ key contact information is located in Schedule 1 (Subject Matter and Details of Processing) to this DPA;
in Table 2 of the UK Addendum, information about the version of the EU SCCs, modules and selected clauses which this UK Addendum is appended to are located above in this Schedule 3;
in Table 3 of the UK Addendum:
- The EU SCCs apply as set forth in Section 2 (EU Transfers) of this Schedule 3 with the following modifications:
the list of parties is located in Schedule 1 (Subject Matter and Details of Processing) to this DPA;
the description of transfer is located in Schedule 1 (Subject Matter and Details of Processing) to this DPA;
Annex II is located in Schedule 2 (Technical and Organizational Measures) to this DPA; and
the list of Subprocessors is located in Schedule 1 (Subject Matter and Details of Processing) to this DPA.
in Table 4 of the UK Addendum, both the Importer and the Exporter may end the UK Addendum in accordance with its terms (and the respective box for each is deemed checked); and
in Part 2: Part 2 - Mandatory Clauses of the Approved Addendum, being the template Addendum B.1.0 issued by the ICO and laid before Parliament in accordance with section 119 (A) of the Data Protection Act 2018 on 2 February 2022, as it is revised under section 18 of those Mandatory Clauses.
5. Data Privacy Framework. For clarity, a transfer of Customer Personal Data from the EU, UK or Switzerland to Provider in the United States subject to the EU-U.S. Data Privacy Framework, the UK Extension to the EU-U.S. Data Privacy Framework, and/or the Swiss-U.S. Data Privacy Framework, as applicable (collectively, the “DPF”), shall not constitute a Restricted Transfer so long as Provider maintains an active certification to the DPF and certification to the DPF remains a legal basis for transfer of Personal Data to the United States under the GDPR, UK GDPR or FADP, as applicable.
Schedule 4: Region-Specific Terms
CALIFORNIA
- Definitions. CCPA and other capitalized terms not defined in this Schedule are defined in the DPA.
“business purpose”, “commercial purpose”, “personal information”, “sell”, “service provider” and “share” have the meanings given in the CCPA.
The definition of “Data Subject” includes “consumer” as defined under the CCPA.
The definition of “Controller” includes “business” as defined under the CCPA.
The definition of “Processor” includes “service provider” as defined under the CCPA.
- Obligations.
Customer is providing the Customer Personal Data to Provider under the Agreement for the limited and specific business purposes of providing the Services as described in Schedule 1 (Subject Matter and Details of Processing) to this DPA and otherwise performing under the Agreement.
Provider will comply with its applicable obligations under the CCPA and provide the same level of privacy protection to Customer Personal Data as is required by the CCPA.
Provider acknowledges that Customer has the right to: (i) take reasonable and appropriate steps under Section 9 (Audits) of this DPA to help to ensure that Provider’s use of Customer Personal Data is consistent with Customer’s obligations under the CCPA, (ii) receive from Provider notice and assistance under Section 7 (Data Subject Requests) of this DPA regarding consumers’ requests to exercise rights under the CCPA and (iii) upon notice, take reasonable and appropriate steps to stop and remediate unauthorized use of Customer Personal Data.
Provider will notify Customer promptly after it makes a determination that it can no longer meet its obligations under the CCPA.
Provider will not retain, use or disclose Customer Personal Data: (i) for any purpose, including a commercial purpose, other than the business purposes described in Section 2.1 of this Section A (California) of Schedule 4 or (ii) outside of the direct business relationship between Provider with Customer, except, in either case, where and to the extent permitted by the CCPA.
Provider will not sell or share Customer Personal Data received under the Agreement.
Provider will not combine Customer Personal Data with other personal information except to the extent a service provider is permitted to do so by the CCPA.