Personal data

Subprocessor Register and International Transfers

In force from 20 September 2026. Version 2026-09-20.

1. Purpose and scope

TrueValue Technologies Ltd, company number 17462580, of 66 Paul Street, London, England, United Kingdom, EC2A 4NA, maintains this register to identify external organisations processing Customer Personal Data in the delivery of TrueValue. Questions and subprocessor objections should be sent to privacy@truevalue.business.

This register forms Schedule 3 to our Data Processing Agreement (DPA) when completed and incorporated into the customer agreement. It distinguishes TrueValue-appointed subprocessors, providers used for our independent controller processing, and services selected directly by a customer. A provider can have different roles for different processing; the relevant activity, not the brand name alone, determines the role.

2. Appointed subprocessors

Provider and legal entityInstructed service and data involvedProcessing, access, retention and safeguards
Supabase, Inc. (United States, operated from Singapore)The database, authentication, file storage and serverless functions the Service runs on: account identifiers, documents and their extracted text, database records and the request logs those functions write, which is every category of Customer Personal Data the Service holds.Database, file storage and daily backups in Amazon Web Services' London region (eu-west-2); each backup deleted seven days after it is taken; platform request logs kept seven days; uploaded files not included in backups. The functions run on Supabase's global edge network, closest to the requester, and hold data only in memory for the duration of a request. Support staff access the project on our request. Cloudflare, Inc. (United States) sits in front of the Supabase API as Supabase's own sub-processor and sees IP addresses and request metadata. Contract: Supabase's Data Processing Addendum, incorporating the EU Standard Contractual Clauses and the UK International Data Transfer Addendum.
Lovable (Lovable Labs Incorporated, United States, with engineering in Sweden)Hosting and delivery of the web application at truevalue.business (request metadata only: IP address, browser and pages requested; no Customer Data content passes through it, since the browser talks to Supabase directly); the AI gateway through which model requests — prompts, extracted document text, context and outputs — are relayed to the model provider; and the connector gateway through which web-page fetches and searches for company research are relayed.Processing under Lovable's data processing terms, which govern its own logs and the safeguards for access from outside the United Kingdom. Lovable engages Google (next entry) as the model provider behind the gateway.
Google LLC (United States), engaged by Lovable as its sub-processor for the Gemini modelsThe prompts, extracted document text, context and outputs relayed through the AI gateway: CIM screening, financial-statement extraction, valuation narrative, document drafting, the copilot and the Agent.Google's Gemini API terms for paid use: prompts and responses are not used to improve Google's models and are logged for a limited period solely to detect abuse (55 days at the date of this register). Access from outside the United Kingdom is covered by Google's data processing terms incorporating the Standard Contractual Clauses.
Resend (Plus Five Five, Inc., United States)Delivery of every email the Service sends, including email a customer instructs us to send: recipient addresses, subject, body (which may carry Customer Data the customer chose to include), attachments and delivery events.Processed on Resend's infrastructure in the United States; message content and delivery logs kept for Resend's operational retention period so that delivery can be traced, then deleted. Contract: Resend's Data Processing Agreement, incorporating the EU Standard Contractual Clauses and the UK Addendum.
Firecrawl (United States), engaged through Lovable's connector gatewayPublic web pages fetched for the market-listing feed and for researching a target company: the page addresses, the search terms (a company's name and registered number) and the page content returned, which may name the people on those public pages.Processed in the United States under Firecrawl's terms of service and the Lovable connector arrangement. Only public pages are read; nothing from a customer's workspace is sent.
Twilio Inc. (United States)SMS one-time codes, only where a sender selects SMS identity verification for a signing workflow: the signer's mobile number and the code.Processed in the United States under Twilio's Data Protection Addendum; message logs kept for Twilio's retention period.

The completed register records the legal entity, service description, data categories, primary processing location, relevant overseas access, retention or deletion cycle, and applicable safeguard for each provider. Where a supplier offers different processing arrangements, the entry must describe the arrangement TrueValue actually uses.

Configured alternatives, not in use for Customer Personal Data: OpenAI, L.L.C. (United States), the fallback route if the AI gateway is unavailable, and Anthropic, PBC (United States), available to one internal drafting tool. Each is covered by its published API data policy (no training on API data; abuse-monitoring retention of up to 30 days) and its data processing addendum. If either becomes the route for customer data, that is a subprocessor change notified under section 5.

Public registers we read — Companies House, the Global Legal Entity Identifier Foundation and the other national registers named in the product — receive only the search terms and identifiers needed to look up a company. They are sources, not processors of Customer Personal Data. No error-tracking or session-recording service is active.

3. Other recipients and distinct roles

Payment services: Stripe was identified in our published service documents. The final entry must identify the actual Stripe contracting entity and explain its roles for the deployed payment service. Payment details, billing contacts, transaction records and fraud-prevention information are not automatically processed as a subprocessor of the customer's deal workspace. Where the provider acts as an independent controller, its own privacy information applies to that activity; where it processes for TrueValue's controller purposes, TrueValue remains responsible for that relationship.

Stripe entry: our payment services are provided by Stripe Payments UK, Ltd. (registered in England and Wales and authorised by the Financial Conduct Authority as an electronic money institution), part of the Stripe group, and card details are entered on Stripe's own checkout pages, never on ours. Stripe processes cardholder details, billing contacts, transaction records and fraud-prevention signals as an independent controller for the payment, fraud prevention and its own legal obligations, under Stripe's privacy policy at stripe.com/gb/privacy, and holds the customer and subscription records it keeps for us under the data-processing terms of the Stripe Services Agreement. Data is processed in the United Kingdom, the European Union and the United States under Stripe's own transfer arrangements, and transaction records are retained for the periods Stripe's legal obligations require.

Advertising measurement: Meta Platforms Ireland Limited and OpenAI's ChatGPT Ads measurement service receive only the advertising events described in the Cookie Policy's inventory after a visitor accepts advertising, under each provider's applicable advertising and privacy terms. No website analytics service other than our own first-party measurement, described in the same inventory, is used.

Customer-selected integrations: an email account, storage service, CRM or external AI client independently selected and connected by a customer may receive information on the customer's instructions under a separate relationship. These providers are not automatically TrueValue-appointed subprocessors. The customer must review permissions and the provider's terms. A TrueValue-selected supplier cannot avoid subprocessor obligations merely by being labelled an integration.

Professional advisers, authorities and other occasional recipients are described in the Privacy Notice where relevant. They are not all ongoing subprocessors of Customer Personal Data.

4. International transfers

A processing location is not the same as a company's headquarters. A local database region does not exclude overseas support access, replication, logging, communications or AI processing. We identify relevant destinations rather than simply listing the country where a supplier was incorporated.

For each restricted transfer, we document the lawful mechanism and required assessment. Depending on the circumstances, this may involve an applicable adequacy arrangement, the UK International Data Transfer Agreement, the UK Addendum to the EU Standard Contractual Clauses, or the EU clauses for processing subject to EU GDPR. An applicable certification or framework is relied upon only after checking the exact entity, scope and current validity.

Listing a possible mechanism in a policy does not execute it. Required instruments and annexes must be in place before the transfer. We review material changes affecting protection and take appropriate action if a mechanism is no longer valid. Customers may request relevant safeguard information from privacy@truevalue.business, subject to necessary confidentiality redactions.

5. Supplier changes and objections

We give at least 30 calendar days' notice to the nominated customer contact before adding or replacing a subprocessor for that customer's processing, as set out in the DPA. The notice identifies the new entity, purpose and relevant locations. Keep your administrative contact details current.

A customer may object within that period on reasonable data-protection grounds. We consider the concern, provide information and seek a reasonable alternative or appropriate restriction. A timely unresolved objection is handled under the DPA, including termination of the affected service with a pro-rata refund of prepaid unused fees where no reasonable solution is available. We do not treat silence as permission for an undisclosed new processing purpose.

6. Version history and requests

The publication date identifies the register version. We retain prior versions so a customer can establish the suppliers applicable to its agreement and subsequent changes. Requests for a signed DPA, supplier information or a change-notification contact should be sent to privacy@truevalue.business.