Oakwatch Data Processing Agreement
Last updated 1 October 2026
This Data Processing Agreement (“DPA”) is between:
- the Customer: the business that signs up to Oakwatch (the “Controller”), and
- Chetnet Limited, a company registered in England and Wales (company number 05921905), which provides Oakwatch (the “Processor”, “we”, “us”).
It forms part of the Oakwatch Terms of Service (the “Terms”). It’s accepted when the Customer signs up to or uses Oakwatch. If this DPA and the Terms conflict about personal data, this DPA wins.
Words like personal data, processing, controller, processor, data subject and personal data breach have the meanings given in the UK GDPR and the Data Protection Act 2018 (together, “Data Protection Law”).
1. Roles
1.1 The Customer is the controller of the personal data it (and its workers, managers and backup contacts) put into Oakwatch (“Customer Data”). Chetnet Limited processes Customer Data as the Customer’s processor.
1.2 The details of the processing are in Annex 1.
2. The Customer’s responsibilities
2.1 The Customer decides why and how Oakwatch is used for its people, and is responsible for:
- having a lawful basis to use Oakwatch, including for location data;
- giving its workers and backup contacts clear privacy information (they can use the Oakwatch Privacy Policy as a starting point);
- carrying out a data protection impact assessment where Data Protection Law requires one (tracking employee location often does);
- the accuracy of what it enters, including contact numbers;
- its own health and safety duties to lone workers. Oakwatch is a tool that helps the Customer meet them; it doesn’t take them over.
2.2 Oakwatch is not an emergency or monitoring service. It alerts the people the Customer chooses and doesn’t contact the emergency services. It relies on phones, batteries, mobile signal and people responding.
3. Our obligations as processor
We will:
3.1 Instructions. Only process Customer Data on the Customer’s documented instructions, which are this DPA, the Terms and the Customer’s use of Oakwatch’s settings. The only exception is where UK law requires otherwise, in which case we’ll tell the Customer first unless the law forbids it. We’ll tell the Customer if we think an instruction breaks Data Protection Law.
3.2 Confidentiality. Make sure anyone we allow to access Customer Data is bound by a duty of confidentiality.
3.3 Security. Take appropriate technical and organisational measures to protect Customer Data, as required by Article 32 UK GDPR. They’re described in Annex 2.
3.4 Sub-processors. Only use the sub-processors in Annex 3, which the Customer authorises by accepting this DPA. We’ll give at least 30 days’ notice (by email or in the app) before adding or replacing one. The Customer may object on reasonable data protection grounds, and if we can’t resolve it, the Customer may end the Terms. Each sub-processor is bound by written data protection terms giving the same level of protection as this DPA, and we remain responsible for them.
3.5 Helping with individuals’ rights. Help the Customer, by appropriate technical and organisational measures, to respond to requests from individuals (for example access, correction or deletion). If we receive a request directly, we’ll pass it to the Customer without undue delay and won’t respond ourselves unless told to.
3.6 Helping with compliance. Help the Customer, taking into account the information available to us, with security, personal data breach notification, data protection impact assessments and any prior consultation with the ICO.
3.7 Personal data breaches. Tell the Customer without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting Customer Data. We’ll give the information the Customer reasonably needs to meet its own duty to report to the ICO within 72 hours where required.
3.8 End of the contract. When the Terms end, the Customer can export its data for 30 days. After that we delete Customer Data, including copies, within a further 30 days, unless UK law requires us to keep it. Backups are overwritten in the normal course of operation.
3.9 Audits. Make available all information reasonably needed to show we comply with this DPA, and allow for and contribute to audits and inspections by the Customer or an auditor it appoints. These are limited to once a year (unless there’s been a breach or the ICO requires it), at the Customer’s cost, with at least 30 days’ notice, during business hours and under confidentiality terms. We’ll answer written questions first, as that’s usually enough.
4. International transfers
4.1 Oakwatch’s main database and servers are in London (Google Cloud, europe-west2). Some sub-processors process data in the USA (see Annex 3).
4.2 We only transfer Customer Data outside the UK with a safeguard recognised by Data Protection Law. At the date of this DPA, that’s the UK Extension to the EU-US Data Privacy Framework (Google and Twilio are certified) and each sub-processor’s UK International Data Transfer Agreement or Addendum.
5. Liability
Each party’s liability under this DPA is subject to the limits in the Terms, except where Data Protection Law doesn’t allow that.
6. General
6.1 This DPA lasts as long as we process Customer Data for the Customer.
6.2 We may update this DPA to reflect changes in law or in Oakwatch, with 30 days’ notice. Changes won’t reduce the protection of Customer Data.
6.3 This DPA is governed by the law of England and Wales, and its courts have exclusive jurisdiction.
Annex 1: Details of the processing
| Item | Details |
|---|---|
| Subject matter | Providing the Oakwatch lone-worker safety service to the Customer |
| Duration | For as long as the Terms last, plus the deletion period in clause 3.8 |
| Nature and purpose | Storing and processing sessions, check-ins and alerts; sending alerts by push notification and text message; showing managers a live board and alert details; keeping a record of what happened |
| Data subjects | The Customer’s workers, managers and owners who use Oakwatch; backup contacts the Customer adds (who may not use the app) |
| Types of personal data | Name; email address; phone number; role; company membership; job names; session times and status; location (only at session start, check-in, extension and SOS, and while the app is open during an SOS); alert details, responses, outcomes and notes; push notification tokens and app version; records of messages sent and whether they were delivered |
| Special category data | Not intended. Alert notes written by the Customer may occasionally include health information (e.g. “had a fall”). The Customer is responsible for having a lawful condition for this |
| Retention | Last location is cleared when a session ends. Location records are deleted automatically after 90 days. Other Customer Data is kept for the duration of the Terms (or until the Customer deletes it), then deleted under clause 3.8 |
Annex 2: Security measures
- Encryption: data is encrypted in transit (TLS) and at rest (Google Cloud default encryption).
- Separation between customers: Firestore security rules make sure each company can only access its own data, and workers can only see their own sessions. These rules are covered by automated tests, including tests for access between companies.
- Trusted server logic: starting sessions, escalation, alerts, invites and removing members all run in server-side Cloud Functions, never trusted to the phone. Times come from the server, not the phone’s clock.
- Secrets: API keys (e.g. Twilio) are held in Google Secret Manager, never in the app or source code.
- Data minimisation: location is only collected at the moments in Annex 1, with “While using the app” permission only. No background tracking, advertising or cross-app tracking.
- Access: only authorised Chetnet Limited personnel can access production systems, and only where needed to provide or support the service.
- Reliability: alerts are recorded before they’re sent, so a retry never sends a stage twice; every delivery attempt is logged.
- Invites: single-use, random 12-character codes that expire after 7 days and can be cancelled.
Annex 3: Authorised sub-processors
| Sub-processor | Purpose | Location | Transfer safeguard |
|---|---|---|---|
| Google LLC / Google Cloud (Firebase, Google Maps) | Database, server functions, sign-in, push notifications, maps in the app | Database and functions: London. Sign-in: USA. Push and maps: global | UK Extension to the EU-US DPF; Google’s data processing terms |
| Twilio Inc. | Sending alert text messages | USA | UK Extension to the EU-US DPF; Twilio’s data protection addendum (incl. UK IDTA) |
| Apple Inc. | Delivering push notifications to iPhones | Global | Apple’s terms |
| 34SP.com | Email (support and account messages) | UK | Not needed (UK) |