Revision of November 17, 2026: aligned to the supplier and support processing chain in Schedule 3 of the Data Processing Addendum Version 1.3. Previous revisions: Sub-processors, November 2, 2026 · Sub-processors, October 19, 2026 · Sub-processors, October 6, 2026 · Sub-processors, September 30, 2026.
How to read this list
This page is informational. It reproduces the generic supplier and support processing chain in Schedule 3 of the Data Processing Addendum Version 1.3. It does not itself authorise a sub-processor, start any processing, grant any person access, or amend any agreement. What governs a customer is the processing actually ordered, the DPA that customer accepted, its authorisation and change-notice process, and the lawful transfer route recorded for the ordered service. Orders that incorporate an earlier DPA version continue under that version.
Locations include storage and potential remote processing; they are not access assignments. Optional processing occurs only for the service actually enabled or used. Listing a provider does not mean it is active for every customer.
1. Core hosting suppliers
SG Systems’ direct contracting parties for the hosted service. Backup and recovery are summarised in the Security & Trust reference.
| Party or route | Service and role | Location and qualification |
|---|---|---|
| Supabase Pte. Ltd. | Direct SG database, Auth and Storage supplier under the verified organisation purchase and terms route. AWS is downstream, not a direct SG engagement merely because Supabase uses it. | London for the UK/Europe core profile; Oregon for other-region and existing HiVE support database. Contracting-entity domicile is distinct from selected hosting. |
| Google LLC | Hosted application, independent backups/archives, infrastructure logging and control plane. | London core profile; Oregon HiVE application and other-region application; US multi-region copies for other-region profile. Required global audit and final deletion exceptions are in DPA Schedule 1. |
2. Email, AI, SMS and gateway — only when used
| Party or route | Service and role | Location and qualification |
|---|---|---|
| Plus Five Five, Inc. trading as Resend | Transactional and sign-in mail under the company-authorised account and supplier DPA. | US content and log handling. A UK sender or callback does not regionalise the supplier’s stored content. Upstream 30-day change rights must be coordinated. |
| OpenAI OpCo, LLC — when AI is used | Model processing under the company API account and applicable standard terms/DPA. | United States/global processing and standard supplier retention; optional sharing is disabled for the identified company account. No European-only or zero-retention commitment unless separately agreed. |
| Google Gemini Developer API — when used | Optional model processing through the verified SG project/billing correspondence and separately applicable terms. | Applicable model and terms govern processing and retention. Google Cloud CDPA acceptance alone is not Gemini Developer API evidence. |
| Twilio — when SG engages or instructs it | Enabled SMS and associated delivery metadata under actual account/terms. Customer-direct contracting is classified separately. | The identified route is us1. Actual per-item deletion and supplier residue follow the applicable terms; shared settings alone do not establish customer-specific purge or Europe-only processing. |
| Lovable Labs Inc. — where the actual feature routes through it | Gateway or other processing only to the extent Customer Personal Data actually traverses the enabled service. It is not used as a substitute name for Resend or the model supplier. | United States/global. The applicable gateway, legal counterparty and terms must match the enabled feature before processing begins. |
3. SG-operated HiVE support route
The existing SG HiVE support route is operated by SG Systems; it is not a separate third-party supplier. It handles SG-operated support, messages, chats, attachments, selected workspace/user context and diagnostics; underlying suppliers remain those identified above. Location: United States, including Oregon database and us-west1 application. It is a separate copy and access route from London hosting.
4. Independent controllers and customer services
Paddle’s merchant-of-record billing is treated according to its independent controller role and Data Sharing Addendum, not as processing manufacturing records for SG. Customer-directed identity providers, integrations and a genuinely Customer-direct Twilio relationship follow their actual contracts and instructions. A billing webhook, credential owner or commercial reseller label alone does not establish the legal role.
5. Support providers
Before a support provider processes a customer’s data, the applicable named-recipient schedule must identify the legal party, named operator where relevant, task, workspace, approved working country, period, safeguards and lawful onward route. That named schedule is controlled and is disclosed through a controlled channel where required; it is not published here. Reported working locations do not themselves authorise access for a customer or establish a lawful transfer route.
Development tools
GitHub, Inc. stores the V5 Ultimate source code and records code review and release approval. It is not where the cloud service or tenant data is hosted, and it is not listed as a customer-data supplier on the basis of holding our source code.
On-premises deployments
For On-Premises services, the customer is responsible for its infrastructure; support materials SG Systems receives remain subject to the applicable DPA duties and finite retention.
Changes to this list
Changes to the actual sub-processors for an Order follow the authorisation and change-notice process in the DPA that Order incorporates. A route with unresolved eligibility, terms or safeguards must not be enabled for a customer. Inclusion on this page does not grant a person access or establish that supplier final deletion has occurred.
Subscribe to updates
To receive email notifications when this page changes, use our .
See also our Privacy Notice, Trial and Evaluation Terms, Imprint, and Accessibility Statement.
