Sub-processors
MVV Technologies Limited (company number 17300982, registered in England and Wales) ("MVV", "we") uses the organisations below to provide the MVV App, the service described in the Terms of Service. This page is the list that clause 7 of the Data Processing Agreement (the "DPA") refers to.
Version: 13 October 2026.
This page is published on MVV's help site, help.mvvtechnologies.com. Every earlier version stays published there, with a note of what each version changed. "Changes to this list", at the end of this page, says how we tell you before the list changes.
How to read this page
- Section A lists the organisations that process your business's personal data for you, on our instructions, when you use the service. These are sub-processors in the UK GDPR sense.
- Section B lists services you connect yourself, with your own account or link, and public look-up services that need no account. They act on your instructions, not ours.
- Section C lists organisations we use only for our own business (for example our own email and our help pages). They are covered by our Privacy Policy, not by the DPA.
- Section D lists what starts when sign-up opens and what is planned but not in use. Section E lists what is blocked.
- "When sign-up opens" means the day MVV sends its first invitation to join to a customer. Joining is by invitation: MVV's public sign-up form is not open, and the rows about that form apply only if MVV opens it. Until that day no customer's payment is taken. Before that day MVV may run the invitation and payment steps in test mode to rehearse them.
- "Where" says where the data is held or processed, as far as the platform's own settings decide it. Where a provider decides for itself, we say so. Where we say the platform sets no region, treat the data as processed outside the UK.
- "Transfer basis" is the legal mechanism that the provider's own terms give for a transfer outside the UK. Each entry is what MVV recorded when it read the provider's published terms on 10 September 2026, unless the entry gives a later date. "Not yet recorded" means MVV had not recorded that provider's mechanism by the date of this version.
- In that column, "SCCs" means the European Commission's Standard Contractual Clauses, "UK Addendum" the UK's addendum to them, "UK IDTA" the UK's International Data Transfer Agreement, and "Data Privacy Framework" the EU-US Data Privacy Framework with its UK Extension.
- Where MVV's reading of a provider's terms, or the provider's public registration, recorded a company name, we give it in brackets. Otherwise we give the provider's name only.
A. Sub-processors of your business data
| # | Provider | What it does for the service | What data | Where | Transfer basis | Status |
|---|---|---|---|---|---|---|
| A1 | Supabase (Supabase Pte. Ltd, Singapore; its terms name Supabase, Inc., United States, as its own sub-processor) | Runs your Workspace's own database, sign-in, file storage, server functions and scheduled jobs. Each customer has a separate Supabase project; no other customer's data is in it. Supabase also runs MVV's own control database, which holds no customer business data, and MVV's own server functions. In use: the AI gateway and the WhatsApp router, which pass your requests and messages through without storing their content (the router carries nothing for your Workspace while WhatsApp is off for it, see A10); MVV ID, in use since 25 September 2026, which lets a person find their company from MVV's phone app: about once an hour your Workspace sends it the list of your people's sign-in email addresses, and it keeps a keyed fingerprint of each address and a hint (its first character and its domain), never the address itself; and the Stripe webhook, running since 29 September 2026, which records Stripe's events about MVV's own billing (Section D). The sign-up intake carries the requests sent from MVV's "I'd like to join" page from the day that page opens, sealed before they are stored so that only MVV's own computer can read them; its other steps start when sign-up opens (Section D). One more is built and switched off: the law-library search, through which your Workspace's Contract Helper would search one central copy of the law library. Its search text, which can name people, would pass through without being stored, and a count per Workspace per day would be kept. | Everything in your Workspace: your people's accounts and sign-in records, projects, customers, operatives, suppliers, money records, documents, photos, messages, voice notes. Supabase also takes its own backups of your Workspace's project and keeps them under its own terms; MVV cannot delete those itself. For MVV's control database: see the Privacy Policy. | Your Workspace: the region chosen from your country when it is created. UK businesses: London (eu-west-2); Ireland: Dublin (eu-west-1); Germany and Italy: Frankfurt (eu-central-1); France: Paris (eu-west-3); Switzerland: Zurich (eu-central-2). A country with no mapped region is refused, never defaulted. MVV's control database: London. Server functions: the platform does not pin them to a region, so Supabase decides where each one runs, which may be outside the UK. Supabase's own terms, as MVV read them on 10 September 2026, say that its backups, its logs and its own sub-processors are outside the regional setting too. | EU SCCs (Modules 2 and 3) with the UK Addendum. No Data Privacy Framework certification. | In use |
| A2 | Cloudflare | (a) Gateway address. Every AI request your Workspace's server functions make, every email your Workspace sends, the list of sign-in email addresses your Workspace sends MVV ID, every incoming WhatsApp message and, once WhatsApp is switched on for your Workspace, every WhatsApp message it sends, with the photos and voice notes it fetches, pass through a Cloudflare Worker at gw.mvvtechnologies.com on their way to MVV's gateway, MVV ID or MVV's WhatsApp router. So does the email address a person types into MVV's phone app to find their company. Cloudflare counts the requests each network address sends to MVV ID and blocks an address for a short time when it sends too many. A live voice conversation does not pass through it. (b) Backups. The backups of every Workspace, which MVV aims to make nightly, are stored in Cloudflare R2 object storage, in a bucket restricted to the EU jurisdiction, one folder per Workspace. (c) Email routing. Replies sent to our no-reply addresses are received by Cloudflare Email Routing and answered by an automatic reply; the message is not forwarded or kept, and the sender's address is held for 25 hours so each person gets one reply a day. Cloudflare's logs of the automatic reply service can also hold the sender's address for a few days. | (a) Request content in transit, including prompts, documents, images, email bodies, your people's sign-in email addresses, and WhatsApp messages in and out with the photos and voice notes a Workspace fetches; the network (IP) address of a phone that uses MVV ID. (b) A full copy of your Workspace: database, people and sign-in records (including password hashes and second-factor settings), and every stored file, up to 20,000. A Workspace holding more, or a night its files cannot be exported, is backed up without its files, and MVV is alerted. Every part is sealed with a key of your Workspace's own that Cloudflare does not hold in a form it can open, and filed under names that do not show your files' names. Cloudflare does hold copies of that key (a current copy and dated copies) and, once your Workspace has one, of the key that locks the passwords of the services your Workspace is connected to. Each copy is itself sealed to MVV's master backup key. Cloudflare does not hold that master key: its private half is kept only in a password manager held by authorised MVV personnel. Since 30 September 2026 a 30-day lock at Cloudflare stops any backup, or dated key copy, being deleted or overwritten before it is 30 days old, even with MVV's own storage key. After a Workspace has left and its key has been destroyed, a short note stays in the storage, naming the Workspace's short name and the date its key was destroyed. (c) The address of the person replying, and Cloudflare's logs of the reply service. | (a) Cloudflare's own network: Cloudflare chooses the location that handles each request, and the platform sets none. (b) EU (R2 EU jurisdiction). (c) Cloudflare's own network, as for (a). | EU SCCs with the UK Addendum, and the Data Privacy Framework. | In use |
| A3 | Netlify | Hosts the Workspace web app, the files your browser downloads, on MVV's own Netlify team. Your Workspace's site there is created, named after your Workspace, before your Workspace is built. The app talks to your Workspace's own server directly, not through Netlify. MVV's publishing tool uploads the app's built files and does not ask Netlify to run any function of MVV's for your Workspace. | Request records: IP address, browser details, the page asked for, time. The site's name, which is made from your company's trading name. | Netlify's content delivery network: Netlify chooses the location that serves each visitor and where its request records are kept; the platform sets none. | Data Privacy Framework first, with SCCs and the UK IDTA as the fallback. When we read it, Netlify's certification showed a usage end date of 17 December 2026. | In use |
| A4 | Anthropic (Anthropic Ireland, Limited, for UK customers) | The main AI model behind the Workspace's assistants: reading documents and photos, drafting reports and documents, answering questions, the WhatsApp and in-app assistant. It also writes the answers of the in-app Support chat (Claude Haiku, on MVV's own key, while Google, A6, is not in use) and of the help assistant in the corner of the app. It also performs web searches through its own search tool, used in six places in the server functions, among them the WhatsApp assistant and the health and safety generator. Anthropic also supplies the AI coding assistant with which MVV operates the platform on MVV's own computer (see "Not on this list, on purpose"): the assistant acts only on MVV's instructions, and what it reads there is sent to Anthropic. | What the assistant is asked to work on: text, images (for example site photos, receipts, drawings), documents, project and money records, names and contact details that appear in them. Search queries. For the Support chat: the question typed (up to 1,000 characters) and up to six earlier turns of the same conversation (up to 2,000 characters each), the name of the screen the person is on and their role, MVV's help text for that screen and any extra instructions the Workspace has set; nothing from the Workspace's records, and not the person's name, email address, account or IP address. For the coding assistant: what MVV's tools show it and the files it is asked to work on, which can include a Workspace's data during a backup, a restore test or a leaving export. | The platform sets no region. Anthropic's own pages, as MVV read them on 4 October 2026, say that it stores data in the United States only, and processes it in the United States or, by default, worldwide ("global"), with no UK or EU option. The platform does not change that default. The web searches are carried out by search providers that Anthropic chooses: its own list of its sub-processors names Brave Search and TurboPuffer for web search, in the United States. MVV does not choose them and has not confirmed which of them carries out each search. | EU SCCs (Modules 2 and 3) with the UK Addendum, in Anthropic's data processing addendum. For the coding assistant: not yet recorded. | In use |
| A5 | OpenAI (OpenAI OpCo, LLC, for UK customers) | Speech-to-text (voice notes and voice messages) and text-to-speech (spoken replies), called through MVV's gateway. Also, through ElevenLabs (A7): OpenAI's models are the language models ElevenLabs runs for three of the six live voice assistants: gpt-4.1-mini for Vera and the Accountant, and gpt-4.1 for the Project Manager, so their conversations, and the records the assistant reads out in them, are processed by an OpenAI model. The model behind the Support, Atlas and Contract Helper voice assistants is set in MVV's ElevenLabs account, not in the platform's code, and may also be an OpenAI model (see A7). | Audio recordings and their transcripts; text to be spoken; live voice conversations with the three assistants above, through ElevenLabs. | The service calls OpenAI's default address, api.openai.com, not a regional one, so OpenAI decides where each request is processed. | SCCs with the UK Addendum, in OpenAI's data processing addendum of 4 October 2026, which MVV and OpenAI have signed. | In use |
| A6 | Google (Gemini API) | Built, not in use. The in-app Support chat is built to ask a Gemini Flash model first, through MVV's gateway. MVV's gateway holds no Gemini key, so it refuses every such call before anything is sent to Google, and Anthropic (A4) writes the answer instead. If MVV ever loads a Gemini key, it will first give the notice in DPA clause 7.2. No Workspace holds a Gemini key or a Google AI account of its own. | None while it is not in use. | If it is ever used: Google's own infrastructure, at Google's default address, generativelanguage.googleapis.com; the platform sets no region. | Not yet recorded. | Not in use. Nothing is sent to Google. |
| A7 | ElevenLabs | Live voice conversations with the assistants. Your browser connects to ElevenLabs directly, using a one-off signed link that MVV's gateway obtains; no key is in your browser. There are six voice assistants (Support, Atlas, Vera, the Accountant, the Project Manager and the Contract Helper), and every customer's are agents in one MVV ElevenLabs account. The conversation is processed by the agent's language model, which ElevenLabs runs: OpenAI's gpt-4.1-mini for Vera and the Accountant and OpenAI's gpt-4.1 for the Project Manager, including what their tools look up and read out, such as invoices, entries and draft evaluations. For Support, Atlas and the Contract Helper the model is the one set on each agent in MVV's ElevenLabs account, not in the platform's code; it may be a model from another provider, run by ElevenLabs in the same way. If an agent's model fails, ElevenLabs may move the call to a backup model; MVV has set every Workspace's voice assistants so that the only backup model is OpenAI's gpt-4o. This traffic does not pass MVV's gateway, so the gateway's IP stripping, records and daily limits do not apply to it. Atlas, the Contract Helper and the Project Manager also pass what the caller asks, and the Contract Helper the last turns of the call, to your Workspace's own AI functions, which use Anthropic (A4); Atlas may also search the web (A4). | The user's voice and the conversation, including the records read out on the call and, with the Contract Helper, what is said about a legal case; the user's IP address. Since 4 October 2026, MVV has set every Workspace's voice assistants in the ElevenLabs account that holds them so that ElevenLabs stores no audio of the call and deletes each conversation, with its transcript, after the call: it keeps them for 0 days. ElevenLabs says that deleted data can stay in its backups for up to 30 days, and that its debugging and moderation logs may still hold data about a call. MVV has also switched off the ElevenLabs setting "Improve the models for everyone" in that account. | api.elevenlabs.io. ElevenLabs' EU data-residency addresses are blocked by the platform today. ElevenLabs decides where the conversation, and each agent's language model, are processed; the platform sets no region. | Not yet recorded, including for the onward transfers to OpenAI, to whichever provider runs the other three agents' model and to the providers of the backup models. | In use |
| A8 | Brave Search | Web searches for assistants that research on the web (for example the Contract Helper and research tools). | Search queries, which may contain names of firms, people or places. | Brave's own infrastructure; the platform sets no region. | Not yet recorded. | Not in use. Built into the gateway, but the gateway holds no Brave key, so it refuses every such call and nothing is sent to Brave by this route. If MVV ever loads a Brave key, it will first give the notice in DPA clause 7.2. Anthropic's own search tool is a separate route (A4). |
| A9 | Resend (Plus Five Five, Inc., trading as Resend, by its Data Privacy Framework record) | Sends the email your Workspace sends (quotes, invoices, notices) from MVV's one shared address notifications@mvvtechnologies.com, with your company's trading name as the sender name (from when sign-up opens, the name as MVV's records hold it). From when sign-up opens, password emails go the same way: MVV writes them, and each goes to the one person only, never copied. Every email is marked no-reply and tagged with your Workspace's short name. Where you have given us a records address, a hidden copy (BCC) of your company email goes to it, unless that would take an email over 50 recipients. | Recipient addresses, subject, message, attachments, a tag naming the Workspace; delivery records. Resend keeps its records under its own terms; MVV's note of its plan, made in September 2026, records 30 days for its logs. | United States. Resend's terms, as MVV read them on 10 September 2026, say message data is stored there whatever region an email is sent from. | Data Privacy Framework first, with SCCs and the UK Addendum as the fallback. When we read it, Resend's certification was marked as under re-certification review. | In use |
| A10 | Meta (WhatsApp Business Platform, Cloud API) | Carries WhatsApp messages between your people and MVV's one shared WhatsApp number: link requests, job notices, the WhatsApp assistant, photos sent in. Incoming messages pass through MVV's router, which passes each to the right Workspace and keeps no message content and no phone number. Messages your Workspace sends, and the photos and voice notes it fetches, go through MVV's router, which sends them to Meta with MVV's own credentials, only to a person linked to your company; your Workspace holds no WhatsApp token. A job notice is sent in MVV's approved wording. | Phone numbers, message text, photos, voice messages. | Meta's own infrastructure. The platform sets no WhatsApp data-localisation region, so Meta decides where messages are stored. | The WhatsApp Business UK Data Transfer Addendum (SCCs with the UK Addendum). WhatsApp LLC is not certified for the Data Privacy Framework's UK Extension. | In use when sign-up opens (Terms of Service, clause 8.3): switched on automatically for each customer's Workspace once the version of the Terms of Service that offers WhatsApp is in force, on MVV's own number once Meta has verified MVV's business; until then it runs only on a Meta test number. A person is linked to your company only by their own "Yes, link me" (a tap, or a yes quoted onto your link request); STOP or Unsubscribe cuts every link, except that a bare "Stop" sent as a reply to one of your company's own messages reaches your company as an instruction and does not unlink them; MVV does not see the content of the messages. |
| A11 | GitHub (a Microsoft company) | Holds MVV's private source code. It holds nothing of a customer's. The only company set-up profiles in MVV's repositories are those of MVV's own demonstration Workspaces: invented companies and MVV's own Workspace, whose profile carries MVV's own company name and number and its director's name and email address, with invented contact details for the company. A paying customer's company details are kept outside them: in a private folder on MVV's computer and in the Workspace's backups. GitHub is listed here so that you can see this. Every repository holding MVV's code there is private, and the GitHub account that holds them uses two-step sign-in. | None of a customer's, as built. | United States by default, by GitHub's terms as MVV read them on 10 September 2026. | Data Privacy Framework: GitHub's certification, with its UK Extension, was active when MVV checked it on 4 October 2026. | In use for MVV's source code and its demonstration Workspaces only. |
MVV's Resend account (A9), MVV's Cloudflare account (A2), the ElevenLabs account that holds the voice assistants (A7) and MVV's Anthropic organisation (A4) are shared with an affiliated business.
Not on this list, on purpose:
- MVV's own operations computer. MVV runs its control console, build and backup tools on its own computer at its premises in England. During a backup, a restore test or a leaving export, a full working copy of a Workspace is on that computer, in a folder on an encrypted disk. That is MVV itself, not a sub-processor, but it is a place your data is processed, so it is stated here. MVV has rented a server to take over this work (Section D, OVHcloud). On the date of this version none of this work has moved to it.
- The AI coding assistant MVV uses to operate the platform. MVV operates the platform with the help of an AI coding assistant on that computer, which acts only on MVV's instructions. Its supplier is on this list: Anthropic (A4).
B. Services you connect yourself
These run under your account, link or instruction, or are public look-up services that need no account. No key of MVV's is used for them: where one needs a credential, it is your own, kept in your Workspace.
| Service | What happens | Notes |
|---|---|---|
| Facebook and Instagram (Meta) | If you connect your own business pages, the social media tools publish the posts, photos and videos you approve. These tools belong to the Business Development module, which is switched off for every plan when sign-up opens. | Under Meta's own terms for publishing, as MVV read them on 10 September 2026, Meta acts as a controller in its own right, not as a processor for you or for MVV. |
| Calendar feeds (Google Calendar, Apple iCloud) | If you paste a private calendar link, your Workspace reads that feed. | |
| Your own WhatsApp Business number (Meta) | Not offered. A Workspace sends WhatsApp only through MVV's shared number (A10): its WhatsApp settings screen says there is nothing to connect and has no field for a token, and the underlying app's own WhatsApp connection is hidden. | |
| Your own Google account for the Contract Helper | An advanced option inside the Contract Helper, where your Workspace has it: the Contract Helper can read case emails from your Gmail, using a Google set-up of your own. | MVV's own Google set-up is not used for this. |
| Public data services | Look-ups that need no key: UK postcodes (postcodes.io), planning applications (PlanIt and council planning portals), UK law and guidance (legislation.gov.uk, National Archives case law, BAILII, the Judiciary, GOV.UK, HSE, ICO, Parliament, ACAS). | The query (for example a postcode or search words) goes to the service, with no account of yours or MVV's. |
C. Used only for MVV's own business
These are covered by the Privacy Policy, not the DPA.
- Companies House: the public register of UK companies. Before MVV builds a Workspace ordered on the sign-up page, MVV support checks the company on the register by hand, and it checks there, by hand, a change a paying customer makes to its registered name or company number. It receives the company number we look up.
- Resend: MVV's own emails: welcome and account emails, the monthly commission statements MVV sends its sales agents and the one-time links that set up their sign-in, all from
sales@mvvtechnologies.com; the six-digit codes MVV ID sends to a person finding their company from MVV's phone app; and the control console's operational alerts to MVV support. The alerts name customer Workspaces and their problems and, for a paying customer, each change it makes to its registered name, company number, registered office, invoice email and website (in full) and VAT number (its last three digits). They go fromnotifications@mvvtechnologies.comto a mailbox on an affiliated business's domain, run on Google Workspace. - Cloudflare: Email Routing for MVV's own inboxes. Mail to MVV's own addresses (for example
support@,privacy@andsales@mvvtechnologies.com) is forwarded to a mailbox on an affiliated business's domain, run on Google Workspace, so that mailbox, and Google as its host, receive every email you send us. Cloudflare also serves MVV's status page,status.mvvtechnologies.com, which names no Workspace, and sees the IP address of each visitor to it. It carries the agents' site's requests to MVV's agents' service, with the agents' sign-in cookie and their network address, including the contact details agents record and, when an agent signs the agent agreement, the selfie, the signature and the name, while they travel; it carries the questions MVV's staff type to Ask Control on their way to OpenAI, through MVV's gateway addressgw.mvvtechnologies.com; and it limits how many requests one network address can make. - Google (Google Workspace): the mail host of that mailbox, which receives MVV's own mail and the control console's alerts. The affiliated business that holds the mailbox has accepted Google's Cloud Data Processing Addendum for its Google Workspace account, naming the UK Information Commissioner as the supervisory authority.
- Google (Google Analytics): counts visits to MVV's main website,
mvvtechnologies.com(which forwards tomvvtech.solutions), only after a visitor presses "Accept" on its cookie banner. - An affiliated business: runs MVV's main website (
mvvtech.solutions, served by Netlify from that business's own account) and receives what is sent on its contact form in its own Supabase project. - Netlify: serves MVV's help pages,
help.mvvtechnologies.com, where this list is published, and sees the IP address and browser details of each visitor; serves MVV's agents' site (agents.mvvtechnologies.com). - Supabase: MVV's control database, in London, MVV's own server functions named in A1, and MVV's agents' service. The agents' service signs MVV's sales agents in on the agents' site and seals and opens the contacts they record, in memory only; the contacts are stored encrypted in MVV's control database in London, and the service's logs record the caller's network address. It also seals each signed agent agreement (a selfie holding photo ID, a drawn signature, the signer's name and the evidence of signing) for MVV's own computer, which alone can open it, and holds the sealed copy in MVV's control database in London until MVV's computer collects it, at most 14 days.
- OpenAI: answers the questions MVV's own staff type to Ask Control, the assistant in MVV's control console, with its gpt-4.1-mini model, through MVV's gateway on MVV's own key. Each request holds the question, excerpts from MVV's own manual for its staff and short readings built from Workspace short names, ids, kinds, counts and dates; never a person's name or free text from a Workspace. MVV's records of each call hold counts and ids, never the question or the answer. Ask Control's voice is not switched on.
D. Planned, or starting when sign-up opens
The rows marked "until sign-up opens" start on that day. Two rows also serve MVV's "I'd like to join" page (signup.mvvtechnologies.com/join.html), from the day that page opens: Cloudflare Turnstile, and Netlify and Cloudflare. They are for MVV's own business (selling to you and billing you), so, like Section C, they are covered by the Privacy Policy, not the DPA. The last three rows are not in use.
| Provider | Use | Status |
|---|---|---|
| Stripe | Card payments and Bacs Direct Debits (set up and collected) on Stripe's own pages, your subscription, the invoices and receipts Stripe emails, and the payment page that the "Buy more AI" button in your Workspace opens. | Built, not in use for customers until sign-up opens. The webhook that records Stripe's events in MVV's control database has been in place since 29 September 2026. Until MVV switches Stripe to real payments for the opening of sign-up, it runs in Stripe's test mode only: it takes Stripe's test events, and an event from a real payment is refused and not recorded. When sign-up opens, Stripe holds the buyer's email, billing address, VAT number if given, and card and, once a Direct Debit is set up, the bank account and the Direct Debit mandate. For an invitation, the details attached to the order are only MVV's order reference and the Workspace's name; for an order made on MVV's public sign-up form, if MVV opens it, they are the company's registered name, number and office, its trading name, the account owner's name and role, the Workspace's name and, if given, the contact person's name and phone. A payment made from the "Buy more AI" button tells Stripe your Workspace's short name, so that MVV knows which Workspace the AI is for. MVV's control database keeps Stripe's ids, amounts, dates and statuses only and, for a card dispute, Stripe's words for its status and reason, and, for a payment for more AI, your Workspace's short name and the payment link's id; never the buyer's name, contact details, address, VAT number or card. |
| Cloudflare Turnstile | The check that a visitor is a person, on the "I'd like to join" page (join.html) and on the sign-up page. | On the "I'd like to join" page, in use from the day that page opens. On the sign-up page, not in use for customers until sign-up opens. Turnstile reads the visitor's browser signals and IP address to make its check. |
| Resend (sign-up codes) | The sign-up page's email code, sent through MVV's gateway as "MVV Technologies" from notifications@mvvtechnologies.com. | Built, not in use for customers until sign-up opens. |
| Netlify and Cloudflare (the sign-up page) | Netlify serves the sign-up site, signup.mvvtechnologies.com, with its "I'd like to join" page. What is typed on it goes to MVV's sign-up service, a server function at Supabase (A1), through the gateway address at Cloudflare (A2). A request to join is sealed there so that only MVV's own computer can read it, before it is stored. Each of them sees the visitor's IP address. Cloudflare counts the requests each network address sends to the sign-up service and blocks an address for a short time when it sends too many. The sign-up service does not look the company up anywhere: MVV checks it by hand on the public register at Companies House before it builds the Workspace (section C). | In use for the "I'd like to join" page from the day that page opens. Otherwise built, not in use for customers until sign-up opens. |
| OVHcloud (OVH Limited, company 05519821) | A server in London to run the control console, the nightly backups, the health monitor and the 90-day deletion job. It will hold every Workspace's keys, database passwords and backup keys, paying customers' company details, and the working copies made during backups, restore tests and exports. The server has two accounts: the backup keys, the public half of MVV's master backup key and the sealed key copies (including those of each Workspace's key for its stored connection passwords) are readable only by the account that runs the backups. OVH's daily backups of the server, kept 7 days, will hold all of this too; they are stored by OVH, and their location is being confirmed with OVH in writing. OVH group companies in the EU and Canada may access the server to give support (UK adequacy). | Planned, not in use. The server was ordered on 28 September 2026 and delivered on 29 September 2026, and is being set up from MVV's server kit. The control console, the backups and the other work above still run on MVV's own computer and have not moved to it. We will publish a new version of this list before they do. |
| PostHog | Product analytics. | Not installed. MVV's own rules keep it out until its data protection questions have been answered. |
| Anthropic (the Legal Tracker, in MVV's control console) | For MVV's own business: drafting and checking MVV's own agreement packs, and reading the replies to them, with Claude models through MVV's gateway. | Built, not in use. Before it is used, this list and the Privacy Policy will say exactly what it sends. |
E. Blocked by the platform
Each Workspace's outbound guard refuses calls to the known AI services that are not listed above, including Higgsfield, and to every sub-domain of them. A feature that relied on one of them does not work in a Workspace.
Changes to this list
We will give notice of a new sub-processor, or of a change to what an existing one does, at least 30 days before the change takes effect, by email to the account owner. You may object as set out in clause 7 of the DPA. Each change is published as a new dated version of this page.
| Date | Change |
|---|---|
| 13 October 2026 | First published version. |