Draft: must be reviewed by a solicitor before launch. This wording is not yet in force and is not legal advice.
Data Processing Agreement
Version: draft 0.1. Last updated: 17 November 2026. Effective from: [effective date: to be added].
This Data Processing Agreement ("DPA") forms part of the Terms of Service between AppstackX Ltd, [company number: to be added], registered office [registered office address: to be added] ("AppstackX", the "Processor") and the business that holds a VesperHire account (the "Customer", the "Controller"). VesperHire is a working name. Accepting the Terms of Service accepts this DPA; no separate signature is needed. A signed copy is available on request from [email protected].
It is written to meet Article 28(3) of the UK GDPR.
1. Definitions
- Data Protection Law means the UK GDPR, the Data Protection Act 2018, the Privacy and Electronic Communications (EC Directive) Regulations 2003, and any law that amends or replaces them in the United Kingdom, including changes made by the Data (Use and Access) Act 2025.
- Customer Personal Data means personal data in the data that the Customer and its users put into the Service, or that the Service creates from it on the Customer's behalf, as described in Annex 1.
- Service means VesperHire as described in the Terms of Service.
- Sub-processor means a processor engaged by AppstackX to process Customer Personal Data.
- "controller", "processor", "data subject", "personal data", "personal data breach" and "processing" have the meanings given in the UK GDPR.
2. Roles and scope
2.1 The Customer is the controller of Customer Personal Data and AppstackX is its processor.
2.2 AppstackX is a separate controller of account, billing, usage and security data about the Customer and its users, as described in the Privacy Policy. This DPA does not apply to that data.
2.3 The subject matter, duration, nature and purpose of the processing, the types of personal data and the categories of data subjects are set out in Annex 1.
3. The Customer's responsibilities
3.1 The Customer is responsible for complying with Data Protection Law as controller, including: having a lawful basis for the data it holds and for each contact it makes; giving data subjects the information required by law; obtaining and recording any consent needed for electronic marketing; telling people on a call that it is being recorded and how the recording will be used; and deciding how long data is kept.
3.2 The Customer confirms that its instructions to AppstackX comply with Data Protection Law.
3.3 The Customer must not put the following into the Service unless it has a clear need and a lawful condition for doing so: special category data, or data about criminal convictions and offences. The Service is not designed as a store for such data.
4. AppstackX's obligations
AppstackX will:
4.1 Instructions. Process Customer Personal Data only on the Customer's documented instructions, including as regards transfers outside the United Kingdom, unless required to do otherwise by UK law; in that case AppstackX will tell the Customer of the legal requirement before processing, unless that law prohibits it. The Customer's instructions are: the Terms of Service, this DPA, the Customer's and its users' use of the Service and its settings, and any further written instructions the parties agree. AppstackX will tell the Customer promptly if it believes an instruction breaks Data Protection Law, and may pause the processing concerned until the point is resolved.
4.2 Confidentiality. Ensure that everyone it authorises to process Customer Personal Data is bound by a duty of confidentiality, and has access only as needed for their work.
4.3 Security. Take the measures required by Article 32 of the UK GDPR. The measures in place are described in Annex 2. AppstackX may update them provided the overall level of protection does not fall.
4.4 Sub-processors. Engage Sub-processors only as set out in clause 5.
4.5 Data subjects' rights. Taking into account the nature of the processing, assist the Customer by appropriate technical and organisational measures, so far as possible, to respond to requests from data subjects. The Service provides tools for this: search, correction, export of everything held about one person, deletion, consent records and a suppression list. If a data subject contacts AppstackX directly about Customer Personal Data, AppstackX will pass the request to the Customer without undue delay where the Customer can be identified, and will not respond to it except to say so, unless the Customer instructs otherwise.
4.6 Assistance. Taking into account the nature of the processing and the information available to it, assist the Customer in meeting its obligations under Articles 32 to 36 of the UK GDPR: security, breach notification, data protection impact assessments and consultation with the Information Commissioner. Assistance beyond the Service's normal features and reasonable information may be charged at a reasonable rate agreed in advance.
4.7 Deletion or return. At the end of the Service, act as set out in clause 9.
4.8 Information and audits. Make available to the Customer all information necessary to demonstrate compliance with Article 28 of the UK GDPR, and allow for and contribute to audits as set out in clause 8.
4.9 No other use. Not sell Customer Personal Data, not use it for its own marketing, and not use it to train AI models.
5. Sub-processors
5.1 The Customer gives general written authorisation for AppstackX to engage Sub-processors. The current list is on the Sub-processors page.
5.2 AppstackX will give the Customer's account owner at least 30 days' notice, by email or in the Service, before adding or replacing a Sub-processor, so that the Customer can object.
5.3 If the Customer objects on reasonable data protection grounds within that period, the parties will discuss the concern in good faith. If it cannot be resolved, the Customer may end the contract before the change takes effect and will receive a refund of fees paid for the period after termination.
5.4 AppstackX will impose on each Sub-processor, by written contract, data protection obligations no less protective than those in this DPA, and remains fully liable to the Customer for the Sub-processor's performance of them.
5.5 In an emergency affecting the security or availability of the Service, AppstackX may replace a Sub-processor with shorter notice and will tell the Customer as soon as it reasonably can.
6. International transfers
6.1 AppstackX intends to host the production database and file storage in the United Kingdom [hosting region: to be confirmed]. Some Sub-processors process data elsewhere, as shown on the Sub-processors page. The Customer instructs AppstackX to make those transfers.
6.2 AppstackX will not transfer Customer Personal Data outside the United Kingdom unless the transfer is covered by UK adequacy regulations, or is subject to appropriate safeguards under Article 46 of the UK GDPR, namely the International Data Transfer Agreement issued by the Information Commissioner (the "UK IDTA") or the International Data Transfer Addendum to the EU Commission standard contractual clauses (the "UK Addendum"), or another mechanism the law allows, together with a transfer risk assessment where required.
6.3 If a transfer mechanism relied on is withdrawn or held invalid, AppstackX will put a valid alternative in place or stop the transfer.
6.4 If the Customer is established outside the United Kingdom, so that AppstackX returning data to it would be a restricted transfer, the parties will enter into the UK IDTA or UK Addendum as needed. [to be reviewed: whether non-UK customers will be accepted]
7. Personal data breaches
7.1 AppstackX will notify the Customer without undue delay, and in any event within 48 hours [period to be confirmed], after becoming aware of a personal data breach affecting Customer Personal Data.
7.2 The notice will be sent to the account owner's email address and will describe, so far as known: what happened; the categories and approximate numbers of data subjects and records concerned; the likely consequences; and the measures taken or proposed. Information may be given in stages as it becomes available.
7.3 AppstackX will take reasonable steps to contain and remedy the breach and will give the Customer the cooperation it reasonably needs to meet its own duties to notify the Information Commissioner and data subjects. The Customer decides whether to notify them.
7.4 Notification of a breach is not an admission of fault or liability.
8. Audits
8.1 On written request, not more than once in any 12 months (or more often if required by a regulator or following a personal data breach), AppstackX will give the Customer: a written description of its security measures; answers to a reasonable security questionnaire; and copies or summaries of relevant third-party certifications or audit reports held by AppstackX or its main Sub-processors, where available.
8.2 If that information is not reasonably enough to demonstrate compliance, the Customer, or an independent auditor it appoints who is bound by confidentiality and is not a competitor of AppstackX, may carry out an audit, including an inspection, on at least 30 days' written notice, during business hours, in a way that does not disrupt the Service or risk other customers' data. As AppstackX runs on cloud infrastructure, an inspection may take the form of a remote review.
8.3 The Customer bears its own audit costs, and AppstackX's reasonable costs for an audit under clause 8.2 unless the audit finds a material breach of this DPA.
9. Deletion and return of data
9.1 During the contract the Customer can export Customer Personal Data from the Service and can delete records, which removes the related files, messages and search data. Where a deleted person had opted out of contact, a minimal suppression entry (the number or address and the channel) is kept so that the opt-out continues to be honoured.
9.2 When the contract ends, AppstackX will keep Customer Personal Data available for export on request for 30 days. After that, at the Customer's choice it will return or delete it; if the Customer makes no choice, AppstackX will delete it. Deletion from live systems will be completed within a further 60 days [period to be confirmed], and from backups when those backups are overwritten in the ordinary cycle of [backup retention period: to be confirmed].
9.3 AppstackX may keep Customer Personal Data where UK law requires it to, and will tell the Customer what is kept and why. That data remains protected by this DPA and is not otherwise processed.
9.4 On request, AppstackX will confirm in writing that deletion has been completed.
10. Liability and general
10.1 Each party's liability under this DPA is subject to the limits in the Terms of Service. Nothing in this DPA limits either party's liability to data subjects or to the Information Commissioner under Data Protection Law. [to be reviewed alongside the liability cap in the Terms of Service]
10.2 If this DPA conflicts with the Terms of Service on a data protection matter, this DPA takes priority.
10.3 If Data Protection Law changes so that this DPA needs to change, the parties will agree the changes in good faith; AppstackX may make changes needed to comply with the law by giving notice under the Terms of Service.
10.4 This DPA is governed by the law of England and Wales and the courts of England and Wales have exclusive jurisdiction.
Annex 1: Details of the processing
| Item | Detail |
|---|---|
| Subject matter | Providing the VesperHire recruitment CRM to the Customer |
| Duration | For the term of the contract, plus the export and deletion periods in clause 9 |
| Nature of the processing | Hosting, storage, organisation, search and retrieval; reading and structuring CVs; drafting, sending and receiving texts and emails; recording consent and opt-outs; transcribing and summarising notes and recordings; AI-assisted search, ranking, drafting and summarising on the user's command; export and deletion |
| Purpose | To let the Customer run its recruitment business: keeping records of candidates, clients, jobs and placements, contacting them, and keeping the records the law requires |
| Categories of data subjects | Candidates and work-seekers; contacts at the Customer's clients and prospects; referees and other people named in CVs, notes or messages; the Customer's own users, as they appear in records and history |
| Types of personal data | Names and contact details; job titles, skills, work history, education and qualifications; CVs and other documents; availability, pay and salary expectations; right-to-work and compliance status where recorded; notes of conversations; texts and emails sent and received; consent and opt-out records; call and meeting recordings, transcripts and summaries; history of actions taken on a record |
| Special category and criminal offence data | Not required by the Service. It may be present where a CV, note, message or recording includes it (for example health information or a disclosed conviction). The Customer decides whether to record it and must have a lawful condition for doing so |
| Sub-processors | As listed on the Sub-processors page |
| Processor contact | [email protected] |
Annex 2: Security measures
This annex describes the measures designed into VesperHire. Items marked [to be confirmed] depend on hosting choices not yet made and must be completed before launch.
Access control and separation of customers
- Every table is protected by row-level security in the database, keyed on the agency, so one agency's users cannot read or change another agency's records even if application code is at fault.
- Role-based permissions inside each agency (owner and recruiter). Sensitive actions such as role changes, invitations, removals, exports and deletions are restricted and written to an audit log that users cannot alter.
- Each user has an individual login. Passwords must be at least 10 characters and are stored only as salted hashes by the authentication service. [multi-factor authentication: to be decided]
- Files (CVs, recordings) are kept in private storage, in folders by agency, and are opened only through time-limited links. A CV reaches someone outside the agency only when a user chooses to send it to a client contact, by a link that expires.
Encryption
- In transit: HTTPS (TLS) for all connections between browsers, the application and suppliers.
- At rest: database and file storage encrypted by the hosting provider. [to be confirmed for the chosen hosting]
Safeguards on messaging and AI
- Nothing is sent to people outside the agency without a user's confirmation. Recipients who have opted out, lack consent for the channel, are marked do not contact or lack contact details are removed in code before every send.
- Sending limits per user and per agency; every send is logged.
- AI calls go through a single controlled route. Text from CVs, notes, messages and imports is treated as data and not as instructions to the AI. The AI can only propose actions; code carries them out, subject to the checks above.
- AI ranking is not given names, photographs, dates of birth or similar markers.
Operations
- Staff access to production data is limited to those who need it to run and support the Service, and is used only for those purposes. [access logging and review: to be confirmed]
- Backups: [frequency, retention and restore testing: to be confirmed].
- Changes are reviewed and tested before release; secrets are kept out of source code.
- Suppliers are assessed for security before use and bound by contract.
- Vulnerability management and dependency updates: [process to be confirmed]. Independent penetration test: [to be decided before launch].
Resilience and incidents
- Monitoring and alerting: [to be confirmed for the chosen hosting].
- A written incident response procedure, including the breach notification steps in clause 7: [to be written before launch].
Data minimisation and retention
- The Customer sets a retention period; records past it are flagged and then deleted.
- Deleting a person removes their files, messages and search data, leaving only a suppression entry where needed to honour an opt-out.