Last updated: 5 May, 2021
THIS DATA PROCESSING AGREEMENT (“DPA”) BETWEEN THE WALKME LEGAL ENTITY SIGNING AN ORDER FORM AND ITS AFFILIATES (COLLECTIVELY, “WALKME”, “COMPANY”, “WE”, “US” or “PROCESSOR”) AND THE INDIVIDUAL OR LEGAL ENTITY LICENSING THE SERVICES UNDER AN APPLICABLE ORDER FORM AND/OR WALKME’S MASTER SAAS AGREEMENT (“THE PRINCIPAL AGREEMENT”) (“CUSTOMER”, “YOU” OR “CONTROLLER”) AND TOGETHER WITH WALKME, THE “PARTIES” GOVERNS CUSTOMER’S ACCESS AND USE OF THE SERVICES.
BY ACCEPTING THIS DPA WHILE EXECUTING AN ORDER FORM AND/OR PRINCIPAL AGREEMENT THAT REFERENCES THIS DPA, CUSTOMER AGREES TO THE TERMS OF THIS DPA. IF YOU ARE ENTERING INTO THIS DPA ON BEHALF OF A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY AND ITS AFFILIATES TO THESE TERMS AND CONDITIONS, IN WHICH CASE THE TERMS “CUSTOMER” “YOU” OR “YOUR” SHALL REFER TO SUCH ENTITY AND ITS AFFILIATES. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF YOU DO NOT AGREE WITH THESE TERMS AND CONDITIONS, YOU MUST NOT ACCEPT THIS DPA AND SHALL NOT BE PERMITTED TO USE THE SERVICES.
BY ACCEPTING THE TERMS OF THIS DPA YOU REPRESENT AND WARRANT THAT ANY AND ALL INFORMATION PROVIDED TO US THROUGH THE SERVICE IS TRUE, ACCURATE AND COMPLETE. THE PROVISION OF FALSE OR FRAUDULENT INFORMATION IS STRICTLY PROHIBITED.
Background and undertakings:
- Controller and WalkMe have entered into the Principal Agreement under which WalkMe agreed to provide the Service pursuant to the Principal Agreement to the Controller and/or its Affiliates. In rendering the Service, WalkMe may from time to time be provided with, or have access to, information of the Controller which may qualify as Personal Data (as defined below).
- Subject to the terms of this DPA, WalkMe shall process Controller‘s data as a processor for the provision of the Service under the Principal Agreement and as further described in Annex 1.
- The Parties agree that the terms and conditions set out below, are an addendum to the Principal Agreement.
Now therefore, and in order to enable the Parties to comply with the Applicable Data Protection Legislation, the Parties have entered into this DPA as follows:
In this DPA the following terms have the following meanings, terms not otherwise defined herein shall have the same meaning as in the Principal Agreement:
“Affiliate/s” means any legal entity directly or indirectly controlling, controlled by or under common control with a party to the Principal Agreement, where “control” means the ownership of a majority share of the voting stock, equity, or voting interests of such entity.
“Applicable Data Protection Legislation” means all applicable laws and regulations, subject to the processing of Controller Data under this DPA, including without limitation (as applicable), (i) the General Data Protection Regulation (EU) 2016/679 (the “GDPR”); and (ii) the California Consumer Privacy Act of 2018, California Civil Code § 1798.100 et seq. (the “CCPA”);
“Controller Data” means any Personal Data processed by Processor on behalf of Controller, pursuant to or in connection with the Principal Agreement;
“Data Processing Agreement or DPA” means this DPA and all appendices attached hereto (as amended from time to time in accordance herewith);
“Personal Data” means any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or as otherwise referred to as “personal information”, “personally identifiable information” or similar term defined in the Applicable Data Protection Legislation; “Personal Data Breach” means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Controller Data processed, transmitted, stored or otherwise processed;
“Privacy Shield” means EU–US and/or Swiss-US Privacy Shield Framework, as administered by the U.S. Department of Commerce and approved by the European Commission pursuant to Decision C(2016)4176 of July 12, 2016 and detailed at https://www.privacyshield.gov/;
“Sub-processor/s” means a Processor engaged by WalkMe to carry out Processing in respect of Controller Data on behalf of the Controller.
The terms recognized by the GDPR, such as “Controller”, “Data Subject”, “Process”, “Processor” “Processing”, “Supervisory Authority” shall have the meanings set out therein even if such terms are not capitalized in this DPA.
- Processing of Controller Data
- 1.1 Each Party shall comply with the Applicable Data Protection Legislation at all times.
- 1.2 The Processor shall solely process the Controller Data to the extent necessary to provide the Service to the Controller.
- 1.3 The Processor agrees to only process Controller Data, in accordance with Controller’s documented instructions under this DPA, the Principal Agreement, the Order Form and in accordance with the Applicable Data Protection Legislation.
- 1.4 Notwithstanding the above, Controller hereby agrees and consents that Processor may Process Controller Data for the purpose of the ongoing operation of the Service, and the improvement and development, security and controls thereof.
- 1.5 Controller warrants and represents that it is, and will, at all relevant times remain duly and effectively authorized to give instructions. Controller shall have sole responsibility for the accuracy, quality and legality of Controller Data and how Controller acquired Controller Data. This DPA, the instructions, the Principal Agreement and the Order Form are Controller’s complete and final instructions to Processor for the Processing of Controller Data. Any additional or alternate instructions must be agreed upon separately in writing between authorized representatives of both Parties.
- 1.6 The Processor shall immediately notify Controller if the Processor cannot fulfil its obligations under this DPA or if the Processor is of the view that an instruction regarding the processing of Controller Data given by Controller would be in breach of Applicable Data Protection Legislation, unless the Processor is prohibited from notifying Controller under applicable Data Protection Legislation.
- 1.7 The Processor shall immediately notify Controller in writing if the Supervisory Authority requests access to Controller Data which the Processor processes on behalf of Controller.
- Security Measures
- 2.1 The Processor shall implement appropriate technical and organizational measures to protect and safeguard the Controller Data that is processed against Personal Data Breaches.
- 2.2 The measures shall at least reach a level of security equivalent of what is prescribed by Applicable Data Protection Legislation, relevant Supervisory Authorities’ applicable regulations and guidelines regarding security of Controller Data and what is otherwise appropriate to the risk of the processing of Controller Data against Personal Data Breaches.
- 2.3 Processor will maintain its security controls and audits, pursuant to, amongst others, ISO 27001, SOC 2 type II and ISO27799 Security management in health. Processor regularly monitors compliance with these safeguards. Processor will not materially decrease the overall security of the Service during the term of the Principal Agreement.
- Personnel; Confidentiality
- 3.1 Processor shall take reasonable steps to ensure the reliability of any employee, agent or contractor of the Processor who may have access to the Controller Data (“Personnel”), ensuring in each case that access is strictly limited to Personnel who need to know/access the relevant Controller Data, as strictly necessary for the purposes of the Principal Agreement, and to comply with the Applicable Data Protection Laws in the context of such Personnel’s duties to the Processor.
- 3.2 The Processor will impose appropriate contractual obligations upon its Personnel Processing Controller Data, including relevant obligations regarding confidentiality, data protection and data security. Personnel engaged are informed of the confidential nature of Controller Data and have received appropriate training with respect to their responsibilities.
- 3.3 The Processor has appointed a Data Protection Officer where such appointment is required by Applicable Data Protection legislation. The appointed person can be reached at email@example.com.
- 4.1 Controller authorizes Processor to appoint Sub-processors in accordance with this Section 4 for the purpose of providing the Services under the Principal Agreement.
- 4.2 Processor may continue to use those Sub-processors already engaged by Processor for the performance of certain Processing activities related to the Service, as detailed at https://www.walkme.com/walkme-sub-processors/ (“Sub-processor Portal“).
- 4.3 Processor shall give Controller at least 30 days’ notice of the appointment of any new Sub-processor or the replacement of an existing Sub-processor, including relevant details of the processing activities to be performed by such Sub-processor, by updating the Sub-processor Portal and providing Controller with a mechanism to obtain notice of that update.
- 4.3.1. If, within seven (7) days of receipt of such notice Controller notifies Processor in writing of any reasonable objection to the appointment with respect to the protection of Controller Data (“Controller Notice”), Processor shall postpone the appointment until reasonable steps have been taken to address Controller’s objection, which may be achieved by way of, amongst others: (i) offering an alternative to provide the Service without using such Sub-processor; (ii) Processor may cease to provide, or Controller may agree, not to use that specific part of the Service involving such Sub-processor; or (iii) take commercially reasonable supplementary measures in cooperation with Controller. Objection Notices should be sent to firstname.lastname@example.org.
- 4.3.2. Where such steps are not reasonably sufficient or available to relieve Controller’s objection and no alternative mutually agreeable solution could be reached within thirty (30) days upon receipt of the Controller Notice, to the extent that it relates to the Service which require the use of such Sub-processor, either Party may, by written notice to the other Party, terminate the applicable Order Form and/or Principal Agreement, for which Processor may – in its sole discretion – provide a refund of the pro-rata portion of any unused, prepaid Fees under the applicable Order Form (calculated from the balance period between termination date and the original term of the Order Form).
- 4.3.3 If the Controller does not provide a timely Controller Notice, the Sub-processors shall be deemed approved, and Processor may commence using such Sub-processor.
- 4.4 Where a Sub-processor fails to fulfil its data protection obligations, the Processor shall remain fully liable to Controller for the performance of the Sub-processor’s obligations.
- 4.5 With respect to each Sub-processor (i) Processor shall before the Sub-processor first Processes Controller Data, carry out adequate due diligence to ensure that the Sub-processor is capable of providing the level of protection for Controller Data required by the Principal Agreement and this DPA; and (ii) ensure that the arrangement between the Processor and the Sub-processor is governed by a written contract that substantially meets the same obligations under this DPA.
- 5.1 Some of Processor’s obligations may be performed by Processor’s Affiliates. Controller acknowledges that Processor’s Affiliates may Process Controller Data on Processor’s behalf to perform the Service under the Principal Agreement.
- 5.2 Processor will be liable for the acts and omissions of its Affiliates to the same extent Processor would be liable if performing the Service under the Principal Agreement.
- 5.3 Controller hereby consents to Processor’s use of Processor’s Affiliates in the performance of the Service in accordance with the terms of this Section 5.
- Personal Data Breach
- 6.1 In the event of a Personal Data Breach, the Processor shall notify Controller of a Personal Data Breach without undue delay and at the latest within 48 hours after becoming aware of the Personal Data Breach.
- 6.2 The Processor shall promptly after becoming aware of a Personal Data Breach:
- a. Commence an investigation of the Personal Data Breach in order to determine the scope, nature and the likely consequences of the Personal Data Breach;
- b. Take appropriate remedial measures in order to mitigate the possible adverse effects of the Personal Data Breach and minimize damage resulting therefrom.
- 6.3 Processor shall promptly provide Controller with such details relating to the Personal Data Breach as Controller reasonably requires complying with its obligations under the Applicable Data Protection Legislation.
- 6.4 The obligations in this Section 6 shall not apply to incidents that are caused by Controller or Controller’s End Users (as defined in the Principal Agreement).
- Rights of Data Subjects
- 7.1 Processor shall, to the extent legally permitted, promptly notify Controller if it receives a request from a Data Subject to exercise the Data Subject’s right of access, right to rectification, restriction of processing, erasure, data portability, or to object to processing, each a “Data Subject Request”. Processor will not respond to any such requests unless authorized to do so by Controller (unless required to do so under Applicable Data Protection Legislation or under the instructions of a competent authority).
- 7.2 The Processor shall provide commercial reasonable assistance to Controller by taking appropriate technical and organisational measures for the fulfilment of Controller’s obligation to respond to requests for exercising the Data Subjects’ rights as laid down by Applicable Data Protection Legislation. Unless prohibited under the Applicable Data Protection Laws, Controller will reimburse Processor with any costs and expenses related to Processor’s provision of such assistance.
- 8.1 Processor shall make available to Controller, upon prior written request, all relevant information necessary to reasonably demonstrate compliance with its obligations detailed in this DPA.
- 8.2 Processor shall allow for and contribute to audits, including inspections on its premises not more than once in each calendar year (except following a Personal Data Breach) and during regular business hours. The audit may be conducted by Controller or a third-party auditor mandated by Controller, provided that such third-party auditor shall be subject to sufficient confidentiality obligations. Controller shall give Processor reasonable notice prior to exercising its audit rights.
- 8.3 Each Party shall bear its own costs in relation to such audit. However, where Controller has mandated a third-party auditor to carry out the audit on its behalf, Controller shall bear the costs for such third-party auditor.
- Data Impact Assessments; Consultations
The Processor shall, upon Controller’s request, provide necessary information in order to allow Controller to fulfil its obligations to, where applicable, carry out data protection impact assessments (“DPIAs”) and prior consultations with the relevant Supervisory Authority under Applicable Data Protection Legislation in relation to the processing of Controller Data covered by this DPA.
Processor shall maintain complete, accurate and up-to-date documentation of its processing activities and measures taken hereunder, as required under the Applicable Data Protection Legislation, which Processor shall make available to Controller upon Controller’s written request.
In order to provide the Service, Processor and its Sub-processors may only transfer Controller Data concerning residents of the EEA to a Sub-processor or an Affiliate outside the EEA in accordance with a data transfer mechanism permitted by the Applicable Data Protection Legislation as further detailed below:
- 11.1 Processor and its Affiliates hereby affirm that they certified their compliance to the EU-US and Swiss-US Privacy Shield Framework (the “Privacy Shield”) as of the effective date of this DPA and shall remain committed to comply with the Privacy Shield principles with respect to transfer of Personal Data concerning residents of the EEA to a Sub-processor or an Affiliate in the United States, until Processor withdraws from the Privacy Shield.
- 11.2 Notwithstanding the above, the Processor and Controller shall execute the Standard Contractual Clauses set forth in Annex 2 hereto in the event that Controller Data is transferred to: (i) countries outside the EEA and (ii) that are not recognized by the EU Commission as providing adequate protection pursuant to Article 45 of the GDPR.
- Deletion; Return
Processor shall promptly, and in any event within 90 days of termination of the Principal Agreement or upon Controller’s request, delete or return all copies of Controller Data, except where such copies are required to be retained in accordance with the Applicable Data Protection Legislation and provided that Processor shall ensure the confidentiality of all such Controller Data. Upon prior written request of Controller, Processor shall provide written documentation that is has complied with its obligation herein.
- General Terms
- 13.1 The parties to this DPA hereby submit to the choice of jurisdiction stipulated in the Principal Agreement with respect to any disputes or claims howsoever arising under this DPA, including disputes regarding its existence, validity or termination or the consequences of its nullity.
- 13.2 Should any provision of this DPA be invalid or unenforceable, then the remainder of this DPA shall remain valid and in force. The invalid or unenforceable provision shall be either (i) amended as necessary to ensure its validity and enforceability, while preserving the parties’ intentions as closely as possible or, if this is not possible, (ii) construed in a manner as if the invalid or unenforceable part had never been contained therein.
- 13.3 Amendments and additions to this DPA shall be in writing and duly signed by the Parties to be valid.
Annex 1 – Details of Processing
This Annex 1 includes details of the Processing of Controller Data as required by Article 28(3) GDPR.
- Subject matter and duration of the Processing of Controller Data
The subject matter and duration of the Processing of the Controller Data are set out in the Principal Agreement and this Annex.
- The nature and purpose of the Processing of Controller Data
WalkMe has developed, and owns a Software as a Service (SaaS) digital adoption platforms solutions that provide guidance and engagement tools, analytics and automation for web, mobile and desktop applications, simplifying and improving End Users’ experience, and increasing user engagement (“Service- as further defined in the Principal Agreement).
The Controller Data is collected by Processor when an End User (as defined in the Principal Agreement) uses the Service.
The Controller Data is processed for the purpose of providing the Service, the ongoing operation thereof, and/or for security purposes.
- The types of Controller Data to be Processed
3.1 End-Users’ IP addresses, Web Application data (page title, URL) and Location information (country and city).
3.2 Email addresses and log-in credentials of authorized Controller personnel inherent for the provision of the Service, for the purpose of creating Outputs (as defined in the Principal Agreement – also referred to as the “WalkMe Editor Admins”) and of those End Users which contact Processor in connection with the provision of technical support for the Service.
- The categories of Data Subject to whom the Controller Data relates
Data subjects are the End-Users of the Service and authorized Controller Personnel (i.e. WalkMe Editor admins).
- The obligations and rights of Controller
The obligations and rights of Controller are set out in this DPA, the Principal Agreement and this Annex.
- Retention Periods
Processor will retain Controller Data it processes hereunder only for as long as required to provide the Service pursuant to the Principal Agreement.
Unless otherwise agreed in writing by the Parties, after a request from the Controller to delete any Controller Data or upon termination or expiration of the Principal Agreement, an automated process will begin that permanently deletes the data in accordance with the timelines set forth in the tables below. Once initiated, this process cannot be reversed, and data will be permanently deleted.
|Type||Timeline for Deletion (after deletion process begins) for Cancellation, Termination or Migration|
|Access Logs||2 years|
|Data in Analytics Platform||90 days|
|Communications regarding requests for data deletion and exercise of individual rights||At least 24 months|