Draft: must be reviewed by a solicitor before launch. This wording is not yet in force and is not legal advice.
Sub-processors
Version: draft 0.1. Last updated: 17 November 2026.
AppstackX Ltd uses the suppliers below to provide VesperHire (a working name). Where a supplier handles personal data that an agency has put into VesperHire, it acts as our sub-processor under the Data Processing Agreement.
VesperHire is not yet live. The table shows honestly where each supplier stands today: "in use in development" means the code uses it now with test data only; "planned, not yet contracted" means no contract has been signed and the choice may change. No real customer data is processed by anyone until launch.
1. Current and planned sub-processors
| Supplier | What it does for VesperHire | Data involved | Where it processes | Transfer safeguard | Status |
|---|---|---|---|---|---|
| Anthropic (Anthropic PBC, USA, or its contracting affiliate [contracting entity: to be confirmed]) | AI model behind the assistant, CV reading, message drafting, reply handling, summaries of notes and calls | Text of commands, CVs, notes, messages and transcripts sent for a task. Names and similar markers are withheld from AI ranking | United States, and other locations Anthropic lists [to be confirmed] | Anthropic's data processing addendum with the UK Addendum to the EU standard contractual clauses [to be verified] | In use in development (test data only). Commercial terms to be reviewed before launch |
| Supabase (Supabase Inc, USA; hosted on Amazon Web Services) | Database, sign-in (authentication), file storage for CVs and recordings | All agency data and account data | Development: on the developer's own machine only, nothing is sent to Supabase. Production: hosted project, intended region London [Supabase region: to be confirmed] | For support access from outside the UK: Supabase's data processing addendum with the UK Addendum [to be verified] | In use in development (local only). Hosted project planned, not yet contracted |
| [hosting provider: to be chosen before launch] | Runs the web application | All data passes through it in transit | [to be confirmed]; UK preferred | [to be confirmed] | Planned, not yet contracted |
| [SMS provider: to be chosen before launch] (UK providers such as The SMS Works or ClickSend are being considered) | Sends text messages and receives replies, including STOP | Mobile numbers, message text, delivery status | [to be confirmed]; UK preferred | [to be confirmed] | Planned, not yet contracted. Development uses a local stand-in; no text leaves the developer's machine |
| [email sending provider: to be chosen before launch] | Sends emails from agencies to candidates and client contacts, and service emails from us | Email addresses, message content, delivery status | [to be confirmed] | [to be confirmed] | Planned, not yet contracted. Development uses a local mail catcher; no email leaves the developer's machine |
| [speech-to-text provider: to be chosen before launch] (Deepgram and AssemblyAI are being considered) | Turns spoken commands, and uploaded call recordings where the agency asks for a transcript, into text | Audio of the recruiter's voice; for call recordings, the voices and words of everyone on the call | [to be confirmed] | [to be confirmed] | Planned, not yet contracted. See the development note below |
| [text-to-speech provider: to be chosen before launch] (ElevenLabs and Deepgram are being considered) | Speaks the assistant's short replies | Short reply text. Replies are designed not to include salaries or phone numbers | [to be confirmed] | [to be confirmed] | Planned, not yet contracted. Development uses the browser's built-in voice, on the device |
| Stripe (contracting entity [to be confirmed], in a Stripe account used only for VesperHire) | Subscription billing and credit purchases | Agency billing contact and payment details. No candidate data | UK, EEA and United States | Stripe's data processing agreement [to be verified]. For card payments Stripe also acts as a controller in its own right | Planned, not yet contracted. Development uses a local stand-in; no money moves |
2. Development note on speech recognition
In development, hold-to-talk uses the browser's built-in speech recognition. In Google Chrome that feature sends audio to Google for recognition. It is a development convenience used with test data only and must be replaced by the contracted speech-to-text provider before any customer uses voice features. [owner to confirm this is done before launch]
3. Suppliers that are not sub-processors
We also use ordinary business tools (for example email and accounting) for our own account, billing and support records, for which we are the controller. They do not receive agency data. [list of business tools: to be added before launch]
4. Changes to this list
We will give agency owners at least 30 days' notice, by email or in the app, before a new sub-processor starts handling agency data, as set out in the Data Processing Agreement. An agency that objects on reasonable data protection grounds can use the process described there.
5. Contact
Questions about this list: [email protected]. AppstackX Ltd, https://appstackx.co.uk.