1. Scope and contact
HomeOrbit is operated by Joshua Roberts trading as HomeOrbit, Apartment 414, 35 Greenland Street, Liverpool, L1 0AD, United Kingdom. Contact support@homeorbit.co.uk for support or security reports. Use “Security” in the subject for suspected compromise, but do not send credentials or confidential care files in ordinary email. Agree a suitable secure channel when necessary.
This policy supports the Platform Terms and DPA. It is not an independent security certification, a guarantee of uninterrupted operation or a 24-hour emergency response service.
2. Technical controls
The application uses authenticated accounts, server-side application-session and recovery checks, role/company/home scoping, module permissions and database row-level security. Privileged service operations must check requester scope. Relevant workflows maintain action, approval and acknowledgement evidence.
HTTPS protects traffic in transit. Managed hosting/database/storage providers supply infrastructure controls; their current encryption, backup, access and region settings must be verified for the deployed accounts. Private files use appropriate scoped access where implemented. Public profile avatars and public site assets are separate and must not contain confidential records.
The product contains MFA and trusted-device functionality. Enforcement depends on deployment/account configuration; availability must not be represented as universal mandatory MFA. Shared devices need appropriate locks, sign-out and device controls.
Security and diagnostic filtering aims to remove credentials, request bodies and record content from telemetry. Optional browser diagnostics require a separate choice. No browser session replay is configured. Server-side operational/security monitoring is separate.
3. Organisational controls and customer duties
Access should be restricted to authorised people with confidentiality duties and the minimum necessary permissions. Software and dependencies need maintenance, changes need review and security incidents need investigation. Operational procedures, supplier agreements, backup restoration exercises and evidence of these activities must be maintained alongside code.
Customers must configure permissions carefully, remove obsolete accounts, protect devices/downloads, train users, maintain lawful instructions/retention policies and report suspected compromise. These responsibilities do not remove HomeOrbit's obligations.
4. Availability, backups and continuity
During pilots, support is on a reasonable-endeavours basis during normal UK business hours, unless an agreed written support arrangement says otherwise. No uptime percentage, response-time SLA or service credits apply unless expressly agreed. Planned maintenance should be notified where practicable; urgent security work may need immediate action.
Backups and recovery depend on configured supplier plans and procedures. No particular recovery point/time objective or backup retention period is promised without written agreement and verification. Customers must maintain suitable care/business continuity arrangements and an emergency process independent of HomeOrbit. Do not use support or the help assistant as an emergency or safeguarding escalation channel.
5. Incidents and vulnerabilities
Report the affected function, time and minimal reproduction details. Do not access other people's records to prove a flaw, run disruptive tests or publish confidential information. We will assess and prioritise reports according to their impact and take appropriate containment and remediation steps.
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. Details may follow in phases. The DPA sets assistance and information requirements. The controller remains responsible for its statutory ICO/individual notifications; where HomeOrbit is controller, it is responsible for its own duties.
6. Support, changes and AI
Support may require narrowly scoped authorised access. Supply the minimum information needed and agree secure sharing for sensitive material. AI help is optional software guidance, can be wrong and must not receive confidential case records. Human review remains necessary.
Material service/policy changes and supplier changes follow the contract and DPA notice processes. We can provide proportionate compliance information and participate in required audits without exposing other customers' information or weakening security.
