Rush Data Processing Agreement

Updated: Jun 21, 2022


(A) Customer (“Customer”) has entered into an agreement with Rush, Inc. (“Rush”) (each a “Party” and collectively the “Parties”) under which Rush has agreed to provide the Services in accordance with such agreement (the “Agreement”). This Data Processing Agreement (the “DPA”) is incorporated into and forms part of the Agreement and shall be effective and replace any previously applicable data processing and security terms as of the effective date of the Agreement (“Effective Date”).

(B) To the extent that Rush processes any Customer Personal Data (as defined below) on behalf of the Customer (or, where applicable, the Customer Affiliate) in connection with the provision of the Services, the Parties have agreed that it shall do so on the terms of this DPA.


1.1 Capitalized terms used but not defined within this DPA shall have the meaning set forth in the Agreement. The following capitalized terms used in this DPA shall be defined as follows:

“Affiliate” means an entity that, directly or indirectly, owns or controls, is owned or is controlled by, or is under common ownership or control with a Party and is a beneficiary of the Agreement;

“Approved Addendum” means the template addendum, version B.1.0 issued by the UK Information Commissioner under S119A(1) Data Protection Act 2018 and laid before the UK Parliament on 2 February 2022, as it may be revised according to Section 18 of the Mandatory Clauses;

“CCPA” means the California Consumer Privacy Act, Cal. Civ. Code §§ 1798.100 et seq., including any amendments and any implementing regulations thereto that become effective on or after the Effective Date of this DPA;

“Customer Personal Data” means the Personal Data processed by Rush on behalf of Customer or Customer Affiliate in connection with the provision of the Services;

“EEA” means the European Economic Area;

“GDPR” means Regulation (EU) 2016/679 (the “EU GDPR”) or, where applicable, the “UK GDPR” as it forms part of the law of England and Wales, Scotland and Northern Ireland by virtue of section 3 of the UK European Union (Withdrawal) Act 2018 or, where applicable, the equivalent provision under Swiss data protection law;

“Mandatory Clauses“ means “Part 2: Mandatory Clauses” of the Approved Addendum;

“Member State” means a member state of the EEA, being a member state of the European Union, Iceland, Norway, or Liechtenstein;

“Personal Data” means any information relating to an identified or identifiable individual or device, or is otherwise “personal data,” “personal information,” “personally identifiable information” and similar terms, and such terms shall have the same meaning as defined by applicable data protection laws;

“Security Incident” means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorized disclosure of, or unauthorized access to (including unauthorized internal access to), Customer Personal Data;

“Standard Contractual Clauses” or “SCCs” means Module Two (controller to processor) and/or Module Three (processor to processor) of the Standard Contractual Clauses annexed to Commission Implementing Decision (EU) 2021/914;

“Sub-processor” means Rush Affiliates and third-party processors appointed by Rush to process Customer Personal Data; and

“UK“ means the United Kingdom of Great Britain and Northern Ireland.

1.2 The terms “ controller“, “ processor“, “ data subject“, “ process“, and “ supervisory authority” shall have the same meaning as set out in the GDPR.

1.3 The terms “sell” and “service provider” shall have the same meaning as set out in the CCPA.


2.1 This DPA supplements and (in case of contradictions) supersedes the Agreement with respect to any processing of Customer Personal Data.

2.2 With respect to Customer Affiliates, by entering into the Agreement Customer warrants it is duly authorised to enter into the DPA for and on behalf of any such Customer Affiliates and, subject to clause 2.3, each Customer Affiliate shall be bound by the terms of this DPA as if they were the Customer.

2.3 Customer warrants that it is duly mandated by any Customer Affiliates on whose behalf Rush processes Customer Personal Data in accordance with this DPA to (a) enforce the terms of this DPA on behalf of the Customer Affiliates, and to act on behalf of the Customer Affiliates in the administration and conduct of any claims arising in connection with this DPA; and (b) receive and respond to any notices or communications under this DPA on behalf of Customer Affiliates.

2.4 The Parties agree that any notice or communication sent by Rush to Customer shall satisfy any obligation to send such notice or communication to a Customer Affiliate.


3.1 The Parties acknowledge and agree that:

 (a) for the purposes of the GDPR, Rush acts as “processor” or “sub-processor.” Rush’s function as processor or sub-processor will be determined by the function of Customer:

  (I) In general, Customer functions as a controller, whereas Rush functions as a processor.

  (II) In certain cases, Customer functions as a processor on behalf of Customer’s customers where Customer and Customer’s customer have concluded a data processing agreement in relation to the processing of Personal Data of Customer’s customers; and

 (b) for the purposes of the CCPA, Rush will act as a “service provider” in its performance of its obligations pursuant to the Agreement.


4.1 The details of data processing (such as subject matter, nature and purpose of the processing, categories of Personal Data and data subjects) are described in the Agreement and in Schedule 1.

4.2 Customer Personal Data will only be processed on behalf of and under the instructions of Customer and in accordance with applicable law. The Agreement and this DPA shall be Customer’s instructions for the processing of Customer Personal Data.

4.3 If Customer’s instructions will cause Rush to process Customer Personal Data in violation of applicable law or outside the scope of the Agreement or the DPA, Rush shall promptly inform Customer thereof, unless prohibited by applicable law (without prejudice to the SCCs).

4.4 Rush is permitted to anonymize Customer Personal Data through a reliable state of the art anonymization procedure and use such anonymized data for its own business purposes, including for research, development of new products and services, and security purposes.

4.5 Rush may store and process Customer Personal Data anywhere Rush or its Sub-processors maintain facilities, subject to clause 5 of this DPA.


5.1 Customer grants Rush general authorisation to engage Sub-processors, subject to clause 5.2, from an agreed list, as well as Rush’s current Sub-processors listed at as of the Effective Date.

5.2 Rush shall (i) enter into a written agreement with each Sub-processor imposing data protection obligations no less protective of Customer Personal Data than Rush’s obligations under this DPA to the extent applicable to the nature of the services provided by such Sub-processor; and (ii) remain liable for each Sub-processor’s compliance with the obligations under this DPA.

5.3 Rush shall provide Customer with at least fifteen (15) days’ notice of any proposed changes to the Sub-processors it uses to process Customer Personal Data (including any addition or replacement of any Sub-processors). Customer may object to Rush’s use of a new Sub-processor (including when exercising its right to object under clause 9(a) of the SCCs) by providing Rush with written notice of the objection within ten (10) days after Rush has provided notice to Customer of such proposed change (an “ Objection“). In the event Customer objects to Rush’s use of a new Sub-processor, Customer and Rush will work together in good faith to find a mutually acceptable resolution to address such Objection. If the parties are unable to reach a mutually acceptable resolution within a reasonable timeframe, either party may, as its sole and exclusive remedy, terminate the Agreement by providing written notice to the other party. During any such Objection period, Rush may suspend the affected portion of the Services.


6.1 As between the Parties, Customer shall have sole discretion and responsibility in responding to the rights asserted by any individual in relation to Customer Personal Data (“Data Subject Request”).

6.2 Rush will forward to Customer without undue delay any Data Subject Request received by Rush or any Sub-processor from an individual in relation to their Customer Personal Data and may advise the individual to submit their request directly to Customer.

6.3 Rush will (taking into account the nature of the processing of Customer Personal Data) provide Customer with self-service functionality through the Services or other reasonable assistance as necessary for Customer to fulfil its obligation under applicable law to respond to Data Subject Requests, including if applicable, Customer’s obligation to respond to requests for exercising the rights set out in the GDPR or CCPA. Rush may charge Customer, and Customer shall reimburse Rush, for any such assistance beyond providing self-service features included as part of the Services.


7.1 Rush will implement and maintain appropriate technical and organizational data protection and security measures designed to ensure security of Customer Personal Data, including, without limitation, protection against unauthorized or unlawful processing (including, without limitation, unauthorized or unlawful disclosure of, access to and/or alteration of Customer Personal Data) and against accidental loss, destruction, or damage of or to it.

7.2 Rush will implement and maintain as a minimum standard the measures set out in Schedule 2. Rush may update or modify the security measures set out in Schedule 2 from time to time, including (where applicable) following any review by Rush of such measures in accordance with clause 8.6 of the SCCs, provided that such updates and/or modifications do not reduce the overall level of protection afforded to the Customer Personal Data by Rush under this DPA.

7.3 Customer or its independent third-party auditor reasonably acceptable to Rush (which shall not include any auditors who are not suitably qualified or independent or are a competitor of Rush) may audit Rush’s compliance with its obligations under this DPA up to once per year, or more frequently in the event a Security Incident has occurred or to the extent required by applicable data protection laws, including where mandated by Customer’s regulatory or governmental authority.

7.4 To request an audit, Customer must submit a detailed proposed audit plan to Rush at least two weeks in advance of the proposed audit date. Rush will review the proposed audit plan and work cooperatively with Customer to agree on a final audit plan. All such audits must be conducted during regular business hours, subject to the agreed final audit plan and Rush’s health and safety or other relevant policies, and may not unreasonably interfere with Rush business activities. Nothing in this clause 7.4 shall require Rush to breach any duties of confidentiality.

7.5 If the requested audit scope is addressed in an ISO 27001 certification, SOC 2 Type 2 report or similar audit report performed by a qualified third-party auditor within twelve (12) months of Customer’s audit request and Rush confirms there are no known material changes in the controls audited, Customer agrees to accept those findings in lieu of requesting an audit of the controls covered by the report.

7.6 Customer will promptly notify Rush of any non-compliance discovered during the course of an audit and provide Rush any audit reports generated in connection with any audit, unless prohibited by applicable law or otherwise instructed by a regulatory or governmental authority. Customer may use the audit reports only for the purposes of meeting Customer’s regulatory audit requirements and/or confirming compliance with the requirements of this DPA.

7.7 Any audits are at Customer’s expense. Customer shall reimburse Rush for any time expended by Rush or its Sub-processors in connection with such audits.

7.8 Rush shall audit its Sub-processors on a regular basis and will, upon Customer’s request, confirm their compliance with data protection law and the obligations set upon Sub-processors according to the data processing agreement concluded with them. Customer may request Rush to conduct further audits only in the event reasonably justified, and in such cases Rush will conduct further audits to the extent permissible.


Rush will promptly notify Customer in writing in the event of any breach of this DPA, applicable law or any instruction by Customer in connection with the processing of Customer Personal Data under this DPA. Without limiting the generality of the foregoing, Rush shall notify Customer in writing without undue delay after becoming aware of any Security Incident, and reasonably cooperate in the investigation of any such Security Incident and any obligation of Customer under applicable law to make any notifications to individuals, supervisory authorities, governmental or other regulatory authority, or the public in respect of such Security Incident. Rush shall take reasonable steps to contain, investigate, and mitigate any Security Incident, and shall, without undue delay, send Customer timely information about the Security Incident, including, but not limited to, the nature of the Security Incident, the measures taken to mitigate or contain the Security Incident, and the status of the investigation. Rush’s notification of or response to a Security Incident under this clause 8 will not be construed as an acknowledgement by Rush of any fault or liability with respect to the Security Incident.


Rush shall, within 90 days of the date of termination or expiry of the Agreement, (a) if requested to do so by Customer within that period, return a copy of all Customer Personal Data or provide self-service functionality allowing Customer to do the same; and (b) delete and use all reasonable efforts to procure the deletion of all other copies of Customer Personal Data processed by Rush or any Sub-processors.


This DPA will commence on the Effective Date and, notwithstanding any termination of the Agreement, will remain in effect until, and automatically expire upon, Rush’s deletion of all Customer Personal Data as described in this DPA.


The Parties agree that the terms of the Standard Contractual Clauses Module Two (Controller to Processor) and Module Three (Processor to Processor), as further specified in Schedule 3 of this DPA, are hereby incorporated by reference and shall be deemed to have been executed by the Parties and apply to any transfers of Customer Personal Data falling within the scope of the GDPR from Customer (as data exporter) to Rush (as data importer).


Rush will provide Customer reasonable support to enable Customer’s compliance with the requirements imposed on the transfer of personal data to third countries with respect to data subjects located in the EEA, Switzerland, and UK. Rush will, upon Customer’s request, provide information to Customer which is reasonably necessary for Customer to complete a transfer impact assessment (“ TIA“). Rush further agrees to implement the supplementary measures agreed upon and set forth in Schedule 4 of this DPA in order to enable Customer’s compliance with requirements imposed on the transfer of personal data to third countries. Rush may charge Customer, and Customer shall reimburse Rush, for any assistance provided by Rush with respect to any TIAs, data protection impact assessments or consultation with any supervisory authority of Customer.


To the extent that the processing of Customer Personal Data is subject to UK or Swiss data protection laws, the UK Addendum and/or Swiss Addendum (as applicable) set out in Schedule 5 shall apply.


14.1 If Customer or Customer Affiliates provide Rush any Customer Personal Data that is “personal information” under the CCPA, Rush will:

 (a) act as a service provider with regard to such personal information;

 (b) retain, use, and disclose such personal information solely for the purpose of performing the Services or as otherwise permitted under the CCPA;

 (c) not sell Customer Personal Data to another business or third party. Notwithstanding the foregoing, disclosures to a third party in the context of a merger, acquisition, bankruptcy, or other transaction shall be permitted in accordance with the terms of the Agreement; and

 (d) provide reasonable assistance to Customer in responding to requests from consumers pursuant to the CCPA with regard to their personal information, and in accordance with clause 6 of this DPA.

14.2 Rush certifies that it understands the foregoing obligations and shall comply with them for the duration of the Agreement and for as long as Rush processes Customer Personal Data.



1. Data Exporter

Customer and/or the Customer Affiliates operating in the countries which comprise the European Economic Area, UK and/or Switzerland and/or – to the extent agreed by the Parties – Customer and/or the Customer Affiliates in any other country to the extent the GDPR or corresponding Swiss law applies.

Customer and Customer Affiliate’s contact person’s position and contact details as well as (if appointed) the data protection officer’s and (if relevant) the representative’s contact details will be notified to Rush prior to the processing of personal data via email to or an available form provided by Rush in Customer’s account in the Services.

The activities relevant to the data transfer under these Clauses are defined by the Agreement and the data exporter who decides on the scope of the processing of personal data in connection with the Services further described in this Schedule 1 and in the Agreement.

2. Data Importer

Rush Ltd, 13 Knyazhevska Str., block of flats Yuta, entr. B, fl. 2, apt. 14, city of Ruse, 7000, Bulgaria
The data importer’s contact person can be contacted at

The data importer’s activities relevant to the data transfer under these Clauses are as follows: the data importer processes personal data provided by the data exporter on behalf of the data exporter in connection with providing the Services to the data exporter as further specified in clause 7 and 8 of this Schedule 1 and in the Agreement.


3. Categories of data subjects

The categories of data subjects whose personal data are transferred: Employees of Customer and Customer Affiliates, as well as Customer’s customers and their employees, as well as the individual recipients of marketing communications and other individuals being targets of other marketing activities of the Customer and/or Customer Affiliates’ or their customers.

4. Categories of personal data

The transferred categories of personal data are: Determined by Customer’s configuration of the Services, and may include name, phone number, email address, address data, IP address, device identifiers, usage data (such as interactions between a user and Rush’s online system, website or email, used browser, used operating system, referrer URL).

Moreover, Customer and Customer Affiliate may include further personal data of data subjects as specified above (in particular in unstructured form) in connection with their use the Services according to the Agreement.

5. Special categories of personal data (if applicable)

The transferred personal data includes the following special categories of data: N/A – Rush’s Acceptable Use Policy prohibits Customer from using the Services to solicit, display, store, process, send or transmit special categories of data.

The 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 are: N/A

6. Frequency of the transfer

The frequency of the transfer is: The transfer is performed on a continuous basis and is determined by Customer’s configuration of the Services.

7. Subject matter and nature of the processing

The subject matter of the processing is: to provide a data analytics and marketing automation platform to Customer.

8. Purpose(s) of the data transfer and further processing

The purpose/s of the data transfer and further processing is: to provide the Services to Customer pursuant to the Agreement so that Customer can analyze customer data, enhance its customer relationships and send marketing and other communications to its customers.

9. Duration

The period for which the personal data will be retained, or, if that is not possible, the criteria used to determine that period: the duration is defined in clause 10 of the DPA.

10. Sub-processor (if applicable)

For transfers to sub-processors, specify subject matter, nature, and duration of the processing: as stipulated in clause 5.1 of the DPA. The Sub-processors may have access to the Personal Data for the term of this DPA or until the service contract with the respective Sub-processor is terminated or the access by the Sub-processor has been excluded as agreed between Rush and Customer.


Identify the competent supervisory authority/ies in accordance with clause 13 of the SCCs

Where the data exporter is established in an EU Member State: The supervisory authority of the country in which the data exporter established is the competent authority.

Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of the GDPR in accordance with its Article 3(2) and has appointed a representative pursuant to Article 27(1) of the GDPR: The competent supervisory authority is the one of the Member State in which the representative is established.

Where the data exporter is not established in an EU Member State, but falls within the territorial scope of application of the GDPR in accordance with its Article 3(2) without, however, having to appoint a representative pursuant to Article 27(2) of the GDPR: The competent supervisory authority is the supervisory authority in Ireland, namely the Data Protection Commission (


Rush has implemented the following technical and organizational measures (including any relevant certifications) to ensure an appropriate level of security, taking into account the nature, scope, context, and purpose of the processing, as well as the risks for the rights and freedoms of natural persons:

1) Organizational management and dedicated staff responsible for the development, implementation, and maintenance of Rush’s information security program.

2) Audit and risk assessment procedures for the purposes of periodic review and assessment of risks to Rush’s organization, monitoring and maintaining compliance with Rush’s policies and procedures, and reporting the condition of its information security and compliance to internal senior management.

3) Utilization of commercially available and industry standard encryption technologies for Customer Personal Data that is:

 a) being transmitted by Rush over public networks (i.e., the Internet) or when transmitted wirelessly; or

b) at rest or stored on portable or removable media (i.e., laptop computers, CD/DVD, USB drives, back-up tapes).

4) Data security controls which include at a minimum, but may not be limited to, logical segregation of data, logical access controls designed to manage electronic access to data and system functionality based on authority levels and job functions, (e.g., granting access on a need-to-know and least privilege basis, use of unique IDs and passwords for all users, periodic review, and revoking/changing access promptly when employment terminates or changes in job functions occur).

5) Password controls designed to manage and control password strength, expiration and usage including prohibiting users from sharing passwords and requiring that Rush’s passwords that are assigned to its employees: (i) be at least eight (8) characters in length, (ii) not be stored in readable format on Rush’s computer systems; (iii) must have defined complexity; (iv) must have a history threshold to prevent reuse of recent passwords; and (v) newly issued passwords must be changed after first use.

6) System audit or event logging and related monitoring procedures to proactively record user access and system activity for routine review.

7) Physical and environmental security of data center, server room facilities and other areas containing Personal Data designed to: (i) protect information assets from unauthorized physical access, (ii) manage, monitor, and log movement of persons into and out of Rush facilities, and (iii) guard against environmental hazards such as heat, fire, and water damage.

8) Operational procedures and controls to provide for configuration, monitoring and maintenance of technology and information systems according to prescribed internal and adopted industry standards, including secure disposal of systems and media to render all information or data contained therein as undecipherable or unrecoverable prior to final disposal or release from Rush’s possession.

9) Change management procedures and tracking mechanisms designed to test, approve, and monitor all changes to Rush’s technology and information assets.

10) Incident / problem management procedures design to allow Rush to investigate, respond to, mitigate, and notify of events related to Rush’s technology and information assets.

11) Network security controls that provide for the use of firewall systems, and intrusion detection systems and other traffic and event correlation procedures designed to protect systems from intrusion and limit the scope of any successful attack.

12) Vulnerability assessment, patch management and threat protection technologies and scheduled monitoring procedures designed to identify, assess, mitigate, and protect against identified security threats, viruses, and other malicious code.

13) Business resiliency/continuity and disaster recovery procedures in an effort to maintain service and/or recovery from foreseeable emergency situations or disasters.


For the purposes of the Standard Contractual Clauses:

1) Module Two shall apply in the case of the processing under clause 3.1(a)(i) of the DPA and Module Three shall apply in the case of processing under clause 3.1(a)(ii) of the DPA.

2) Clause 7 of the Standard Contractual Clauses (Docking Clause) does not apply.

3) Clause 9(a) Option 2 (General written authorization) is selected, and the time period to be specified is determined in clause 5.3 of the DPA.

4) The option in Clause 11(a) of the Standard Contractual Clauses (Independent dispute resolution body) does not apply.

5) With regard to Clause 17 of the Standard Contractual Clauses (Governing law), the Parties agree that option one shall apply. The parties agree that the governing law shall be the law of the Republic of Ireland.

6) In Clause 18 of the Standard Contractual Clauses (Choice of forum and jurisdiction), the Parties submit themselves to the jurisdiction of the courts of the Republic of Ireland.

7) For the Purpose of Annex I of the Standard Contractual Clauses, Schedule 1 contains the specifications regarding the parties, the description of transfer, and the competent supervisory authority.

8) For the Purpose of Annex II of the Standard Contractual Clauses, Schedule 2 contains the technical and organizational measures.

9) The specifications for Annex III of the Standard Contractual Clauses, are determined by clause 5.1 of the DPA. The Sub-processor’s contact person’s name, position and contact details will be provided by Rush upon request.


Rush further commits to implementing supplementary measures based on guidance provided by EU supervisory authorities in order to enhance the protection of Customer Personal Data in relation to the processing in a third country, as described in this Schedule 4.

1. Additional Technical Measures (Encryption)

1.1 The personal data is transmitted (between the Parties and by Rush between data centers as well as to a Sub-processor and back) using strong encryption.

1.2 The personal data at rest is stored by Rush using strong encryption

2. Additional Organizational Measures

2.1Internal policies for governance of transfers especially with groups of enterprises

 (a) Adoption of adequate internal policies with clear allocation of responsibilities for data transfers, reporting channels and standard operating procedures for cases of formal or informal requests from public authorities to access the data.

 (b) Development of specific training procedures for personnel in charge of managing requests for access to personal data from public authorities, which should be periodically updated to reflect new legislative and jurisprudential developments in the third country and in the EEA.

2.2Transparency and accountability measures

Regular publication of transparency reports or summaries regarding governmental requests for access to data and the kind of reply provided, insofar publication is allowed by local law.

2.3Organizational methods and data minimization measures

Development and implementation of best practices by both Parties to appropriately and timely involve and provide access of information to their respective data protection officers, if existent, and to their legal and internal auditing services on matters related to international transfers of personal data transfers.


Adoption and regular review by Rush of internal policies to assess the suitability of the implemented complementary measures and identify and implement additional or alternative solutions when necessary, to ensure that an essentially equivalent level of protection to that guaranteed within the EEA of the personal data transferred is maintained.

3Additional Contractual Measures

3.1Transparency obligations

 (a) Rush declares that (1) it has not purposefully created back doors or similar programming that could be used to access the system and/or personal data, (2) it has not purposefully created or changed its business processes in a manner that facilitates access to personal data or systems, and (3) that national law or government policy does not require Rush to create or maintain back doors or to facilitate access to personal data or systems or for Rush to be in possession or to hand over the encryption key.

 (b) Rush will verify the validity of the information provided for the TIA questionnaire on a regular basis and provide notice to Customer in case of any changes without delay. Clause 14(e) of the SCCs shall remain unaffected.

3.2Obligations to take specific actions

In case of any order to disclose or to grant access to the personal data, Rush commits to inform the requesting public authority of the incompatibility of the order with the safeguards contained in the Article 46 GDPR transfer tool and the resulting conflict of obligations for Rush.

3.3Empowering data subjects to exercise their rights

 (a) Rush commits to fairly compensate the data subject for any material and non-material damage suffered because of the disclosure of his/her personal data transferred under the chosen transfer tool in violation of the commitments it contains.

 (b) Notwithstanding the foregoing, Rush shall have no obligation to indemnify the data subject to the extent the data subject has already received compensation for the same damage.

 (c) Compensation is limited to material and non-material damages as provided in the GDPR and excludes consequential damages and all other damages not resulting from Rush’s infringement of the GDPR.

4.Additional obligations in case of requests or access by public authorities

4.1 Rush shall promptly inform Customer:

 (a) Of any legally binding requests from a law enforcement or other government authority (“Public Authority”) to disclose the personal data shared by Customer (“Transferred Personal Data”); such notification shall include information about the personal data requested, the requesting authority, the legal basis for the request and the response provided. Such notification shall occur prior to the disclosure of any personal data in response to such requests.

 (b) If it becomes aware of any direct access by public authorities to transferred personal data in accordance with the laws of the country of destination, such notification shall include all information available to Rush.

 (c) If Rush is prohibited from notifying Customer and/or the data subject, Rush agrees to use its best efforts to obtain a waiver of the prohibition, with a view to communicate as much information and as soon as possible. Rush agrees to document its best efforts in order to be able to demonstrate them upon request of the data exporter.

4.2 Rush agrees to review, under the laws of the country of destination, the legality of the public authority’s request, notably whether it remains within the powers granted to the requesting public authority and exhaust all available remedies to challenge the request if, after a careful assessment, Rush concludes that there are grounds under the laws of the country of destination to do so. This includes requests under section 702 of the United States Foreign Intelligence Surveillance Court (“FISA”). When challenging a request, Rush shall seek interim measures with a view to suspend the effects of the request until the court has decided on the merits. Rush shall not disclose or provide access to the personal data requested until required to do so under the applicable procedural rules and, at such time, shall provide only the minimum amount of information required to comply with the request, based on a reasonable interpretation of the request.

4.3 Rush agrees to preserve the information required to comply with this Schedule 4 for the duration of the Agreement and, unless prohibited by applicable law, make it available to the competent supervisory authority upon request and when required by applicable law.



With respect to any transfers of Customer Personal Data falling within the scope of the UK GDPR from Customer (as data exporter) to Rush (as data importer):

1.1 The Approved Addendum as further specified in this Schedule 5 shall form part of this DPA, and the Standard Contractual Clauses shall be read and interpreted in light of the provisions of the Approved Addendum, to the extent necessary according to Clause 12 of the Mandatory Clauses.

1.2 In deviation to Table 1 of the Approved Addendum and in accordance with Clause 16 of the Mandatory Clauses, the parties are further specified in Schedule 1 clause A of this DPA.

1.3 The selected Modules and Clauses to be determined according to Table 2 of the Approved Addendum are further specified in Schedule 3 of this DPA as amended by the Mandatory Clauses.

1.4 Annex 1 A and B of Table 3 to the Approved Addendum are specified by Schedule 1 of this DPA, Annex II of the Approved Addendum is further specified by Schedule 2 of this DPA, and Annex III of the Approved Addendum is further specified by Schedule 1 clause B.10 of this DPA.

1.5 Rush (as data importer) may end this DPA, to the extent the Approved Addendum applies, in accordance with clause ‎19 of the Mandatory Clauses.

1.6 Clause 16 of the Mandatory Clauses shall not apply.


As stipulated in clause 13 of the DPA, this Swiss Addendum shall apply to any processing of Customer Personal Data subject to Swiss data protection law or to both Swiss data protection law and the GDPR.

2.1 Interpretation of this Addendum

(a) Where this Addendum uses terms that are defined in the Standard Contractual Clauses as further specified in Schedule 3 of this DPA, those terms shall have the same meaning as in the Standard Contractual Clauses. In addition, the following terms have the following meanings:

 “This Addendum” means This Addendum to the Clauses.

 “Clauses” means The Standard Contractual Clauses as further specified in Schedule 3 of this DPA.

 “Swiss Data Protection Laws” means The Swiss Federal Act on Data Protection of 19 June 1992 and the Swiss Ordinance to the Swiss Federal Act on Data Protection of 14 June 1993, and any new or revised version of these laws that may enter into force from time to time.

(b) This Addendum shall be read and interpreted in the light of the provisions of Swiss Data Protection Laws, and so that if fulfils the intention for it to provide the appropriate safeguards as required by Article 46 GDPR and/or Article 6(2)(a) of the Swiss Data Protection Laws, as the case may be.

(c) This Addendum shall not be interpreted in a way that conflicts with rights and obligations provided for in Swiss Data Protection Laws.

(d) Any references to legislation (or specific provisions of legislation) means that legislation (or specific provision) as it may change over time. This includes where that legislation (or specific provision) has been consolidated, re-enacted and/or replaced after this Addendum has been entered into.

2.2 Hierarchy
In the event of a conflict or inconsistency between this Addendum and the provisions of the Clauses or other related agreements between the Parties, existing at the time this Addendum is agreed or entered into thereafter, the provisions which provide the most protection to data subjects shall prevail.

2.3 Incorporation of the Clauses

(a) In relation to any processing of personal data subject to Swiss Data Protection Laws or to both Swiss Data Protection Laws and the GDPR, this Addendum amends the DPA including as further specified in Schedule 3 of this DPA to the extent necessary so they operate:

 (I) for transfers made by the data exporter to the data importer, to the extent that Swiss Data Protection Laws or Swiss Data Protection Laws and the GDPR apply to the data exporter’s processing when making that transfer; and

 (II) to provide appropriate safeguards for the transfers in accordance with Article 46 of the GDPR and/or Article 6(2)(a) of the Swiss Data Protection Laws, as the case may be.

(b) To the extent that any processing of personal data is exclusively subject to Swiss Data Protection Laws, the amendments to the DPA including the SCCs, as further specified in Schedule 3 of this DPA and as required by clause 2.1 of this Swiss Addendum, include (without limitation):

 (I) References to the “Clauses” or the “SCCs” means this Swiss Addendum as it amends the SCCs and

 (II) Clause 6 Description of the transfer(s) is replaced with:
“The details of the transfer(s), and in particular the categories of personal data that are transferred and the purpose(s) for which they are transferred, are those specified in Schedule 1 of this DPA where Swiss Data Protection Laws apply to the data exporter’s processing when making that transfer.”

 (III) References to “Regulation (EU) 2016/679” or “that Regulation” or ““GDPR” are replaced by “Swiss Data Protection Laws” and references to specific Article(s) of “Regulation (EU) 2016/679” or “GDPR” are replaced with the equivalent Article or Section of Swiss Data Protection Laws extent applicable.

 (IV) References to Regulation (EU) 2018/1725 are removed.

 (V) References to the “European Union”, “Union”, “EU” and “EU Member State” are all replaced with “Switzerland”.

 (VI) Clause 13(a) and Part C of Annex I are not used; the “competent supervisory authority” is the Federal Data Protection and Information Commissioner (the “FDPIC”) insofar as the transfers are governed by Swiss Data Protection Laws;

 (VII) Clause 17 is replaced to state:
“These Clauses are governed by the laws of Switzerland insofar as the transfers are governed by Swiss Data Protection Laws”.

 (VIII) Clause 18 is replaced to state:
“Any dispute arising from these Clauses relating to Swiss Data Protection Laws shall be resolved by the courts of Switzerland. A data subject may also bring legal proceedings against the data exporter and/or data importer before the courts of Switzerland in which he/she has his/her habitual residence. The Parties agree to submit themselves to the jurisdiction of such courts.”

Until the entry into force of the revised Swiss Data Protection Laws, the Clauses shall also protect personal data of legal entities and legal entities shall receive the same protection under the Clauses as natural persons.

2.4 To the extent that any processing of personal data is subject to both Swiss Data Protection Laws and the GDPR, the DPA including the Clauses as further specified in Schedule 3 of this DPA will apply (i) as is and (ii) additionally, to the extent that a transfer is subject to Swiss Data Protection Laws, as amended by clauses 2.1 and 2.3 of this Swiss Addendum, with the sole exception that Clause 17 of the SCCs shall not be replaced as stipulated under clause 2.3(b)(vii) of this Swiss Addendum.

2.5 Customer warrants that it and/or Customer Affiliates have made any notifications to the FDPIC which are required under Swiss Data Protection Laws.