1. Parties, scope and priority
This DPA forms part of the agreed contract between the Customer organisation and Joshua Roberts trading as HomeOrbit, a UK sole trader of Apartment 414, 35 Greenland Street, Liverpool, L1 0AD, United Kingdom; support@homeorbit.co.uk.
“Data Protection Law” means the UK GDPR, Data Protection Act 2018, PECR where applicable, and applicable amendments. Controller, processor, personal data, processing and personal data breach have their meanings in that law. “Customer Personal Data” is personal data processed on the Customer's behalf in providing the Services.
The Customer is normally a controller and HomeOrbit its processor. Where the Customer is itself a processor, it must have the controller's authority to appoint HomeOrbit as a subprocessor and pass on lawful documented instructions. This DPA applies to that chain accordingly. Independent controller activities described in our Privacy Notice are separate and do not permit independent reuse of care or employment records.
This DPA prevails over conflicting service terms on data protection. It does not limit statutory rights, regulatory powers or liabilities that cannot lawfully be limited. An ordinary user's acknowledgement does not give them authority to amend the Customer's processing contract.
2. Documented instructions
HomeOrbit will process Customer Personal Data only on documented instructions, including for transfers, unless UK law requires otherwise. If law requires processing outside those instructions, HomeOrbit will inform the Customer before processing unless that law prohibits this on important public-interest grounds.
The agreed contract, this DPA, authorised configuration and permitted user actions form the initial instructions. Material changes to purposes, categories or permitted processing require written agreement. HomeOrbit will immediately inform the Customer if, in its opinion, an instruction infringes Data Protection Law and suspend the affected instruction while resolved. General service-improvement wording does not authorise AI training or independent reuse of Customer Personal Data.
3. Confidentiality and security
Authorised persons must commit to confidentiality or be under an appropriate statutory obligation. Access must be limited to authorised duties.
HomeOrbit will implement measures required by Article 32, considering the state of the art, costs, nature, scope, context, purposes and risks to people, including vulnerable children. Schedule 3 describes service measures. Changes must not materially reduce the agreed overall protection. Customer responsibilities for users, devices and access configuration do not remove HomeOrbit's own obligations.
4. Subprocessors
The Customer gives general written authorisation for providers in the Subprocessor Schedule for the described functions. Before adding or replacing a provider processing Customer Personal Data, HomeOrbit will give the designated customer contact at least 30 days' written notice, describing the provider, purpose, location information and safeguards, and an opportunity to object on reasonable data protection grounds before the change.
The parties will work to resolve objections, including a reasonable alternative or discontinuing the affected optional function. If unresolved, the Customer may terminate the affected service before the change without termination penalty and receive a refund of prepaid unused fees for it. If urgent security/legal necessity requires shorter notice, HomeOrbit will provide as much advance notice as reasonably possible and preserve objection and a lawful alternative or exit; urgency does not waive lawful-processing requirements.
Each subprocessor must have a binding contract imposing the same data protection obligations required by Article 28 for the processing concerned, including sufficient guarantees for appropriate measures. HomeOrbit remains fully liable to the Customer for performance of those obligations. Provider marketing statements do not replace these contracts.
5. International transfers
Restricted transfers require documented instructions and compliance with Chapter V. Where necessary, this includes an applicable adequacy regulation or safeguards such as the UK IDTA or UK Addendum, required transfer assessment and supplementary measures. HomeOrbit will provide relevant location, onward-transfer and safeguard information on request, subject to proportionate confidentiality protections.
A UK/EU hosting region does not remove the need to assess overseas support, network processing and other providers. HomeOrbit must verify that a mechanism covers the actual recipient and processing. This DPA does not itself execute third-party transfer paperwork.
6. Assistance and rights
Taking account of the processing, HomeOrbit will assist through appropriate technical and organisational measures, insofar as possible, with individuals' rights requests. It will promptly notify the Customer of requests concerning Customer Personal Data and will not decide the substantive response without instructions unless law requires it.
Taking account of the processing and information available, HomeOrbit will assist with Articles 32 to 36: security, breach assessment/notification, DPIAs and prior consultation. It will supply relevant information in time for applicable deadlines. Any agreed reasonable assistance charges must not prevent or improperly delay statutory compliance.
7. Personal data breaches
HomeOrbit will notify the Customer without undue delay after becoming aware of a personal data breach affecting Customer Personal Data, without waiting for a complete investigation. Information can follow in phases without undue further delay.
As available, notification will include the nature of the breach, categories and approximate numbers of people and records, contact details, likely consequences, measures taken/proposed and mitigation. HomeOrbit will preserve relevant evidence, investigate and cooperate. The Customer remains responsible for its notifications to the ICO and people affected, with HomeOrbit's assistance. HomeOrbit will not speak on the Customer's behalf without authority unless law requires it.
8. Return, deletion and backups
At the end of the Services, HomeOrbit will, at the Customer's choice, return or delete Customer Personal Data and delete existing copies unless UK law requires storage. The normal 30-day export window facilitates that choice; it does not override lawful earlier deletion instructions or statutory rights. If no different instruction is received, deletion follows that window. Payment disputes do not authorise withholding assistance required by data protection law.
Residual backups must be beyond ordinary use, protected and deleted/overwritten within the applicable documented backup lifecycle. Restores must reapply deletions before ordinary use. HomeOrbit will identify that lifecycle and confirm completion on reasonable request. Backups must not become indefinite archives. Legally required retention must be identified where permitted, isolated and used only for that requirement. General commercial convenience or unspecified dispute concerns do not create unrestricted processor retention rights.
9. Information and audits
HomeOrbit will make available all information necessary to demonstrate Article 28 compliance and allow for and contribute to audits, including inspections, by the Customer or its mandated auditor. Documentation and remote review may be used first where sufficient. Reasonable notice, confidentiality, security, timing and scope arrangements protect other customers and avoid unnecessary disruption; they must not frustrate statutory audit rights, urgent investigation or supervisory authority access.
10. Customer responsibilities
The Customer must have authority, give privacy information, identify lawful bases and sensitive-data conditions, maintain appropriate records, configure access/retention and assess risks. It must not put unnecessary sensitive information in public avatars, email-visible text or help questions. It must assess high-risk care processing and supervised children's activities, including DPIA and Children's Code obligations where applicable.
11. Liability, duration and law
The main contract's lawful liability provisions apply between the parties, without restricting individuals' rights, ICO powers or liabilities that cannot lawfully be restricted. This DPA continues while HomeOrbit or its subprocessors hold Customer Personal Data. England and Wales law and courts apply subject to mandatory law.
Schedule 1. Processing details
Subject matter and purpose: provision of the Customer's care-operations service, including storage, permissions, records, forms, scheduling, medication/HR administration, communications, supervised activities, security, support and exports on instructions.
Duration: the service term and limited instructed return/deletion period and documented protected backup lifecycle, unless UK law requires further storage.
Nature: collection, recording, organisation, storage, retrieval, viewing, updating, workflow/status calculations, authorised sharing, transmission, export, restriction and deletion. Optional AI help sends user-supplied questions and limited context to its named provider; this is not a general instruction to disclose care records or train models.
Schedule 2. People and data
People: staff, workers, agency/bank staff, managers, applicants, contractors, young people/service users, family/emergency contacts, professionals, training providers, organisational contacts and others lawfully included in records.
Data: names, contacts, roles, identifiers, memberships; employment, attendance, rotas, timesheets, leave, training/certificates; policies, forms, signatures and audit evidence; payroll/payslips; care, medication, safeguarding and contact records; budgets/receipts; attachments, photographs and media; access/communications records; supervised game progress and virtual inventory.
Sensitive categories: health, disability, medication and other special category information where entered, plus DBS/criminal-offence data where lawful. Narratives can reveal additional sensitive categories. Additional material categories/conditions must be specified before changing the agreed processing.
Schedule 3. Measures
- Authenticated accounts, server session/recovery checks, company/home/role scope controls and database row-level security.
- Feature permissions, restricted administrative/service credentials and scope checks for privileged actions.
- HTTPS and managed database/storage infrastructure. Supplier encryption, backup settings, regions and access arrangements require verification for the deployed service.
- Private attachment controls where applicable; public avatars/assets are separate and must not contain confidential records.
- Audit/acknowledgement evidence for relevant workflows and filtering to reduce credentials/record content in diagnostic reports.
- Code/dependency maintenance, incident response and assistance with rights, exports and deletion.
- MFA/trusted-device functionality where enabled. Its availability is not a promise that every deployment/account enforces MFA.
- Separate optional-browser-diagnostics choices and no configured browser session replay; confidentiality and minimum necessary support access.
This summary is not independent security certification or a promise that risk is eliminated. Supporting operational evidence must be maintained alongside the software.
