Supvoices Data Processing Agreement
This Data Processing Agreement (DPA) forms part of the Agreement between SR TravelTech Services Ltd (company number 16349999), trading as Supvoices (Supvoices, the processor) and the Customer named in the Order Form (the controller). It sets out how Supvoices processes personal data on the Customer's behalf, as required by Article 28 of the UK GDPR and, where it applies, Article 28 of the EU GDPR. Terms defined in the Subscription Terms have the same meaning here.
1. Definitions
- Data Protection Law: the UK GDPR, the Data Protection Act 2018 and the Privacy and Electronic Communications Regulations 2003 (each as amended, including by the Data (Use and Access) Act 2025) and, where it applies to the processing, the EU GDPR (Regulation (EU) 2016/679) and the national laws implementing or supplementing it.
- Personal Data: personal data contained in Customer Data that Supvoices processes on the Customer's behalf.
- controller, processor, data subject, processing, personal data breach, supervisory authority: as defined in Data Protection Law.
- Sub-processor: a third party Supvoices engages to process Personal Data.
- Restricted Transfer: a transfer of Personal Data to a country that does not have an adequacy decision or regulations recognising it as adequate under the applicable Data Protection Law.
2. Roles
2.1 The Customer is the controller and Supvoices is the processor of Personal Data.
2.2 Supvoices is a controller only of the personal data it needs to run its own business, such as Customer contact details, billing records and User account data used to secure and bill the Service. That data is covered by the Supvoices Privacy Policy, not this DPA.
2.3 The Customer's Connected Systems (for example its reservation system, Microsoft 365 and accounting system, such as Xero) are operated by the Customer or its own providers. Supvoices connects to them on the Customer's instructions; their providers are not Supvoices' Sub-processors.
3. Supvoices' obligations
Supvoices will:
- process Personal Data only on the Customer's documented instructions, which are the Agreement and the Customer's use and configuration of the Service, unless the law requires otherwise (in which case Supvoices will tell the Customer first, unless the law forbids it);
- tell the Customer promptly if it believes an instruction breaches Data Protection Law;
- make sure everyone authorised to process Personal Data is bound by confidentiality;
- apply the security measures in Annex 2;
- use Sub-processors only under section 5;
- help the Customer, taking into account the nature of the processing, to respond to data subject requests (section 6);
- help the Customer with security, breach notification, data protection impact assessments and prior consultation with a supervisory authority, as far as these relate to the Service;
- delete or return Personal Data when the Agreement ends (section 9);
- make available the information needed to show compliance with this DPA, and allow audits under section 10.
4. The Customer's obligations
4.1 The Customer is responsible for having a lawful basis for the processing, for giving any notices to data subjects (for example its suppliers' staff and its passengers), and for the lawfulness of its instructions.
4.2 The Customer will not upload special category or criminal-offence data except where it unavoidably appears on supplier documents, as set out in the Acceptable Use Policy.
5. Sub-processors
5.1 The Customer gives general authorisation for Supvoices to use Sub-processors. The current list, with each Sub-processor's purpose and location, is published at supvoices.com/legal/subprocessors.
5.2 Supvoices will give at least 30 days' notice before adding or replacing a Sub-processor, by email to the Customer's nominated contact and by updating the list.
5.3 The Customer may object on reasonable data protection grounds within that 30-day period. The parties will discuss the objection in good faith. If it is not resolved, the Customer may end the affected part of the Agreement by written notice, and Supvoices will refund Fees paid in advance for the period after termination.
5.4 Supvoices will put a written contract in place with each Sub-processor with data protection obligations no less protective than this DPA, and remains liable to the Customer for its Sub-processors' performance.
6. Data subject requests
6.1 The Service lets the Customer find, export, correct and delete Personal Data in its instance. If Supvoices receives a request directly from a data subject about Personal Data, it will pass it to the Customer without undue delay and will not respond itself except to confirm it has passed it on.
6.2 Where the Customer cannot handle a request using the Service, Supvoices will provide reasonable help. Help beyond reasonable levels may be charged at the rates in the Order Form.
7. Personal data breaches
7.1 Supvoices will notify the Customer without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting Personal Data.
7.2 The notice will describe, as far as known: the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, and the measures taken or proposed. Supvoices will send further information as it becomes available.
7.3 Supvoices will take reasonable steps to contain and remedy the breach, and will help the Customer meet its own notification duties. Notifying a breach is not an admission of fault.
8. International transfers
8.1 Supvoices is based in the United Kingdom. Each Customer's instance is hosted in the region shown in the Sub-processor list (by default the United Kingdom or the European Economic Area).
8.2 Supvoices will make a Restricted Transfer, or allow a Sub-processor to make one, only with a valid transfer safeguard under Data Protection Law, such as:
- from the UK: UK adequacy regulations (including the UK Extension to the EU-US Data Privacy Framework, where the recipient is certified), or the UK International Data Transfer Agreement or the UK Addendum to the EU Standard Contractual Clauses;
- from the EEA: an EU adequacy decision (including for the United Kingdom, and the EU-US Data Privacy Framework where the recipient is certified), or the EU Standard Contractual Clauses (Commission Decision 2021/914).
9. Return and deletion
9.1 When the Agreement ends, the Customer may request an export of its Customer Data for 30 days, as set out in the Subscription Terms.
9.2 Supvoices will then delete Personal Data from its instance and file storage within a further 60 days, and from backups when those backups expire (within 35 days of deletion from the live system), unless the law requires it to keep some data. Supvoices will confirm deletion in writing on request.
9.3 Copies the Service filed in the Customer's own SharePoint or OneDrive are under the Customer's control and are not deleted by Supvoices.
10. Audits
10.1 Supvoices will answer the Customer's reasonable written security and data protection questions, and share relevant documentation (for example security policies and Sub-processor certifications), once a year or after a personal data breach.
10.2 If that is not enough to show compliance, or a supervisory authority requires it, the Customer (or an independent auditor bound by confidentiality) may carry out an audit, at the Customer's cost, on at least 30 days' notice, during business hours, no more than once in any 12 months, and without access to other customers' data.
11. Liability and term
11.1 Each party's liability under this DPA is subject to the limits in the Subscription Terms (including the data protection cap in clause 11.5).
11.2 This DPA lasts as long as Supvoices processes Personal Data for the Customer.
Annex 1 — Details of the processing
| Subject matter and nature | Providing the Service: receiving, storing and extracting data from supplier documents; matching them to the Customer's vouchers or purchase orders; managing queries and supplier correction requests; logging activity; exporting and filing records to the Customer's systems; where the Customer chooses an Accounting Connection, creating supplier bills and credit notes in the Customer's accounting system and reading back their status; support |
| Duration | The term of the Agreement plus the export and deletion periods in section 9 |
| Purpose | To provide the Service to the Customer under the Agreement |
| Categories of data subjects | The Customer's Users and staff; contacts at the Customer's suppliers (including sole traders and individual guides or drivers); the Customer's clients, passengers or guests named on supplier documents or vouchers |
| Categories of personal data | Names, job titles, business email addresses and phone numbers; User log-in and activity records; supplier bank details (for example IBAN) where the supplier is an individual or sole trader; names of passengers or group leaders, booking references and service dates on invoices and vouchers; contents of queries and messages |
| Special category data | Not intended. May unavoidably appear on supplier documents (for example dietary or accessibility notes). Handled with the same security measures and only as part of the document |
| Frequency | Continuous, while the Customer uses the Service |
| Retention | As configured by the Customer during the term; then as in section 9 |
Annex 2 — Security measures
- Separation: each Customer has its own database and file storage project; no shared customer database.
- Encryption: data encrypted in transit (TLS 1.2 or higher) and at rest by the hosting provider.
- Access control: role-based permissions in the Service (for example User, supervisor, administrator) enforced in the database; least-privilege access for Supvoices staff, limited to support and maintenance; multi-factor authentication on Supvoices' administrative accounts.
- Secrets: credentials for Connected Systems stored encrypted or in a secrets vault, never in application code. Accounting system connections use the provider's own authorisation (for Xero, OAuth 2.0), limited to the permissions the connection needs, and the Customer can revoke them at any time from its accounting system.
- Logging: an audit log of User actions and decisions in the Service; posting and reversal recorded with who and when.
- Validation: every posting passes server-side checks in a single database transaction.
- Backups: daily database backups kept for at least 7 days; tested restore procedure.
- Development: code reviewed before release; automated tests on matching and posting logic; separate test environments without Customer Data where practical.
- AI providers: used under commercial terms that prohibit training on Customer Data.
- People: confidentiality obligations for anyone with access; access removed when no longer needed.
- Incidents: documented incident response, including the notification timeline in section 7.
Annex 3 — Sub-processors
As listed at supvoices.com/legal/subprocessors on the date of the Order Form, and as updated under section 5.