Halo Support Ltd - Data Processing Agreement

1. About this agreement

This Data Processing Agreement ("DPA") sets out how Halo Support Ltd handles personal data on behalf of its clients. It forms part of the Halo Support Ltd Terms and Conditions (www.halo.support/termsandconditions) and applies automatically when a Client places an order for any Service listed in the Schedules.

Version 1.0, November 2026.

Halo Support Ltd ("Halo", "we", "us")
Registered address: 40 Brondeg, Heolgerrig, Merthyr Tydfil, CF48 1TW
Company number: 11983639
ICO registration: ZA309434
Data Protection Officer: Tom Lewis, tom@halo.support, 07446 975496

The Client ("you"): the school, organisation or business named on the order.

1.1 This DPA only applies to the Services the Client has bought. Each Schedule describes one Service and applies only if the Client uses that Service.

1.2 If anything in the Terms and Conditions conflicts with this DPA on data protection, this DPA wins.

1.3 The Halo Sign-in System Data Handling Document explains in more detail how the Halo Sign-in System works. It is guidance and does not override this DPA.

2. Definitions

TermMeaning
Data Protection LegislationThe UK GDPR, the Data Protection Act 2018 and any other UK law on personal data that applies, as amended from time to time (including by the Data (Use and Access) Act 2025)
Controller, Processor, Data Subject, Personal Data, Processing, Personal Data BreachHave the meanings given in the UK GDPR
ServicesThe products and services Halo provides to the Client, as described in the Schedules
Client Personal DataPersonal Data that Halo processes on the Client's behalf while providing the Services
Sub-processorAnother company Halo uses that processes Client Personal Data
Authorised ContactA member of the Client's staff who is allowed to give Halo instructions, such as the head teacher, business manager, office manager or Data Protection Officer

3. Roles and responsibilities

3.1 For Client Personal Data, the Client is the Controller and Halo is the Processor.

3.2 Halo is a Controller, not a Processor, for its own business data. This includes client contact and billing details, and the names and feedback of people who attend Halo training. That data is covered by Halo's privacy notice at www.halo.support/gdpr, not by this DPA.

3.3 The Client is responsible for:

  1. having a lawful basis for the personal data it collects, and telling Data Subjects how it is used (for the Halo Sign-in System, this includes checking and, if needed, editing the "About data collection" text in the Halo App);
  2. deciding which fields, questions and custom questions are switched on, and making sure they are relevant and limited to what is necessary;
  3. setting data retention periods in line with its own retention policy;
  4. keeping its own devices, passcodes, admin credentials and QR codes secure, and choosing who can see the data;
  5. making sure exports and reports are only sent to email addresses the Client controls, and deciding how long exports are kept in any Gmail account used to send them;
  6. making sure any instruction it gives Halo is lawful.

4. What Halo commits to

4.1 Instructions. Halo will only process Client Personal Data on the Client's documented instructions, unless UK law requires otherwise. The Client's instructions are this DPA, the Terms and Conditions, the settings the Client chooses in each Service, and written requests (including email) from an Authorised Contact. If Halo believes an instruction breaks Data Protection Legislation, it will tell the Client straight away.

4.2 Only as described. Halo will only access Client Personal Data in the ways set out in the Schedules. Halo will never sell Client Personal Data, use it for its own purposes or marketing, or use it to train AI tools.

4.3 Who can access it. Only Halo's two directors, Tom Lewis and Mark Haycock, can access Client Personal Data. Halo does not use employees, associates or contractors for this. If that changes, anyone given access will be bound by a written duty of confidentiality and the Client will be told.

4.4 Security. Halo will keep appropriate technical and organisational security measures in place, as set out in Schedule 3.

4.5 Data Subject requests. If Halo receives a request from a Data Subject (for example a subject access request), it will pass it to the Client without delay and will not respond itself. Halo will help the Client respond where it reasonably can.

4.6 Helping the Client comply. Halo will reasonably help the Client with security, breach notification, data protection impact assessments and any consultation with the Information Commissioner's Office, taking into account the information Halo has.

5. Sub-processors, breaches, deletion and other terms

5.1 Sub-processors. The Client gives Halo general authorisation to use the Sub-processors listed in Schedule 3. Halo will email the Client at least 30 days before adding or replacing a Sub-processor. The Client can object on reasonable data protection grounds. If the objection can't be resolved, the Client may end the affected Service. Halo will only use Sub-processors that provide data protection terms giving the same level of protection as this DPA, and Halo remains responsible for them.

5.2 International transfers. Halo processes Client Personal Data in the UK. Some Sub-processors may process data outside the UK. Where they do, the transfer will rely on UK adequacy regulations or on safeguards approved under Data Protection Legislation, such as the UK International Data Transfer Agreement or Addendum.

5.3 Personal Data Breaches. Halo will tell the Client without undue delay, and in any event within 48 hours, after becoming aware of a Personal Data Breach affecting Client Personal Data. Halo will share what it knows: what happened, the data and people likely affected, the likely consequences and what Halo is doing about it. The Client decides whether to report the breach to the ICO or to Data Subjects.

5.4 Deletion and return. Where Halo holds a copy of Client Personal Data to complete a task (such as an App update or troubleshooting), Halo will delete it once the task is finished, as set out in the Schedules. When a Service ends, Halo will hand over any accounts and credentials it holds for the Client, then delete its own copies and records of them, unless UK law requires Halo to keep them.

5.5 Information and audits. Halo will give the Client the information it reasonably needs to show that Halo is meeting this DPA. The Client may audit Halo's compliance once a year, with at least 30 days' notice and at its own cost. Halo's Cyber Essentials certificate and this DPA will normally be enough.

5.6 Liability. Each party is responsible for its own compliance with Data Protection Legislation. Halo is not responsible for a breach caused by the Client not following its own responsibilities in section 3.3, for example an unlocked device or credentials shared with unauthorised people. Halo's liability is subject to the limits in the Terms and Conditions.

5.7 Changes to this DPA. Halo may update this DPA, for example to reflect changes in the law or the Services. The current version will always be at www.halo.support/dpa. Halo will tell Clients about any change that affects how their data is handled.

5.8 Duration. This DPA lasts for as long as Halo processes Client Personal Data, and the deletion terms continue after a Service ends.

5.9 Law. This DPA is governed by the laws of England and Wales.

Schedule 1: Halo Sign-in System

How the system holds data. The Halo Sign-in System App runs on the Client's iPad and stores all sign-in data locally on that iPad. Halo has no remote access to the iPad or to the data on it. The App runs in Claris FileMaker Go and works entirely offline. It does not use FileMaker Server or any Claris hosted or cloud service, so no Client Personal Data is sent to Claris. Halo can only see Client Personal Data in the situations below.

WhenWhat Halo can accessSafeguards
Installation and on-site supportData on the iPad, using the admin login, while physically on siteOnly with the Client's permission and during the visit
App updatesA copy of the Client's data, from an iCloud backup or an export the Client providesImported into the updated App on a Halo director's computer, checked for a complete transfer, then deleted from that computer
TroubleshootingAn export or App backup the Client sends when reporting an issueUsed only to investigate the issue, deleted once it is resolved
Gmail account set up by Halo on the Client's behalf to send exportsExports and reports stored in that account's sent mailThe Client is given the login and can change the password at any time. Halo keeps a copy so the account can be recovered if the login is lost, and only uses it with the Client's permission, for example to fix export problems
Apple ID set up by Halo on the Client's behalfThe iPad's iCloud backupThe Client is given the login and can change the password at any time. Halo keeps a copy so the account can be recovered if the login is lost, and only uses it with the Client's permission
Admin login and admin QR codesNothing remotely; they only work on the iPad itselfStored in a password manager, used only when on site

Accounts set up on the Client's behalf. Any Gmail account or Apple ID that Halo sets up for the Client belongs to the Client and runs on Google's or Apple's standard terms for personal accounts. Google and Apple are therefore the Client's own service providers for these accounts, not Halo's Sub-processors. The Client decides whether those terms suit its policies, and can provide its own Google Workspace account or Apple ID instead. The Client can ask Halo to delete its copy of the login at any time.

Data Subjects. Staff, visitors, contractors, agency workers, pupils, parents and guardians, residents (Care edition), and any other visitor types the Client adds.

Categories of Personal Data. What is collected depends on the fields the Client switches on.

Data SubjectData that may be collected
StaffName, sign-in and sign-out times, QR code ID, answers to staff questions
Visitors, contractors, agency workersVisitor type, full name, company, vehicle registration, person visiting, badge number, signature, mobile number, email address, answers to custom questions, sign-in and sign-out times
PupilsName, reason for late arrival or early departure, class or year group, dinner choice, answers to custom questions, times
Parents and guardiansName, signature, relationship to the pupil
ResidentsName (or initials or a nickname, if the Client chooses), QR code ID, sign-in and sign-out times

Special category data. The system is not designed to collect special category data. However, a reason for absence or an answer to a custom question could include health information, such as a medical appointment. "Rather not say" is included as an absence option by default so nobody has to share this at the screen. The Client decides whether to collect this kind of information.

Purpose. Keeping an accurate record of who is in the building, for emergencies, fire registers, safeguarding and administration. Where switched on, Track and Trace reports use the same data to show who was in the building at the same time as a named person.

Retention. The Client sets retention periods in the App's settings, separately for each visitor type, and is responsible for matching them to its retention policy. Data past its retention period is deleted from the iPad automatically.

Duration. For as long as the Client uses the Halo Sign-in System.

Schedule 2: IT support (Google Workspace and device management)

What Halo does. Under a support agreement, Halo helps run the Client's Google Workspace domain and manages its devices through a mobile device management platform such as Jamf. This includes creating, suspending and updating user accounts, resetting passwords, managing settings and policies, and pushing apps and settings to devices.

How Halo accesses data. Halo works remotely through the Google Admin console and the device management console, using admin accounts the Client has authorised. Admin access means Halo could technically see the contents of user accounts. Halo will only open account content (such as email or files) when a support task requested by an Authorised Contact needs it, and only as much as that task needs.

Accounts and licences. The Client owns its Google Workspace and device management licences, accounts and credentials, and contracts with those providers directly. Google and the device management provider are therefore the Client's own Processors, not Halo's Sub-processors.

Data Subjects. Staff, pupils, governors or trustees, and anyone else with an account on the Client's domain or a managed device.

Categories of Personal Data. Names, email addresses, account details and roles, groups and classes, device identifiers and assigned users, sign-in and audit logs, and any content in user accounts that Halo needs to see to complete a support task. Account content may include special category data, which Halo will not access unless a support task strictly requires it.

Purpose. Administering, securing and supporting the Client's Google Workspace domain and managed devices.

Ending the Service. When the support agreement ends, Halo will hand over any credentials it holds and remove its own admin access, or ask the Client to remove it.

Duration. For the term of the support agreement.

Schedule 3: Security measures and Sub-processors

Halo's security measures

  • Halo holds Cyber Essentials certification and appropriate business insurance.
  • Only Halo's two directors can access Client Personal Data.
  • Client credentials (admin logins, Gmail accounts, Apple IDs) are kept in a password manager and are never written down or shared.
  • Gmail accounts Halo sets up on a Client's behalf for sending exports are set up with 2-step verification.
  • Halo has no remote access to Halo Sign-in System iPads.
  • Copies of Client Personal Data received for updates or troubleshooting are kept only on a Halo director's computer, which is encrypted with FileVault, and deleted once the task is complete, including any copy received by email.
  • Halo gives Clients written guidance on securing their devices, in the Halo Sign-in System Data Handling Document.

Sub-processors

Sub-processorWhat it doesApplies toWhere data may be processed
GoogleHalo's own Google Workspace email, used to receive exports and backups for updates or troubleshootingSchedule 1UK and other countries, including the US
AnthropicClaude AI assistant (Team plan), used to help with admin and support emails, which may contain Client Personal DataSchedules 1 and 2US and other countries