Legal•Business

HomeOrbit Subprocessor Schedule

Current infrastructure and support providers used in connection with HomeOrbit.

Version 2.0
Updated 29/09/2026

View published versions

1. Scope

This schedule identifies providers used by Joshua Roberts trading as HomeOrbit for the services described below. A provider acts as a subprocessor where it handles Customer Personal Data on our instructions; some account, billing and security activities have separate controller roles under its terms. Read this alongside the DPA and Privacy Notice.

The list describes actual integrations and verified configuration, not a certification of every supplier contract. Exact contracting entities, account settings, onward providers, retention and applicable transfer safeguards must be checked against the service agreement for each account. Contact support@homeorbit.co.uk for the relevant information.

2. Supabase

Function: managed Postgres database, authentication, file storage and associated platform services.

Information: customer operational/care/HR records and files, account and authentication information, permissions and technical metadata.

Location: the HomeOrbit project dashboard showed London (eu-west-2) on 29 September 2026. Regional database storage does not necessarily restrict all account, support or other processing to that location.

Provider DPA and region information.

3. Vercel

Function: application hosting, server functions, delivery network, deployment and operational logs.

Information: requests and responses processed by the application, account/session metadata, uploaded content in transit where handled by a route, and technical logs.

Location: the HomeOrbit project dashboard showed function region London (lhr1) on 29 September 2026. Delivery networks, account/support systems and subprocessors can involve other countries, including the United States. A project setting is not a blanket UK residency guarantee or proof of every existing deployment's location.

Provider DPA and function regions.

4. Sentry

Function: application error/security diagnostics and, with a separate browser choice, browser error/performance diagnostics.

Information: filtered error and performance information, relevant technical metadata and identifiers where necessary. Filtering reduces personal data but does not warrant complete anonymisation. No browser session replay is configured.

Location: the application uses Sentry's Germany/EU ingest endpoint. Account, support and authorised onward processing may have different locations; verify the organisation's region and contractual scope.

Provider DPA and data storage locations.

5. Resend

Function: transactional email, including authentication, account setup/recovery and enabled operational notifications, reminders and cover/calendar messages.

Information: recipient email addresses, message content, sending details, delivery status and related technical metadata. Operational messages can contain names, dates and notification text, not just email addresses.

Location: Resend states that its data, including email content and logs, is stored in the United States. Choosing a sending region does not itself change storage residency.

Provider data protection information and DPA.

6. OpenAI

Function: optional software-use help assistant through the OpenAI Responses API.

Information: user-entered questions, limited recent chat context, current page path and selected help-guide extracts. The integration does not retrieve live care or personnel records. Users must not enter confidential case details.

Location and retention: the reviewed code uses the general API endpoint; it does not establish European residency or approved Zero Data Retention. Requests set store:false, but provider abuse-monitoring and legally required retention can still apply. API training is off by default under provider policy unless the account opts in; HomeOrbit does not authorise training on Customer Personal Data.

Provider data controls and DPA.

7. Changes and safeguards

The DPA requires advance notice of additions/replacements, an opportunity to object and equivalent Article 28 obligations. Restricted transfers require an applicable mechanism and assessment; provider availability of contractual terms or certification is not evidence that the relevant HomeOrbit account has completed all necessary arrangements.

We will identify material changes to customer contacts before use as required by the DPA. Ordinary support emails, downloaded files and links chosen by users can involve recipients outside this supplier list; organisations remain responsible for their own authorised sharing.