·Transparency Report

·Published: May 9, 2023

·This document provides information about Salesforce's principles for handling government requests for customer data and the relevant annual figures regarding such requests.

·Background

·Like many other technology companies, Salesforce may on occasion receive a request from a law enforcement or other government agency seeking access to certain data, including access to data belonging to a customer. Salesforce receives relatively few government requests for customer data as a primarily B2B company. Our goal is always to protect our customers' data, while complying with applicable laws.

·This document explains the principles that Salesforce follows if we receive such a request and provides information regarding the types and numbers of requests that we have received from law enforcement and other government agencies, and how we responded to them, during the period from January 1, 2022, to December 31, 2022 (the "Covered Period"). Customers may provide this information to their supervisory authorities, if required.

·The term "customer data" used in this document refers to electronic data and information submitted by or for customers to our services, as further defined in the Main Services Agreement.

·Our Policies and Process

·Trust is our #1 value

·At Salesforce, trust is our number one value. The protection of our customers' data is paramount to us, and we safeguard that data with a robust, comprehensive, and transparent privacy and security program. Our privacy and security programs are designed to protect our customers' privacy and protect data submitted by or for our customers to our services against unauthorized access or disclosure.

·Salesforce offers its customers various contractual commitments in its Main Services Agreement (including its Data Processing Addendum) which align to the principles described below. More precisely, these commitments can be found in section 8 "Government Access Requests" of Salesforce's Data Processing Addendum, clause 15 of the Standard Contractual Clauses, which form part of the Data Processing Addendum, and section 10 of Salesforce's EU and UK Processor Binding Corporate Rules. Salesforce strongly believes that these contractual protections provide customers as much legal certainty as possible in relation to compelled disclosure.

·For that reason, every government request for customer data that Salesforce receives is carefully reviewed, consistent with the laws in the relevant jurisdiction(s), to ensure the requesting government agency is entitled to the data sought with the type of process utilized. Where we believe a government request for customer data is invalid or unlawful, we will try to challenge it. We aim to fully meet our legal obligations while honoring the faith that our customers place in us.

·We notify an affected customer of any legally binding and valid request for its data or any direct access to customer data by a law enforcement or other government agency, unless we are explicitly prohibited from doing so by law.

·Trust starts with transparency. Unless prohibited by law, Salesforce always notifies a customer when it receives a legally binding and valid request for that customer's data, including a government request. We also promptly notify a customer if we become aware of any direct access by a government agency to customer data, and we will provide information that is available to us in this respect, to the extent permitted by law.

·Where possible, we refer the requesting government agency to the affected customer.

·We believe our customers should have as much control as possible over their respective data. Salesforce is not the owner of our customers' data, and we strongly believe that any government agency seeking access to customer data should address its request directly with that customer, where possible. Accordingly, if we receive a government request for customer data, unless prohibited by law, we endeavor to refer the requesting agency to the affected customer so that the customer can work with the government agency directly to respond.

·We do not disclose customer data to government agencies unless compelled by law and we challenge or reject unlawful requests.

·We review each government request for customer data on a case-by-case basis and only comply if and to the extent we determine the request is legally binding and valid and we are required to do so under applicable procedural rules. We do not provide government agencies with direct or unrestricted access to our customer's data. When reviewing the lawfulness of a government request, we take into account all applicable laws, including the laws of other jurisdictions. We require government agencies to follow the required legal process under applicable laws, such as issuing their request via a subpoena, court order, or search warrant. Where we believe a government request for customer data is invalid or unlawful, we try to challenge it and pursue possibilities of appeal. If we are required to disclose customer data to government agencies, we ensure the transfer is necessary and proportionate and provide the minimum amount of information possible, based on a reasonable interpretation of the request. We apply this principle equally to all government agencies (that is, whether it is a request relating to law enforcement or national security).

·If prohibited by law from notifying the affected customer, we try to get that legal restriction waived.

·If we receive a government agency request for data, and we are prohibited by law from notifying the affected customer, we use best efforts to request that the confidentiality requirement be waived in order for us to notify the appropriate data protection authorities. We keep a record of the actions we have taken to waive any applicable confidentiality requirements.

·We do not provide any government agency with encryption keys or any other way to break encryption.

·Salesforce provides options to encrypt customer data at rest and in transit. Salesforce ensures that encryption keys are securely stored and managed in accordance with industry best practice. Many of the Salesforce services provide the option for customers to create and manage their own encryption keys, or for the encryption keys to be managed through a third party provider. This allows customers to protect and control who has access to their data.

·Salesforce does not provide any government agency with encryption keys used to secure customers' data and not facilitating any other means of breaking the encryption.

·We do not build backdoors into our products.

·We have not purposefully created back doors or similar programming that allows access by a government agency to our services or customers' data.

·Figures

·Types of Legal Processes Received

·The figures below represent the total numbers of various forms of government requests for customer data, or their local equivalents, received during the Covered Period from January 1, 2022, to December 31, 2022. Any requests that do not pertain to customer data are not included in these figures.

·Requests by Country

·Although Salesforce is headquartered in the U.S., we provide services in jurisdictions around the world and have a corporate presence in several countries. Salesforce complies with the law in all jurisdictions where we operate and is thus required to respond to requests in all the countries that have legal jurisdiction over our operations. When we receive requests from governments in any country, we evaluate them carefully for validity and applicability before responding.

11 This category includes, for example, grand jury, administrative, and civil subpoenas issued by a government agency, as well as their equivalents in other jurisdictions.

22 This category includes, for example, pen register and trap and trace orders, and orders authorized under 18 U.S.C. § 2703(d), as well as their equivalents in other jurisdictions.

·The figures below represent the total number of government requests for customer data received for the Covered Period, organized by country of origin. Any requests that do not pertain to customer data are not included. Note that any potential requests made under the CLOUD Act in the U.S. are included in the figures below. Country | Number of Requests Received United States | 53 Australia | 1 The Netherlands | 1 Singapore | 1 Spain | 1 Total Requests Received | 57

·Requests by Response

·The figures below represent the total number of government requests for customer data received for the Covered Period, categorized by data disclosed. "Content" refers to electronic data and information that our customers submit to our services, including customer data. "Non-Content" is Confidential Information that is not customer data, as these terms are defined in the Main Services Agreement. It includes basic customer information (such as name, address, email address, billing information) and service derived and generated data.

·U.S. National Security Requests

·In the United States, companies are legally prohibited from disclosing the precise number of received National Security Letters (NSLs) and court orders under the Foreign Intelligence Surveillance Act (FISA). However, the USA Freedom Act enables us to report such requests (including both NSLs and FISA orders) in broad ranges, which we do below. No inferences should be drawn from the limits of the below ranges and, as previously stated, Salesforce receives relatively few government requests of any kind.

·DATA PROCESSING ADDENDUM

·(Revision August 2026)

·This Data Processing Addendum, including its Schedules, ("DPA") forms part of the Main Services Agreement or other written or electronic agreement between SFDC and Customer for the purchase of Services from SFDC (the "Agreement") to reflect the Parties' agreement with regard to the Processing of Personal Data.

·HOW TO EXECUTE THIS DPA:

• 11. This DPA consists of two parts: the main body of the DPA, and Schedules 1 and 2.
• 22. This DPA has been pre-signed on behalf of SFDC. Schedule 2, section 1 has been pre-signed by Salesforce, Inc. as the data importer. Please note that the contracting entity under the Agreement may be a different entity than Salesforce, Inc.
• 33. To complete this DPA, Customer must:
• 4Complete the information in the signature box and sign on page 6.
• 5Send the signed DPA to SFDC by email to dataprocessingaddendum@salesforce.com indicating the Customer's Account Number (as set out on the SFDC Order Form or invoice).

·Except as otherwise expressly provided in the Agreement, this DPA will become legally binding once SFDC receives the validly completed DPA at this email address.

·For the avoidance of doubt, signature of the DPA on page 6 shall be deemed signature and acceptance of the Standard Contractual Clauses, including Schedule 2. Where Customer wishes to separately execute the Standard Contractual Clauses and its Appendix, Customer should also complete the information as the data exporter and sign on page 15 (Schedule 2).

·HOW THIS DPA APPLIES

·If the Customer entity signing this DPA is a party to the Agreement, this DPA is an addendum to and forms part of the Agreement and the SFDC entity that is party to the Agreement is party to this DPA.

·If the Customer entity signing this DPA has executed an Order Form with SFDC or its Affiliate under the Agreement, but is not itself a party to the Agreement, this DPA is an addendum to that Order Form and applicable renewal Order Form(s), and the SFDC entity that is party to such Order Form is party to this DPA. For the purposes of this DPA, any reference to Order Form herein shall include "Ordering Document" (as defined in the Agreement).

·If the Customer entity signing this DPA is not a party to an Order Form or the Agreement, this DPA is not valid and is not legally binding. Such entity should request the Customer entity who is a party to the Agreement execute this DPA.

·DATA PROCESSING TERMS

11. DEFINITIONS

·"CCPA" means the California Consumer Privacy Act, Cal. Civ. Code § 1798.100 et seq., as amended by the California Privacy Rights Act, and its implementing regulations.

·"Controller" means the entity which determines the purposes and means of the Processing of Personal Data, including as applicable any "business" as that term is defined by CCPA.

·"Data Protection Laws and Regulations" means all laws and regulations that apply to the Processing of Personal Data under the Agreement.

·"Data Subject" means the identified or identifiable person to whom Personal Data relates.

·"Personal Data" means any information relating to (i) an identified or identifiable natural person or, (ii) an identified or identifiable legal entity (where such information is protected similarly as personal data or personally identifiable information under applicable Data Protection Laws and Regulations), where for each (i) or (ii), such data is Customer Data.

·"Processing" or "Process" means any operation or set of operations which is performed upon Personal Data, whether or not by automatic 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 the entity which Processes Personal Data on behalf of the Controller, including as applicable any "service provider" as that term is defined by the CCPA.

·"Public Authority" means a government agency or law enforcement authority, including judicial authorities.

·"Salesforce Processor BCR" means Salesforce's processor binding corporate rules for the Processing of Personal Data, the most current versions of which are available on SFDC's website, currently located at https://www.salesforce.com/company/privacy.

·"Security, Privacy and Architecture Documentation" means the Security, Privacy and Architecture Documentation for the Services purchased by Customer, as updated from time to time, and accessible via SFDC's Trust and Compliance webpage at https://www.salesforce.com/company/legal/trust-and-compliance-documentation/, or as otherwise made reasonably available by SFDC.

·"SFDC" means the SFDC entity which is a party to this DPA, as specified in the section "HOW THIS DPA APPLIES" above.

·"SFDC Group" means SFDC and its Affiliates engaged in the Processing of Personal Data.

·"Sub-processor" means any Processor engaged by SFDC or a member of the SFDC Group.

22. PROCESSING OF PERSONAL DATA

• 2.12.1. Customer's Processing of Personal Data. As a Controller or Processor, Customer shall comply with all applicable Data Protection Laws and Regulations in its use of the Services, including by ensuring that its instructions to SFDC are lawful, and by complying with any requirement to provide notice to Data Subjects of the use of SFDC as Processor.
• 2.22.2. SFDC's Processing of Personal Data. As Processor, SFDC shall treat Personal Data as Confidential Information, Process Personal Data on behalf of Customer, and Process Personal Data only under Customer's documented instructions for the following purposes: (i) Processing in accordance with the Agreement and Order Form(s); (ii) Processing initiated by Users in their use of the Services; and (iii) Processing to comply with other documented reasonable instructions provided by Customer (e.g., via email) where such instructions are consistent with the terms of the Agreement.
• 2.32.3. Details of the Processing. The subject-matter of Processing of Personal Data by SFDC is the performance of the Services under the Agreement. The duration of the Processing, the nature and purpose of the Processing, the types of Personal Data and categories of Data Subjects Processed under this DPA are further specified in Schedule 2 (Description of Processing/Transfer) to this DPA.

33. RIGHTS OF DATA SUBJECTS

• 3.13.1. Data Subject Request. SFDC shall, to the extent legally permitted, promptly notify Customer of any complaint, dispute or request it has received from a Data Subject, each such request being a "Data Subject Request." SFDC shall not respond to a Data Subject Request itself, except that Customer authorizes SFDC to redirect the Data Subject Request as necessary to allow Customer to respond directly.
• 3.23.2. Required Assistance. Taking into account the nature of the Processing, SFDC shall assist Customer by appropriate technical and organizational measures, insofar as this is possible, for the fulfillment of Customer's obligation to respond to a Data Subject Request under Data Protection Laws and Regulations.
• 3.33.3. Additional Assistance. To the extent Customer, in its use of the Services, does not have the ability to address a Data Subject Request, SFDC shall upon Customer's request provide commercially reasonable efforts to assist Customer in responding, to the extent SFDC is legally permitted to do so and the response is required under Data Protection Laws and Regulations. To the extent legally permitted, Customer shall be responsible for any costs arising from SFDC's provision of such assistance.

44. SFDC PERSONNEL AND DATA PROTECTION OFFICER

• 4.14.1. Confidentiality, Reliability and Limitation of Access. SFDC shall ensure that its personnel engaged in the Processing of Personal Data are informed of the confidential nature of the Personal Data, receive appropriate training on their responsibilities and have executed written confidentiality agreements. SFDC shall:

·(i) ensure that such confidentiality obligations survive the termination of the personnel engagement;

• ·(ii) take commercially reasonable steps to ensure the reliability of any SFDC personnel engaged in the Processing of Personal Data; and
• ·(iii) ensure that SFDC's access to Personal Data is limited to those personnel performing Services in accordance with the Agreement, Order Form(s) and Documentation.
• ·Data Protection Officer. Members of the SFDC Group have appointed a data protection officer. The appointed person may be reached at privacy@salesforce.com.

55. SUB-PROCESSORS

• 5.15.1. Appointment of Sub-processors. Customer acknowledges and agrees that (a) SFDC's Affiliates may be retained as Subprocessors; and (b) SFDC and SFDC's Affiliates respectively may engage third-party Sub-processors to provide the Services. SFDC or an SFDC Affiliate has entered into a written agreement with each Sub-processor containing, in substance, data protection obligations no less protective of Personal Data than those in the Agreement.
• 5.25.2. Current List of Sub-processors and Notification of New Sub-processors. The current list of Sub-processors engaged in Processing Personal Data for the performance of each Service, including a description of their processing activities and countries of location, is listed in the Infrastructure and Sub-processor Documentation which can be found on SFDC's Trust and Compliance webpage at https://www.salesforce.com/company/legal/trust-and-compliance-documentation/ ("Infrastructure and Sub-processor Documentation"), or as otherwise made reasonably available by SFDC. Customer hereby consents to these Sub-processors, their locations and processing activities. The Infrastructure and Sub-processor Documentation contains a mechanism to subscribe to notifications of new Sub-processors for each Service, and if Customer subscribes, SFDC shall notify Customer before authorizing any new Sub-processor to Process Personal Data for that Service.
• 5.35.3. Objection Right for New Sub-processors. Customer may object to SFDC's use of a new Sub-processor by notifying SFDC promptly in writing within thirty (30) days of SFDC sending notice under section 5.2. If Customer objects, SFDC will use commercially reasonable efforts to make available to Customer a change in the Services or recommend a commercially reasonable change to Customer's configuration or use of the Services to avoid Processing of Personal Data by the new Subprocessor without unreasonably burdening Customer. If SFDC is unable to make available such change within sixty (60) days, Customer may terminate the applicable Order Form(s) with respect only to those Services which cannot be provided by SFDC without the use of the new Sub-processor by providing written notice to SFDC. SFDC will refund Customer any prepaid fees covering the remainder of the term of such Order Form(s) following the effective date of termination with respect to the terminated Services, without imposing a penalty for such termination on Customer.
• 5.45.4. Liability. SFDC shall be liable for the acts and omissions of its Sub-processors to the same extent SFDC would be liable if performing the services of each Sub-processor directly under the terms of this DPA, unless otherwise set forth in the Agreement.

66. SECURITY, CERTIFICATIONS AND AUDIT

• 6.16.1. Controls for the Protection of Customer Data. SFDC shall maintain appropriate technical and organizational measures for the protection of the security, confidentiality and integrity of Customer Data (including measures designed to protect against unauthorized or unlawful Processing and against accidental or unlawful destruction, loss, alteration, or damage, unauthorized access to or disclosure of Customer Data), as set forth in the Security, Privacy and Architecture Documentation. SFDC regularly monitors compliance with these measures. SFDC will not materially decrease the overall security of the Services during a subscription term.
• 6.26.2. Third-Party Certifications and Audits. SFDC has obtained the third-party certifications and audits set forth in the Security, Privacy and Architecture Documentation for each applicable Service. Where SFDC has obtained ISO 27001 certifications and SSAE 18 Service Organization Control (SOC) 2 reports for a particular Service as described in the Documentation, SFDC agrees to maintain these certifications or standards, or appropriate and comparable successors thereof, for the duration of the subscription term.
• 6.36.3. Audit Program. SFDC shall maintain an audit program to help ensure compliance with the obligations set out in this DPA and shall make available to Customer information to demonstrate compliance with the obligations set out in this DPA, including those obligations required by applicable Data Protection Laws and Regulations, as follows:
• 6.3.16.3.1. Access to Third-Party Certification and Audit Information. Upon Customer's written request at reasonable intervals, and subject to the confidentiality obligations set forth in the Agreement, SFDC shall:
• 5(i) make available to Customer (or Customer's Third-Party Auditor as defined below) information regarding SFDC's compliance with the obligations set forth in this DPA in the form of a copy of SFDC's then most recent third-party audits or certifications set forth in the Security, Privacy and Architecture Documentation. Such third-party audits or certifications may also be shared with Customer's competent supervisory authority on its request;
• 6(ii) provide Customer with a report and/or confirmation of SFDC's audits of third-party Sub-processors' compliance with the data protection controls set forth in this DPA and/or a report of third-party auditors' audits of Sub-processors that

·have been provided by those Sub-processors to SFDC, to the extent such reports or evidence may be shared with Customer ("Sub-processor Audit Reports"). Customer acknowledges that (i) Sub-processor Audit Reports are both Confidential Information and confidential information of the Sub-processor and (ii) Sub-processors may require Customer to execute a non-disclosure agreement with them to view a Sub-processor Audit Report.

6.3.26.3.2. On-Site Audit. Customer can request an on-site audit of SFDC's Processing activities covered by this DPA ("OnSite Audit"). An On-Site Audit may be conducted by Customer either itself or through a Third-Party Auditor selected by Customer when:

• ·(i) the information available under the section "Third-Party Certifications and Audits" is insufficient to demonstrate compliance with the obligations set out in this DPA and its Schedules;
• ·(ii) Customer has received a notice from SFDC of a Customer Data Incident; or
• ·(iii) such an audit is required by Data Protection Laws and Regulations or by Customer's competent supervisory authority.

·Any On-Site Audit will be limited to Customer Data Processing facilities operated by SFDC or its Affiliates.

6.3.36.3.3. Reasonable Exercise of Rights. An On-Site Audit shall be conducted by Customer or its Third-Party Auditor:

• ·(i) acting reasonably, in good faith, and in a proportional manner, taking into account the nature and complexity of the Services used by Customer;
• ·(ii) up to one time per year with at least three weeks' advance written notice. If an emergency justifies a shorter notice period, SFDC will use good faith efforts to accommodate the On-Site Audit request; and
• ·(iii) during SFDC's normal business hours, under reasonable duration and without unreasonably interfering with SFDC's day-to-day operations.

·Before any On-Site Audit, Customer and SFDC shall agree on the scope, timing, and duration of the audit and the reimbursement rate for which Customer shall be responsible. All reimbursement rates shall be reasonable, taking into account the resources expended by or on behalf of SFDC. SFDC shall have the right to reasonably adapt the scope of any On-Site Audit to avoid or mitigate risks including service levels, availability, and confidentiality of other SFDC customers' information.

6.3.46.3.4. Third-Party Auditor. A Third-Party Auditor means a third-party independent contractor that is not a competitor of SFDC. An On-Site Audit can be conducted through a Third Party Auditor if:

• ·(i) the Third-Party Auditor enters into a non-disclosure agreement containing confidentiality provisions no less protective than those set forth in the Agreement to protect SFDC's proprietary information; and
• ·(ii) Customer bears the costs of the Third-Party Auditor.

6.3.56.3.5. Findings. Customer must promptly provide SFDC with information regarding any non-compliance discovered during an On-Site Audit.

• 6.46.4. Data Protection Impact Assessment. Upon Customer's request, SFDC shall provide Customer with reasonable cooperation and assistance needed to fulfill Customer's obligation under Data Protection Laws and Regulations to carry out a data protection impact assessment related to Customer's use of the Services, to the extent Customer does not otherwise have access to the relevant information, and to the extent such information is available to SFDC.

77. CUSTOMER DATA INCIDENT MANAGEMENT AND NOTIFICATION

·SFDC maintains security incident management policies and procedures specified in the Security, Privacy and Architecture Documentation and shall notify Customer without undue delay after becoming aware of the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or access to Customer Data, including Personal Data, transmitted, stored or otherwise Processed by SFDC or its Sub-processors (a "Customer Data Incident"). SFDC shall make reasonable efforts to identify the cause of such Customer Data Incident and take steps it deems necessary and reasonable to remediate the cause of such a Customer Data Incident to the extent the remediation is within SFDC's reasonable control. The obligations herein shall not apply to incidents that are caused by Customer or Customer's Users.

88. GOVERNMENT REQUESTS

8.18.1 SFDC Requirements. As a Processor, SFDC shall maintain appropriate measures to protect Personal Data in accordance with the requirements of Data Protection Laws and Regulations, including by implementing appropriate technical and organizational safeguards to protect Personal Data against any interference that goes beyond what is necessary in a democratic society to safeguard national security, defense and public security. If SFDC receives a legally binding request to access Personal Data from a Public Authority, SFDC shall, unless otherwise legally prohibited, promptly notify Customer including a summary of the nature of the request. To the extent SFDC is prohibited by law from providing such notification, SFDC shall use commercially reasonable efforts to obtain a waiver of the prohibition to enable SFDC to communicate as much information as possible, without undue delay. Further, SFDC shall challenge the request if, after careful assessment, it concludes that there are reasonable grounds to consider that the request is unlawful. SFDC shall pursue appeals where available. When challenging a request, SFDC shall seek interim measures to suspend the effects of the request until the competent judicial authority has decided on its merits. It shall not disclose the Personal Data requested until required to do so under the applicable procedural rules. SFDC agrees it will provide the minimum amount of information permissible when responding to a request for disclosure, based on a reasonable interpretation of the request. SFDC shall promptly notify Customer if SFDC becomes aware of any direct access by a Public Authority to Personal Data and shall provide Customer with related information available to SFDC, if permitted by law. SFDC certifies that SFDC (1) has not purposefully created back doors or similar programming for the purpose of allowing access to the Services and/or Personal Data by any Public Authority; (2) has not purposefully created or changed its business processes in a manner that facilitates access to the Services and/or Personal Data by any Public Authority; and (3) at the Effective Date is not currently aware of any national law or government policy requiring SFDC to create or maintain back doors, or to facilitate access to the Services or Personal Data, or to keep in its possession any encryption keys or hand over encryption keys to any third party.

8.28.2 Sub-processors Requirements. SFDC shall ensure that Sub-processors involved in the Processing of Personal Data are subject to the relevant commitments regarding Government Access Requests in the Standard Contractual Clauses and Salesforce Processor BCR.

99. RETURN AND DELETION OF CUSTOMER DATA

·SFDC shall return Customer Data to Customer and, to the extent allowed by applicable law, delete Customer Data in accordance with the procedures and timeframes specified in the Security, Privacy and Architecture Documentation. Until Customer Data is deleted or returned, SFDC shall continue to comply with this DPA and its Schedules.

1010. AFFILIATES

·Customer enters into this DPA on behalf of itself and, to the extent required under Data Protection Laws and Regulations, in the name and on behalf of its Affiliates authorized to use the Services under the Agreement. Except where applicable Data Protection Laws and Regulations require such an Affiliate to exercise a right or seek any remedy under this DPA against SFDC directly, the parties agree that solely the Customer that is the contracting party to the Agreement shall exercise rights and remedies under this DPA, in a combined manner for itself and all of its Affiliates. For the avoidance of doubt, an Affiliate is not and does not become a party to the Agreement, and is a party only to this DPA unless it has signed an Order Form.

1111. REMEDIES

·Each party's and all of its Affiliates' liability, taken together in the aggregate, arising out of or related to this DPA, whether in contract, tort or under any other theory of liability, is subject to the 'Limitation of Liability' section of the Agreement.

1212. EUROPE SPECIFIC PROVISIONS

• 12.112.1. Definitions. For the purposes of this section 12, Schedule 1, and Schedule 2 these terms shall be defined as follows:

·"Europe" means the European Union, the European Economic Area, Switzerland and the United Kingdom.

·"European Data Protection Laws and Regulations" means the Data Protection Laws and Regulations applying in Europe.

·"European Personal Data" means the Personal Data subject to European Data Protection Laws and Regulations.

·"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 (General Data Protection Regulation), including as implemented or adopted under the laws of the United Kingdom.

·"SCC Module 2" means Standard Contractual Clauses sections I, II, III and IV to the extent they reference Module Two (Controller-to-Processor).

·"SCC Module 3" means Standard Contractual Clauses sections I, II III and IV to the extent they reference Module Three (Processor-to-Processor).

·"Standard Contractual Clauses" means Standard Contractual Clauses for the transfer of Personal Data to third countries pursuant to Regulation (EU) 2016/679 of the European Parliament and the Council approved by European Commission Implementing Decision (EU) 2021/914 of 4 June 2021, as currently set out at https://eurlex.europa.eu/eli/dec_impl/2021/914/oj.

·"Third-Country Transfer" means a transfer of European Personal Data that is not subject to an adequacy decision by the European Commission. When US entities part of the SFDC Group or its Sub-processors are certified under the EU-US Data Privacy Framework and its extensions, the Parties agree that transfers to such entities are not considered Third-Country Transfers.

• 12.212.2. GDPR. SFDC will Process European Personal Data in accordance with the GDPR requirements directly applicable to SFDC's provision of its Services.
• 12.312.3. Customer Instructions. SFDC shall inform Customer immediately (i) if, in its opinion, an instruction from Customer constitutes a breach of the GDPR and/or (ii) if SFDC is unable to follow Customer's instructions for the Processing of European Personal Data.
• 12.412.4. Transfer Mechanisms for Data Transfers. If, in the performance or use of the Services, European Personal Data is subject to a Third-Country Transfer, the transfer mechanisms listed below shall apply:
• 4Salesforce Processor BCR, which shall apply to the Services listed in the Appendix to the Salesforce Processor BCR (the "BCR Services"), subject to the additional terms in section 1 of Schedule 1;
• 5SCC Module 2. Where Customer is a Controller and a data exporter, subject to the additional terms in section 2 of Schedule 1; and/or
• 6SCC Module 3. Where Customer is a Processor acting on behalf of a Controller and a data exporter, subject to the additional terms in sections 2 and 3 of Schedule 1.
• 12.512.5. Impact of Local Laws. As of the Effective Date, SFDC has no reason to believe that the laws and practices in any third country where it Processes European Personal Data as set forth in the Infrastructure and Sub-processors Documentation, including any requirements to disclose European Personal Data or measures authorizing access by a Public Authority, prevent SFDC from fulfilling its obligations under this DPA. If SFDC reasonably believes that any existing or future enacted or enforceable laws and practices in the third country where it Processes European Personal Data ("Local Laws") prevent it from fulfilling its obligations under this DPA, it shall promptly notify Customer. SFDC shall then use commercially reasonable efforts to make available to Customer a change in the Services or recommend a commercially reasonable change to Customer's configuration or use of the Services to facilitate compliance with the Local Laws without unreasonably burdening Customer. If SFDC is unable to make available such change promptly, Customer may terminate the applicable Order Form(s) and suspend the transfer of European Personal Data in respect only to those Services which cannot be provided by SFDC in accordance with the Local Laws by providing written notice in accordance with the "Notices" section of the Agreement. Customer shall receive a refund of any prepaid fees for the period following the effective date of termination for such terminated Services. If SFDC receives an order from a government to suspend or cease cloud operations in Europe, SFDC shall promptly contest such a measure using all legal avenues available, including by pursuing litigation in court.

1313. APEC PRIVACY RECOGNITION FOR PROCESSORS

·SFDC and the SFDC Group have obtained APEC Privacy Recognition for Processors ("PRP") certification available at https://www.salesforce.com/company/privacy/ and https://slack.com/trust/security.

1414. LEGAL EFFECT

·This DPA shall only become legally binding between Customer and SFDC (and Salesforce, Inc., if different) when the formalities steps set out in the section "HOW TO EXECUTE THIS DPA" above have been fully completed.

·List of Schedules

Schedule 1Schedule 1: Transfer Mechanisms for European Data Transfers

Schedule 2Schedule 2: Description of Processing/Transfer

·The parties' authorized signatories have duly executed this DPA:

·CUSTOMER

·Signature: ________________________________

·Customer Legal Name: ______________________

·Print Name: _______________________________

·Title: ____________________________________

·Date: ____________________________________

·SALESFORCE, INC. (F/K/A SALESFORCE.COM, INC.)

·Signature: _______________________________

·Print Name: Scott Siamas___________________ Senior Vice President,

·Title: ___________________________________ Associate General Counsel

·Date: 8/6/2026_____________________________

·SALESFORCE.COM CANADA CORPORATION

·Signature: ______________________________

·Print Name: Scott Siamas__________________

·Title: _________________________________ Vice President

·Date: 8/6/2026_____________________________

·SALESFORCE.COM GERMANY GMBH

·SALESFORCE.COM FRANCE S.A.S.

·Signature: ______________________________

·Print Name: Stéphane Jacottet______________ EMEA&LATAM Controller

·Title: __________________________________

·Date: 8/6/2026_____________________________

·SALESFORCE.COM INDIA PRIVATE LIMITED

·Signature: _______________________________

·Print Name: Sarita Sachdev__________________

·Title: ___________________________________

·Date: 8/6/2026_____________________________

·Signature: _______________________________

·Print Name: Stéphane Jacottet______________

·Title: _________________________________ EMEA&LATAM Controller

·Date: 8/6/2026_____________________________ Director

·SALESFORCE.COM ITALY S.R.L.

·Signature: _______________________________

·Print Name: Stéphane Jacottet______________

·Title: ____________________________________ EMEA&LATAM Controller

·Date: 8/6/2026_____________________________

·SALESFORCE JAPAN CO., LTD. (F/K/A KABUSHIKI KAISHA SALESFORCE.COM)

·Signature: _______________________________

·Print Name: Shinichi Koide__________________ CEO

·Title: _____________________________________

·Date: 8/6/2026_____________________________

·SALESFORCE TECNOLOGIA LTDA.

·SALESFORCE.COM SINGAPORE PTE. LTD.

·Signature: _______________________________

·Print Name: Benson Wong__________________ Director

·Title: ____________________________________

·Date: 8/6/2026_____________________________

·SALESFORCE SYSTEMS SPAIN, S.L.

·Signature: _______________________________

·Print Name: Stéphane Jacottet________________ EMEA&LATAM Controller

·Title: ___________________________________

·Date: 8/6/2026_____________________________

·SALESFORCE UK LIMITED (F/K/A SALESFORCE.COM EMEA LIMITED)

·Signature: _______________________________

·Print Name: Stéphane Jacottet______________

·Title: ____________________________________

·Date: 8/6/2026_____________________________

·Signature: _______________________________

·Print Name: Alexandre Costa________________ Director

·Title: ____________________________________

·Date: 8/6/2026_____________________________ EMEA&LATAM Controller

·SFDC AUSTRALIA PTY, LTD.

·Signature: _______________________________

·Print Name: Benson Wong__________________ Director

·Title: ___________________________________

·Date: 8/6/2026___________________________

·DEMANDWARE, LLC

·Signature: _______________________________

·Print Name: Scott Siamas___________________

·Title: ______________________________ President and Secretary

·Date: 8/6/2026_____________________________

·MULESOFT, LLC

·Signature: _______________________________

·Print Name: Scott Siamas___________________ President and Secretary

·Title: ___________________________________

·Date: 8/6/2026_____________________________

·SLACK TECHNOLOGIES, LLC

·Signature: _______________________________

·Print Name: Scott Siamas___________________

·Title: ___________________________________ President and Secretary

·Date: 8/6/2026_____________________________

·INFA DENMARK APS

·Signature: _______________________________

·Print Name: Nicholas Smith________________ VP Finance

·Title: ____________________________________

·Date: 8/6/2026_____________________________

·SFDC IRELAND LIMITED

·Signature: _______________________________

·Print Name: Patrick Tobin___________________ Director

·Title: ____________________________________

·Date: 8/6/2026_____________________________

·HEROKU, INC.

·Signature: _______________________________

·Print Name: Scott Siamas___________________

·Title: ____________________________________ President and Secretary

·Date: 8/6/2026_____________________________

·SLACK TECHNOLOGIES LIMITED

·Signature: _______________________________

·Print Name: Patrick Tobin___________________ Director

·Title: ____________________________________

·Date: 8/6/2026_____________________________

·TABLEAU SOFTWARE, LLC

·Signature: _______________________________

·Print Name: Scott Siamas___________________

·Title: ____________________________________ President and Secretary

·Date: 8/6/2026_____________________________

·I.D.I INFORMATICA DATA INTEGRATION LIMITED

·Signature: _______________________________

·Print Name: Nicholas Smith________________ VP Finance

·Title: ___________________________________

·Date: 8/6/2026_____________________________

·INFO CORP INFORMATICA PORTUGAL, SOCIEDADE UNIPESSOAL LDA.

·Signature: _______________________________

·Print Name: Nicholas Smith________________

·Title: ___________________________________ VP Finance

·Date: 8/6/2026_____________________________

·INFORMATICA BELGIE BVBA

·Signature: _______________________________

·Print Name: Nicholas Smith________________ VP Finance

·Title: ____________________________________

·Date: 8/6/2026_____________________________

·INFORMATICA GMBH

·Signature: _______________________________

·Print Name: Stuart Robson__________________ Senior dorecot

·Title: ____________________________________

·Date: 8/6/2026_____________________________

·INFORMATICA LLC

·Signature: _______________________________

·Print Name: Scott Siamas___________________

·Title: _____________________________________ President and Secretary

·Date: 8/6/2026_____________________________

·INFORMATICA SOFTWARE ITALIA S.R.L.

·Signature: _______________________________

·Print Name: Stuart Robson__________________

·Title: ___________________________________ Senior director

·Date: 8/6/2026_____________________________

·INFA SWEDEN AB

·Signature: _______________________________

·Print Name: Nicholas Smith________________

·Title: ____________________________________ VP Finance

·Date: 8/6/2026_____________________________

·INFORMATICA AUSTRALIA PTY. LTD.

·Signature: _______________________________

·Print Name: Nadeem Mohammed_____________ Senior Finance Director

·Title: ____________________________________

·Date: 8/6/2026_____________________________

·INFORMATICA DATA INTEGRATION IBÉRICA, S.L.

·Signature: _______________________________

·Print Name: Stuart Robson__________________

·Title: ____________________________________ Senior directo

·Date: 8/6/2026_____________________________

·INFORMATICA IRELAND EMEA UNLIMITED COMPANY

·Signature: _______________________________

·Print Name: Tony McAuliffe__________________ Director

·Title: _____________________________________

·Date: 8/6/2026_____________________________

·INFORMATICA SOFTWARE (SCHWEIZ) GMBH

·Signature: _______________________________

·Print Name: Stuart Robson__________________ Senior director

·Title: ____________________________________

·Date: 8/6/2026_____________________________

·INFORMATICA SOFTWARE NEDERLAND B.V.

·Signature: _______________________________

·Print Name: Stuart Robson__________________

·Title: __________________________________ Senior director

·Date: 8/6/2026_____________________________

·IS INFORMATICA SOFTWARE LTDA

·Signature: _______________________________

·Print Name: Alexandre Costa________________

·Title: ___________________________________ Director

·Date: 8/6/2026____________________________

·INFORMATICA ARABIA INFORMATION TECHNOLOGY

·Signature: _______________________________

·Print Name: Nicholas Smith________________ VP Finance

·Title: ____________________________________

·Date: 8/6/2026_____________________________

·INFORMATICA S.E.A. PTE. LTD.

·Signature: _______________________________

·Print Name: Nadeem Mohammed_____________

·Title: ___________________________________ Senior Finance Director

·Date: 8/6/2026_____________________________

·APROMORE, INC.

·Signature: _______________________________

·Print Name: Scott Siamas___________________

·Title: _________________________________________ President and Secretary

·Date: 8/6/2026_____________________________

·INFORMATICA SOFTWARE LIMITED [UK]

·Signature: _______________________________

·Print Name: Nicholas Smith________________

·Title: ____________________________________ VP Finance

·Date: 8/6/2026_____________________________

·INFORMÁTICA SOFTWARE DE MÉXICO, S. DE R.L. DE C.V.

·Signature: _______________________________

·Print Name: Nicholas Smith________________

·Title: ____________________________________ VP Finance

·Date: 8/6/2026_____________________________

·INFORMATICA AUSTRALIA PTY. LTD. (NEW ZEALAND BRANCH)

·Signature: _______________________________

·Print Name: Nadeem Mohammed_____________

·Title: ___________________________________ Senior Finance Director

·Date: 8/6/2026_____________________________

·APROMORE PTY LTD

·Signature: _______________________________

·Print Name: Benson Wong__________________

·Title: ____________________________________ Director

·Date: 8/6/2026_____________________________

·CIMULATE, INC.

·Signature: _______________________________

·Print Name: Scott Siamas___________________ President and Secretary

·Title: ____________________________________

·Date: 8/6/2026_____________________________

·M3TER UK LIMITED

·Signature: _______________________________

·Print Name: Greg Murphy___________________

·Title: ____________________________________

·M3TER US SERVICES INC.

·Signature: _______________________________

·Print Name: Greg Murphy___________________ COO

·Title: ____________________________________ COO

·Date: 8/6/2026_____________________________

Schedule 1SCHEDULE 1 - TRANSFER MECHANISMS FOR EUROPEAN DATA TRANSFERS

11. ADDITIONAL TERMS FOR BCR SERVICES

• 1.11.1. Instructions and Notices. Where Customer acts as a Processor under the instructions of the relevant Controller of Personal Data, Customer acknowledges and accepts that the commitments contained in the Salesforce Processor BCR are for the benefit of the ultimate Controller. Customer is responsible for ensuring that its Processing instructions as set out in the Agreement and this DPA, including its authorizations to SFDC for the appointment of Sub-processors in accordance with this DPA, have been authorized by the relevant Controller. Customer shall also be solely responsible for forwarding any notifications received from SFDC to the relevant Controller where appropriate.
• 1.21.2. Audits of the BCR Services. The Parties agree that the audits of BCR Services described in the BCR shall be carried out in accordance with section 6.3 of the DPA.
• 1.31.3. Reference to the Salesforce Processor BCR. All provisions contained in the Salesforce Processor BCR, the most current versions which are available on SFDC's website, currently located at https://www.salesforce.com/company/privacy are incorporated by reference and are an integral part of this DPA.
• 1.41.4. Liability. In accordance with the Agreement, Customer shall have the right to enforce the Salesforce Processor BCR against the SFDC Group, including judicial remedies and the right to receive compensation.
• 1.51.5. Conflict. In the event of any conflict or inconsistency between this DPA and the Salesforce Processor BCR, the Salesforce Processor BCR shall prevail.

22. STANDARD CONTRACTUAL CLAUSES OPERATIVE PROVISIONS AND ADDITIONAL TERMS

·For the purposes of SCC Module 2 and SCC Module 3, Customer is the data exporter and Salesforce, Inc. ("SFDC Inc") is the data importer. Where the SFDC entity that is a party to this DPA is not SFDC Inc, that SFDC entity acts as the data importer on behalf of SFDC Inc. Where this section 2 does not explicitly mention SCC Module 2 or SCC Module 3 it applies to both of them.

• 2.12.1. Reference to the Standard Contractual Clauses. The relevant provisions contained in the Standard Contractual Clauses are incorporated by reference and are an integral part of this DPA, and signature of the Agreement or amendment containing the DPA will be deemed to constitute signature of the SCCs. The information required for the purposes of the Appendix to the Standard Contractual Clauses are set out in Schedule 2. Where Customer wishes to separately sign the SCCs and its Appendix, Customer should also complete the information as the data exporter and sign on page 17 (Schedule 2).
• 2.22.2. Docking Clause. The option under clause 7 shall not apply.
• 2.32.3. Instructions. This DPA and the Agreement are Customer's complete and final documented instructions at the time of signature of the Agreement to SFDC for the Processing of Personal Data. Any additional or alternate instructions must be consistent with the terms of this DPA and the Agreement. For clause 8.1(a), the instructions by Customer to Process Personal Data are set out in section 2.2 of this DPA and include onward transfers to a third party located outside Europe for the purpose of the performance of the Services.
• 2.42.4. Certification of Deletion. The parties agree that the certification of deletion of Personal Data that is described in clause 8.5 and 16(d) of the Standard Contractual Clauses shall be provided by SFDC to Customer only upon Customer's written request.
• 2.52.5. Security of Processing. For clause 8.6(a), Customer is responsible for making an independent determination as to whether the technical and organizational measures set forth in the Security, Privacy and Architecture Documentation meet Customer's requirements 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 its Personal Data as well as the risks to individuals) the security measures and policies implemented and maintained by SFDC provide a level of security appropriate to the risk with respect to its Personal Data. For clause 8.6(c), personal data breaches will be handled in accordance with section 7 (Customer Data Incident Management and Notification) of this DPA.
• 2.62.6. Audits of the SCCs. The parties agree that the audits described in clause 8.9 of the Standard Contractual Clauses shall be carried out in accordance with section 6.3 of this DPA.
• 2.72.7. General Authorization for Use of Sub-processors. Option 2 under clause 9 shall apply. For clause 9(a), SFDC has Customer's general authorization to engage Sub-processors in accordance with section 5 of this DPA. SFDC shall make available to Customer the current list of Sub-processors in accordance with section 5.2 of this DPA.
• 2.82.8. Notification of New Sub-processors and Objection Right for New Sub-processors. For clause 9(a), Customer acknowledges and expressly agrees that SFDC may engage new Sub-processors as described in sections 5.2 and 5.3 of this DPA. SFDC shall inform Customer of any changes to Sub-processors following the procedure provided for in section 5.2 of this DPA.
• 2.92.9. Complaints - Redress. For clause 11, and subject to section 3 of this DPA, SFDC shall inform data subjects on its website of a contact point authorized to handle complaints. SFDC shall inform Customer if it receives a complaint by, or a dispute from, a Data Subject with respect to Personal Data and shall without undue delay communicate the complaint or dispute to Customer. SFDC shall not otherwise have any obligation to handle the request (unless otherwise agreed with Customer). The option under clause 11 shall not apply.
• 2.102.10. Supervision. Clause 13 shall apply as follows:
• 2.10.12.10.1. Where Customer is established in an EU Member State, the supervisory authority with responsibility under the GDPR for Customer's data transfers shall act as competent supervisory authority.
• 2.10.22.10.2. Where Customer is not established in an EU Member State, but falls within the territorial scope of GDPR Article 3(2) and has appointed a representative under GDPR Article 27(1), the supervisory authority of the Member State in which that Customer representative is established shall act as competent supervisory authority.
• 2.10.32.10.3. Where Customer is not established in an EU Member State, but falls within the territorial scope of GDPR Article 3(2) without having to appoint a representative under Article 27(2), Commission nationale de l'informatique et des libertés shall act as competent supervisory authority.
• 2.10.42.10.4. Where Customer is established in the United Kingdom or falls within the territorial scope of application of the Data Protection Laws and Regulations of the United Kingdom ("UK Data Protection Laws and Regulations"), the Information Commissioner's Office shall act as competent supervisory authority.
• 2.10.52.10.5. Where Customer is established in Switzerland or falls within the territorial scope of application of the Data Protection Laws and Regulations of Switzerland ("Swiss Data Protection Laws and Regulations"), the Swiss Federal Data Protection and Information Commissioner shall act as competent supervisory authority insofar as the relevant data transfer is governed by Swiss Data Protection Laws and Regulations.
• 2.112.11. Notification of Government Access Requests. For clause 15(1)(a), SFDC shall notify Customer (only) and not the Data Subject(s) in case of government access requests. Customer shall be solely responsible for promptly notifying the Data Subject as necessary.
• 2.122.12. Governing Law. The governing law for clause 17 shall be the law that is designated in the Governing Law section of the Agreement. If the Agreement is not governed by an EU Member State law, the Standard Contractual Clauses will be governed by either (i) the laws of France; or (ii) where the Agreement is governed by the laws of the United Kingdom, the laws of England and Wales.
• 2.132.13. Choice of Forum and Jurisdiction. The courts under clause 18 shall be those designated in the Venue section of the Agreement. If the Agreement does not designate an EU Member State court, then exclusive jurisdiction shall be in either (i) France; or (ii) where the Agreement designates the United Kingdom as having exclusive jurisdiction, the courts of England and Wales. For Data Subjects habitually resident in Switzerland, the courts of Switzerland are an alternative place of jurisdiction.
• 2.142.14. Appendix. The Appendix shall be completed as follows:
• 12The contents of section 1 of Schedule 2 shall form Annex I.A to the Standard Contractual Clauses
• 13The contents of sections 2 to 9 of Schedule 2 shall form Annex I.B to the Standard Contractual Clauses
• 14The contents of section 10 of Schedule 2 shall form Annex I.C to the Standard Contractual Clauses
• 15The contents of section 11 of Schedule 2 to this Exhibit shall form Annex II to the Standard Contractual Clauses.
• 2.152.15. Data Exports from the United Kingdom under the Standard Contractual Clauses. For data transfers governed by UK Data Protection Laws and Regulations, the UK International Data Transfer Addendum to the EU Commission Standard Contractual Clauses (available here) ("Approved Addendum") shall apply. The information required for Tables 1 to 3 of Part One of the Approved Addendum is in Schedule 2 of this DPA. For Table 4 of Part One of the Approved Addendum, neither party may end the Approved Addendum when it changes.
• 2.162.16. Data Exports from Switzerland under the Standard Contractual Clauses. For data transfers governed by Swiss Data Protection Laws, general and specific references in the Standard Contractual Clauses to GDPR or EU or Member State Law shall have the same meaning as the equivalent reference in Swiss Data Protection Laws.
• 2.172.17. Conflict. The Standard Contractual Clauses are subject to this DPA and the additional safeguards set out hereunder. The rights and obligations afforded by the Standard Contractual Clauses will be exercised in accordance with this DPA, unless stated otherwise. If the body of this DPA is inconsistent with the Standard Contractual Clauses, the Standard Contractual Clauses shall prevail.

33. ADDITIONAL TERMS FOR SCC MODULE 3

·For the purposes of SCC Module 3 only, the Parties agree the following.

• 3.13.1. Instructions and Notifications. For clause 8.1(a), Customer informs SFDC that it acts as Processor under the instructions of the relevant Controller. Customer warrants that its Processing instructions, including in the Agreement and this DPA have been authorized by the relevant Controller. Customer shall be solely responsible for forwarding any notifications received from SFDC to the relevant Controller where appropriate.
• 3.23.2. Security of Processing. For clause 8.6(c) and (d), SFDC shall notify Customer of a personal data breach concerning Personal Data Processed by SFDC.
• 3.33.3. Documentation and Compliance. For clause 8.9, all enquiries from the relevant Controller shall be provided to SFDC by Customer. If SFDC receives an enquiry directly from a Controller, it shall forward the enquiry to Customer and Customer shall be solely responsible for any response to the relevant Controller.
• 3.43.4. Data Subject Rights. For clause 10 and subject to section 3 of this DPA, SFDC shall notify Customer about any request it has received directly from a Data Subject without obligation to handle it (unless otherwise agreed), but shall not notify the relevant Controller. Customer shall be solely responsible for cooperating with the relevant Controller in fulfilling any obligations to respond to any such request.

Schedule 2SCHEDULE 2 - DESCRIPTION OF PROCESSING/TRANSFER

11. LIST OF PARTIES

·Data exporter(s): Identity and contact details of the data exporter(s) and, where applicable, of its/their data protection officer and/or representative in the European Union

·Name: Customer.

·Address:

·Contact person's name, position and contact details:

·Activities relevant to the data transferred under these clauses: Performance of the Services under the Agreement and as further described in the Documentation.

·Signature and date:

·__________________________________________________________

·Role: For the purposes of SCC Module 2 Customer is a Controller. For the purposes of SCC Module 3 Customer is a Processor.

·Data importer(s): Identity and contact details of the data importer(s), including any contact person with responsibility for data protection

·Name: Salesforce, Inc.

·Address: Salesforce Tower, 415 Mission Street, 3rd Floor, San Francisco, CA 94105, USA

·Contact person's name, position and contact details: Lindsey Finch, DPO, privacy@salesforce.com

·Activities relevant to the data transferred under these clauses: Performance of the Services under the Agreement and as further described in the Documentation.

·Signature and date: Role: Processor

22. CATEGORIES OF DATA SUBJECTS WHOSE PERSONAL DATA IS TRANSFERRED

·Customer may submit Personal Data to the Services, the extent of which is determined and controlled by Customer in its sole discretion, and which may include, but is not limited to Personal Data relating to the following categories of data subjects:

• ·Prospects, customers, business partners and vendors of Customer (who are natural persons)
• ·Employees or contact persons of Customer's prospects, customers, business partners and vendors
• ·Employees, agents, advisors, freelancers of Customer (who are natural persons)
• ·Customer's Users authorized by Customer to use the Services

33. CATEGORIES OF PERSONAL DATA TRANSFERRED

·Customer may submit Personal Data to the Services, the extent of which is determined and controlled by Customer in its sole discretion, and which may include, but is not limited to the following categories of Personal Data: First and last name Title Position Employer

• ·Contact information (company, email, phone, physical business address) ID data Professional life data Personal life data Location data

44. SENSITIVE DATA TRANSFERRED

·Sensitive data transferred (if applicable) and applied restrictions or safeguards that fully take into consideration the nature of the data and the risks involved, such as for instance strict purpose limitation, access restrictions (including access only for staff having followed specialised training), keeping a record of access to the data, restrictions for onward transfers or additional security measures:

·Customer may submit special categories of data to the Services, the extent of which is determined and controlled by Customer in its sole discretion, and which may include information revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade-union membership, and the processing of genetic data, biometric data for the purpose of uniquely identifying a natural person, data concerning health or data concerning a natural person's sex life or sexual orientation.

·The applicable security measures are described under the Security, Privacy and Architecture Documentation for the Services purchased by Customer, as updated from time to time, and accessible via SFDC's Trust and Compliance webpage or as otherwise made reasonably available by SFDC.

55. FREQUENCY OF THE TRANSFER

·The frequency of the transfer (e.g. whether the data is transferred on a one-off or continuous basis): Continuous basis depending on the use of the Services by Customer.

66. NATURE OF THE PROCESSING

·The nature of the Processing is the performance of the Services under the Agreement.

77. PURPOSE OF PROCESSING, THE DATA TRANSFER AND FURTHER PROCESSING

·SFDC will Process Personal Data as necessary to perform the Services under the Agreement, as further specified in the Documentation, and as further instructed by Customer in its use of the Services.

88. DURATION OF PROCESSING

·The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period:

·Subject to section 9 of the DPA, SFDC will Process Personal Data for the duration of the Agreement, unless otherwise agreed upon in writing.

99. SUB-PROCESSOR TRANSFERS

·For transfers to (sub-) processors, also specify subject matter, nature and duration of the processing:

·As per 7 above, the Sub-processor will Process Personal Data as necessary to perform the Services under the Agreement. Subject to section 9 of this DPA, the Sub-processor will Process Personal Data for the duration of the Agreement, unless otherwise agreed in writing.

·Identities of Sub-processors and their locations are listed under the Infrastructure and Sub-processor Documentation which can be found on SFDC's Trust and Compliance webpage.

1010. COMPETENT SUPERVISORY AUTHORITY

·Identify the competent supervisory authority/ies in accordance with clause 13: the supervisory authority specified in section 2.10 of Schedule 1 shall act as the competent supervisory authority for the Standard Contractual Clauses.

1111. TECHNICAL AND ORGANISATIONAL MEASURES

·SFDC will maintain administrative, physical, and technical safeguards for protection of the security, confidentiality and integrity of Personal Data uploaded to the Services, as described in the Security, Privacy and Architecture Documentation for the Services purchased by Customer. SFDC will not materially decrease the overall security of the Services during a subscription term.