Data Processing Agreement
This Data Processing Agreement (“DPA”) governs the processing of personal data by Bend Technology, Inc. DBA Versa (“Provider”) on behalf of the customer entity that uses the Service (“Customer”). This DPA applies when Provider processes Customer Personal Data in connection with the Service.
By using the Service, Customer enters into this DPA on behalf of itself and, to the extent required under Applicable Data Protection Laws, in the name and on behalf of its authorized affiliates.
Processor and Subprocessor Relationships
Provider as Processor.
In situations where Customer is a Controller of the Customer Personal Data, Provider will be deemed a Processor that is Processing Personal Data on behalf of Customer.
Provider as Subprocessor.
In situations where Customer is a Processor of the Customer Personal Data, Provider will be deemed a Subprocessor of the Customer Personal Data.
Processing
Processing Details.
Annex I of this DPA describes the subject matter, nature, purpose, and duration of this Processing, as well as the Categories of Personal Data collected and Categories of Data Subjects.
Processing Instructions.
Customer instructs Provider to Process Customer Personal Data: (a) to provide and maintain the Service; (b) as may be further specified through Customer’s use of the Service; (c) as documented in any applicable service agreement between the parties; and (d) as documented in any other written instructions given by Customer and acknowledged by Provider about Processing Customer Personal Data under this DPA. Provider will abide by these instructions unless prohibited from doing so by Applicable Laws. Provider will immediately inform Customer if it is unable to follow the Processing instructions. Customer has given and will only give instructions that comply with Applicable Laws.
Processing by Provider.
Provider will only Process Customer Personal Data in accordance with this DPA, including the Annexes. If Provider updates the Service to update existing or include new products, features, or functionality, Provider may change the Categories of Data Subjects, Categories of Personal Data, Special Category Data, Special Category Data Restrictions or Safeguards, Frequency of Transfer, Nature and Purpose of Processing, and Duration of Processing as needed to reflect the updates by notifying Customer of the updates and changes.
Customer Processing.
Where Customer is a Processor and Provider is a Subprocessor, Customer will comply with all Applicable Laws that apply to Customer’s Processing of Customer Personal Data. Customer’s agreement with its Controller will similarly require Customer to comply with all Applicable Laws that apply to Customer as a Processor. In addition, Customer will comply with the Subprocessor requirements in Customer’s agreement with its Controller.
Consent to Processing.
Customer has complied with and will continue to comply with all Applicable Data Protection Laws concerning its provision of Customer Personal Data to Provider and/or the Service, including making all disclosures, obtaining all consents, providing adequate choice, and implementing relevant safeguards required under Applicable Data Protection Laws.
Subprocessors.
- Provider will not provide, transfer, or hand over any Customer Personal Data to a Subprocessor unless Customer has approved the Subprocessor. The current list of Approved Subprocessors includes the identities of the Subprocessors, their country of location, and their anticipated Processing tasks. Provider will inform Customer at least 10 business days in advance and in writing of any intended changes to the Approved Subprocessors whether by addition or replacement of a Subprocessor, which allows Customer to have enough time to object to the changes before Provider begins using the new Subprocessor(s). Provider will give Customer the information necessary to allow Customer to exercise its right to object to the change to Approved Subprocessors. Customer has 30 days after notice of a change to the Approved Subprocessors to object, otherwise Customer will be deemed to accept the changes. If Customer objects to the change within 30 days of notice, Customer and Provider will cooperate in good faith to resolve Customer’s objection or concern.
- When engaging a Subprocessor, Provider will have a written agreement with the Subprocessor that ensures the Subprocessor only accesses and uses Customer Personal Data (i) to the extent required to perform the obligations subcontracted to it, and (ii) consistent with the terms of this DPA.
- If the GDPR applies to the Processing of Customer Personal Data, (i) the data protection obligations described in this DPA (as referred to in Article 28(3) of the GDPR, if applicable) are also imposed on the Subprocessor, and (ii) Provider’s agreement with the Subprocessor will incorporate these obligations, including details about how Provider and its Subprocessor will coordinate to respond to inquiries or requests about the Processing of Customer Personal Data. In addition, Provider will share, at Customer’s request, a copy of its agreements (including any amendments) with its Subprocessors. To the extent necessary to protect business secrets or other confidential information, including personal data, Provider may redact the text of its agreement with its Subprocessor prior to sharing a copy.
- Provider remains fully liable for all obligations subcontracted to its Subprocessors, including the acts and omissions of its Subprocessors in Processing Customer Personal Data. Provider will notify Customer of any failure by its Subprocessors to fulfill a material obligation about Customer Personal Data under the agreement between Provider and the Subprocessor.
California Consumer Privacy Act
To the extent the California Consumer Privacy Act, Cal. Civ. Code § 1798.100 et seq. (“CCPA”), applies, the parties acknowledge and agree that Provider is a service provider and is receiving Personal Data from Customer to provide the Service as described in this DPA and detailed in Annex I (see Nature and Purpose of Processing), which constitutes a limited and specified business purpose. Provider will not sell or share any Personal Data provided by Customer in connection with the Service. In addition, Provider will not retain, use, or disclose any Personal Data provided by Customer in connection with the Service except as necessary for providing the Service for Customer, as stated in this DPA, or as permitted by Applicable Data Protection Laws. Provider certifies that it understands the restrictions of this section and will comply with all Applicable Data Protection Laws. Provider will notify Customer if it can no longer meet its obligations under the CCPA.
Restricted Transfers
Authorization.
Customer agrees that Provider may transfer Customer Personal Data outside the EEA, the United Kingdom, or other relevant geographic territory as necessary to provide the Service. If Provider transfers Customer Personal Data to a territory for which the European Commission or other relevant supervisory authority has not issued an adequacy decision, Provider will implement appropriate safeguards for the transfer of Customer Personal Data to that territory consistent with Applicable Data Protection Laws.
Ex-EEA Transfers.
Customer and Provider agree that if the GDPR protects the transfer of Customer Personal Data, the transfer is from Customer from within the EEA to Provider outside of the EEA, and the transfer is not governed by an adequacy decision made by the European Commission, then by entering into this DPA, Customer and Provider are deemed to have signed the EEA SCCs and their Annexes, which are incorporated by reference. Any such transfer is made pursuant to the EEA SCCs, which are completed as follows:
- Module Two (Controller to Processor) of the EEA SCCs apply when Customer is a Controller and Provider is Processing Customer Personal Data for Customer as a Processor.
- Module Three (Processor to Sub-Processor) of the EEA SCCs apply when Customer is a Processor and Provider is Processing Customer Personal Data on behalf of Customer as a Subprocessor.
- For each module, the following applies (when applicable):
- The optional docking clause in Clause 7 does not apply;
- In Clause 9, Option 2 (general written authorization) applies, and the minimum time period for prior notice of Subprocessor changes is 10 business days;
- In Clause 11, the optional language does not apply;
- All square brackets in Clause 13 are removed;
- In Clause 17 (Option 1), the EEA SCCs will be governed by the laws of Ireland;
- In Clause 18(b), disputes will be resolved in the courts of Ireland; and
- The Annexes to this DPA contain the information required in Annex I, Annex II, and Annex III of the EEA SCCs.
Ex-UK Transfers.
Customer and Provider agree that if the UK GDPR protects the transfer of Customer Personal Data, the transfer is from Customer from within the United Kingdom to Provider outside of the United Kingdom, and the transfer is not governed by an adequacy decision made by the United Kingdom Secretary of State, then by entering into this DPA, Customer and Provider are deemed to have signed the UK Addendum and their Annexes, which are incorporated by reference. Any such transfer is made pursuant to the UK Addendum, which is completed as follows:
- Section 4.2 of this DPA contains the information required in Table 2 of the UK Addendum.
- Table 4 of the UK Addendum is modified as follows: Neither party may end the UK Addendum as set out in Section 19 of the UK Addendum; to the extent the ICO issues a revised Approved Addendum under Section 18 of the UK Addendum, the parties will work in good faith to revise this DPA accordingly.
- The Annexes to this DPA contain the information required by Annex 1A, Annex 1B, Annex II, and Annex III of the UK Addendum.
- The UK Addendum is governed by the laws of England and Wales.
Other International Transfers.
For Personal Data transfers where Swiss law (and not the law in any EEA member state or the United Kingdom) applies to the international nature of the transfer, references to the GDPR in Clause 4 of the EEA SCCs are, to the extent legally required, amended to refer to the Swiss Federal Data Protection Act or its successor instead, and the concept of supervisory authority will include the Swiss Federal Data Protection and Information Commissioner.
Security Incident Response
Upon becoming aware of any Security Incident, Provider will: (a) notify Customer without undue delay when feasible, but no later than 72 hours after becoming aware of the Security Incident; (b) provide timely information about the Security Incident as it becomes known or as is reasonably requested by Customer; and (c) promptly take reasonable steps to contain and investigate the Security Incident. Provider’s notification of or response to a Security Incident as required by this DPA will not be construed as an acknowledgment by Provider of any fault or liability for the Security Incident.
Audit & Reports
Audit Rights.
Provider will give Customer all information reasonably necessary to demonstrate its compliance with this DPA and Provider will allow for and contribute to audits, including inspections by Customer, to assess Provider’s compliance with this DPA. However, Provider may restrict access to data or information if Customer’s access to the information would negatively impact Provider’s intellectual property rights, confidentiality obligations, or other obligations under Applicable Laws. Customer acknowledges and agrees that it will only exercise its audit rights under this DPA and any audit rights granted by Applicable Data Protection Laws by instructing Provider to comply with the reporting and due diligence requirements below. Provider will maintain records of its compliance with this DPA for 3 years after the DPA ends.
Security Reports.
Customer acknowledges that Provider is regularly audited against the standards defined in the Security Policy by independent third-party auditors. Upon written request, Provider will make its full SOC 2 Type II report available to Customer on a confidential basis under NDA through Provider’s Trust Center so that Customer can verify Provider’s compliance with the standards defined in the Security Policy.
Security Due Diligence.
In addition to the Report, Provider will respond to reasonable requests for information made by Customer to confirm Provider’s compliance with this DPA, including responses to information security, due diligence, and audit questionnaires, or by giving additional information about its information security program. All such requests must be in writing and made to security@versa.org and may only be made once a year.
Coordination & Cooperation
Response to Inquiries.
If Provider receives any inquiry or request from anyone else about the Processing of Customer Personal Data, Provider will notify Customer about the request and Provider will not respond to the request without Customer’s prior consent. Examples of these kinds of inquiries and requests include a judicial or administrative or regulatory agency order about Customer Personal Data where notifying Customer is not prohibited by Applicable Law, or a request from a data subject. If allowed by Applicable Law, Provider will follow Customer’s reasonable instructions about these requests, including providing status updates and other information reasonably requested by Customer. If a data subject makes a valid request under Applicable Data Protection Laws to delete or opt out of Customer’s giving of Customer Personal Data to Provider, Provider will assist Customer in fulfilling the request according to the Applicable Data Protection Law. Provider will cooperate with and provide reasonable assistance to Customer, at Customer’s expense, in any legal response or other procedural action taken by Customer in response to a third-party request about Provider’s Processing of Customer Personal Data under this DPA.
DPIAs and DTIAs.
If required by Applicable Data Protection Laws, Provider will reasonably assist Customer in conducting any mandated data protection impact assessments or data transfer impact assessments and consultations with relevant data protection authorities, taking into consideration the nature of the Processing and Customer Personal Data.
Deletion of Customer Personal Data
Deletion by Customer.
Provider will enable Customer to delete Customer Personal Data in a manner consistent with the functionality of the Service. Provider will comply with this instruction as soon as reasonably practicable except where further storage of Customer Personal Data is required by Applicable Law.
Deletion at DPA Expiration.
- After the DPA expires, Provider will return or delete Customer Personal Data at Customer’s instruction unless further storage of Customer Personal Data is required or authorized by Applicable Law. If return or destruction is impracticable or prohibited by Applicable Laws, Provider will make reasonable efforts to prevent additional Processing of Customer Personal Data and will continue to protect the Customer Personal Data remaining in its possession, custody, or control. For example, Applicable Laws may require Provider to continue hosting or Processing Customer Personal Data.
- If Customer and Provider have entered the EEA SCCs or the UK Addendum as part of this DPA, Provider will only give Customer the certification of deletion of Personal Data described in Clause 8.1(d) and Clause 8.5 of the EEA SCCs if Customer asks for one.
Limitation of Liability
Liability Caps and Damages Waiver.
To the maximum extent permitted under Applicable Data Protection Laws, each party’s total cumulative liability to the other party arising out of or related to this DPA will be subject to the waivers, exclusions, and limitations of liability stated in any applicable service agreement between the parties.
Related-Party Claims.
Any claims made against Provider or its Affiliates arising out of or related to this DPA may only be brought by the Customer entity that is a party to this DPA.
Exceptions.
This DPA does not limit any liability to an individual about the individual’s data protection rights under Applicable Data Protection Laws. In addition, this DPA does not limit any liability between the parties for violations of the EEA SCCs or UK Addendum.
Conflicts Between Documents
If there is any inconsistency between this DPA and any of its parts, the part listed earlier will control over the part listed later for that inconsistency: (1) the EEA SCCs or the UK Addendum, and then (2) this DPA. If Customer and Provider have entered into a separate service agreement, this DPA will control over that agreement with respect to data processing matters.
Term
This DPA will start when Customer begins using the Service and will continue until Customer’s use of the Service ends. However, Provider and Customer will each remain subject to the obligations in this DPA and Applicable Data Protection Laws until Customer stops transferring Customer Personal Data to Provider and Provider stops Processing Customer Personal Data.
Definitions
“Applicable Laws” means the laws, rules, regulations, court orders, and other binding requirements of a relevant government authority that apply to or govern a party.
“Applicable Data Protection Laws” means the Applicable Laws that govern how the Service may process or use an individual’s personal information, personal data, personally identifiable information, or other similar term.
“Controller” will have the meaning(s) given in the Applicable Data Protection Laws for the company that determines the purpose and extent of Processing Personal Data.
“Customer Personal Data” means Personal Data that Customer uploads or provides to Provider as part of the Service and that is governed by this DPA.
“DPA” means this Data Processing Agreement, including all Annexes, and the policies and documents referenced herein.
“EEA SCCs” means the standard contractual clauses annexed to the European Commission’s Implementing Decision 2021/914 of 4 June 2021 on standard contractual clauses for the transfer of personal data to third countries pursuant to Regulation (EU) 2016/679 of the European Parliament and of the European Council.
“European Economic Area” or “EEA” means the member states of the European Union, Norway, Iceland, and Liechtenstein.
“GDPR” means European Union Regulation 2016/679 as implemented by local law in the relevant EEA member nation.
“Personal Data” will have the meaning(s) given in the Applicable Data Protection Laws for personal information, personal data, or other similar term.
“Processing” or “Process” will have the meaning(s) given in the Applicable Data Protection Laws for any use of, or performance of a computer operation on, Personal Data, including by automatic methods.
“Processor” will have the meaning(s) given in the Applicable Data Protection Laws for the company that Processes Personal Data on behalf of the Controller.
“Report” means audit reports prepared by an independent third party according to the standards defined in the Security Policy on behalf of Provider.
“Restricted Transfer” means (a) where the GDPR applies, a transfer of personal data from the EEA to a country outside of the EEA which is not subject to an adequacy determination by the European Commission; and (b) where the UK GDPR applies, a transfer of personal data from the United Kingdom to any other country which is not subject to adequacy regulations adopted pursuant to Section 17A of the United Kingdom Data Protection Act 2018.
“Security Incident” means a Personal Data Breach as defined in Article 4 of the GDPR.
“Security Policy” means Provider’s security policy available at versa.org/security.
“Service” means the Versa platform and related products and services made available by Provider to Customer.
“Special Category Data” will have the meaning given in Article 9 of the GDPR.
“Subprocessor” will have the meaning(s) given in the Applicable Data Protection Laws for a company that, with the approval and acceptance of Controller, assists the Processor in Processing Personal Data on behalf of the Controller.
“UK GDPR” means European Union Regulation 2016/679 as implemented by section 3 of the United Kingdom’s European Union (Withdrawal) Act of 2018 in the United Kingdom.
“UK Addendum” means the international data transfer addendum to the EEA SCCs issued by the Information Commissioner for Parties making Restricted Transfers under S119A(1) Data Protection Act 2018.
Annex I — Description of Transfer and Processing Activities
Service
The Service is Provider’s platform for retrieving, processing, and delivering travel and expense documentation and related booking data. The Service may include: (a) retrieval of hotel folios and other travel receipts; (b) delivery of receipts and related data to expense management systems; (c) transmission of booking information between travel providers and expense systems; and (d) APIs and integrations enabling automated data exchange between systems designated by Customer.
Categories of Data Subjects
- Customer’s end users or customers
Categories of Personal Data
- Name
- Contact information such as email, phone number, or address
- Transactional information such as account information or purchases
- Location information
Special Category Data
No special category data (as defined in Article 9 of the GDPR) is processed under this DPA.
Frequency of Transfer
Continuous.
Nature and Purpose of Processing
- Retrieval and ingestion of receipt, booking, and transaction data from connected sources
- Normalization and structuring of transaction data into the Versa schema
- Storage and organization of processed data for customer access
- Delivery of structured data to customer-designated receiving systems
- Logging and monitoring of processing activity for operational and security purposes
Provider does not perform profiling or automated decision-making (as defined in GDPR Article 22) on Customer Personal Data.
Duration of Processing
Provider will Process Customer Personal Data as long as required (i) to conduct the Processing activities instructed in Section 2.2(a)–(d); or (ii) by Applicable Laws.
C. Competent Supervisory Authority
The competent supervisory authority will be the supervisory authority of the data exporter, as determined in accordance with Clause 13 of the EEA SCCs or the relevant provision of the UK Addendum.
Annex II — Technical and Organizational Security Measures
Provider implements and maintains the following technical and organizational measures pursuant to Article 32 of the GDPR. Additional detail is available on the Security page.
Encryption (Art. 32(1)(a))
- All data in transit is encrypted using TLS 1.2 or higher
- All data at rest is encrypted using AES-256 or equivalent
- Database credentials, API keys, and secrets are managed through dedicated secrets management tooling
- Where payment metadata is transmitted (e.g. last-four card digits), it is classified as sensitive financial information and subject to additional handling controls
Confidentiality (Art. 32(1)(b))
- Role-based access control (RBAC) with least-privilege policies
- Multi-factor authentication required for all access to production systems
- Audit logging for privileged activity
- Periodic access reviews
- Personnel with access to Customer Personal Data are bound by confidentiality obligations
Integrity (Art. 32(1)(b))
- Automated dependency vulnerability scanning in CI/CD pipelines
- Automated security and linting checks on every build
- Regular patching and update cycles
Availability & Resilience (Art. 32(1)(b))
- Cloud-hosted infrastructure with network isolation and firewall controls
- Continuous infrastructure monitoring and alerting
- Regular vulnerability scanning
- Database backups with point-in-time recovery capabilities
Testing, Assessing & Evaluating (Art. 32(1)(d))
- SOC 2 Type II certification
- Ongoing compliance monitoring through Vanta
- Periodic risk assessments and control evaluations
Incident Response
- Documented incident response program for detection, investigation, and remediation
- Customer notification of confirmed security incidents in accordance with Section 6 of this DPA and applicable law
Subprocessor Oversight
- Subprocessors are subject to due diligence review before engagement
- Contractual obligations requiring subprocessors to maintain equivalent security measures
- Current list of Approved Subprocessors maintained at versa.org/legal/subprocessors
Annex III — Approved Subprocessors
The current list of Approved Subprocessors is maintained at versa.org/legal/subprocessors.