Version 1.0, 10 November 2026
1.1 This Data Processing Agreement ("DPA") is between Accurail Ltd, company number 13030851, registered office Neo, 9 Charlotte Street, Manchester, United Kingdom, M1 4ET ("Accurail", the processor), and the customer named in the Services Agreement ("Customer", the controller).
1.2 Accurail provides the Accurail platform (web application and mobile app) for safe system of work planning, shift records and related rail safety documentation (the "Services"). To provide the Services, Accurail processes personal data on the Customer's behalf.
1.3 This DPA forms part of the Services Agreement between the parties (the "Agreement") as a schedule. It adds to clause 11 of the Agreement (Data Protection and Privacy) and does not replace it. For the processing of personal data, this DPA prevails over any other term of the Agreement, despite the Agreement's order of priority, except the Agreement's limits and exclusions of liability, which always apply, and any term the parties agree in writing that expressly varies this DPA.
1.4 This DPA takes effect when the Customer accepts it, either by signing it or by accepting it in the Services, and applies to all Customer Personal Data that Accurail holds at that date and after it. A person who accepts this DPA in the Services confirms that they are authorised to do so on the Customer's behalf.
2.1 Data Protection Law means the UK GDPR, the Data Protection Act 2018, the Privacy and Electronic Communications Regulations 2003, and any law that replaces or amends them, including the Data (Use and Access) Act 2025.
2.2 Customer Personal Data means personal data that Accurail processes for the Customer under the Agreement, as described in Schedule 1.
2.3 Location Data means data from a user's mobile device that shows, or can be used to work out, where that user is. It includes GPS coordinates, accuracy readings and the result of a location check.
2.4 Sub-processor means a third party that Accurail engages to process Customer Personal Data.
2.5 Personal Data Breach has the meaning in Article 4(12) UK GDPR.
2.6 Authorised User means a person the Customer allows to use the Services, including the Customer's employees, contractors and agency staff.
2.7 "controller", "processor", "data subject", "personal data", "processing" and "supervisory authority" have the meanings in Data Protection Law. The supervisory authority is the Information Commissioner's Office (ICO).
3.1 The Customer is the controller and Accurail is the processor of Customer Personal Data.
3.2 Accurail will process Customer Personal Data only on the Customer's documented instructions. The Agreement, this DPA and the Customer's configuration of the Services are the Customer's complete instructions at the date of signing. This includes the features the Customer turns on and how it configures them.
3.3 Accurail will tell the Customer promptly if it believes an instruction breaks Data Protection Law. Accurail may pause the affected processing until the Customer confirms or changes the instruction.
3.4 If UK law requires Accurail to process Customer Personal Data other than on the Customer's instructions, Accurail will tell the Customer before it does so, unless the law forbids this.
3.5 The Customer is responsible for:
3.6 Accurail will not sell Customer Personal Data, use it for advertising, or combine it with data from other customers, except in aggregated form that identifies no person or customer.
4.1 Confidentiality. Accurail will make sure that every person it allows to process Customer Personal Data is bound by a duty of confidence, through employment contracts, confidentiality agreements and Accurail's Human Resource Security Policy and Code of Conduct.
4.2 Least access. Accurail staff will access Customer Personal Data only when they need to, for example to provide support the Customer asks for or to investigate an incident. Access follows Accurail's Access Control Policy and is logged under its Operations Security Policy.
4.3 Security. Accurail will keep in place the technical and organisational measures in Schedule 2, as required by Article 32 UK GDPR. Accurail may update those measures, but will not reduce the overall level of protection.
4.4 Data minimisation. Accurail designs the Services to collect only the personal data each feature needs. Schedule 1 describes the processing, and Accurail gives the Customer a written description of any feature on request under clause 4.5. Accurail will tell the Customer before it materially changes how Customer Personal Data is collected or stored.
4.5 Assistance. Taking into account the nature of the processing, Accurail will give the Customer reasonable help to:
4.6 Records. Accurail will keep a record of its processing activities for the Customer, as Article 30(2) UK GDPR requires.
4.7 Data protection lead. Accurail's data protection lead is its Director. Contact: privacy@accurail.co.uk.
4.8 New optional features. Accurail may add optional features to the Services that process Customer Personal Data in new ways, including new uses of Location Data. Before a new feature is available, Accurail will update Schedule 1 to describe it and tell the Customer. A new feature processes Customer Personal Data only once the Customer turns it on, and turning it on is the Customer's documented instruction for that processing.
5.1 The Customer gives general written authorisation for Accurail to use the Sub-processors in Schedule 3. This authorisation is also the Customer's prior written consent to that subcontracting under the Agreement's assignment clause.
5.2 Accurail will tell the Customer about any intended addition or replacement of a Sub-processor at least 7 days before it takes effect, by email to the Customer's contact named in the Agreement. Where a change is urgently needed for security or continuity of the Services, Accurail will give as much notice as it reasonably can. Despite the Agreement's notices clause, this notice takes effect when sent and needs no acknowledgement. The Customer may object on reasonable data protection grounds within 30 days of the notice. If the parties cannot resolve the objection, the Customer may end the affected part of the Services.
5.3 Accurail will put a written contract in place with each Sub-processor that imposes data protection obligations giving at least the same protection as this DPA, as far as they apply to the processing that Sub-processor carries out (Article 28(4) UK GDPR). Accurail assesses each Sub-processor before use and reviews it at least once a year under its Third-Party Management Policy. Accurail stays fully liable to the Customer for each Sub-processor's performance.
5.4 Accurail will not transfer Customer Personal Data outside the UK unless one of these applies:
6.1 Accurail will notify the Customer without undue delay after becoming aware of a Personal Data Breach affecting Customer Personal Data, as Article 33(2) UK GDPR requires.
6.2 The notice will include, as far as Accurail knows at the time:
Accurail may give this information in stages where it is not all available at once.
6.3 Accurail will investigate and contain the breach under its Incident Response Plan. Under that plan, the Director makes the breach decision, legal counsel approves every external notice, and a root-cause analysis is written for every incident.
6.4 Accurail will not tell data subjects or the ICO about a breach of Customer Personal Data on the Customer's behalf, unless the Customer asks it to or the law requires it.
6.5 A notice under this clause is not an admission of fault or liability.
7.1 Data subject requests. If Accurail receives a request from a data subject about Customer Personal Data, it will pass it to the Customer without undue delay and will not answer it unless the Customer asks. Accurail will help the Customer find, export, correct or delete the data.
7.2 Evidence of compliance. On request, and no more than once a year, Accurail will give the Customer the information it reasonably needs to show compliance with this DPA. This includes Accurail's current certifications (ISO/IEC 27001 and Cyber Essentials Plus), its Statement of Applicability, and a summary of its most recent independent penetration test, which runs at least once a year.
7.3 Audits. The Customer or an independent auditor it appoints may audit Accurail if the information under clause 7.2 is not enough, after a Personal Data Breach affecting Customer Personal Data, where the Customer has a substantiated concern about Accurail's compliance with this DPA, or where the ICO requires it. Outside those cases, audits are limited to once a year. The Customer will give at least 30 days' notice (or less where the ICO requires), keep the audit to normal working hours, and bear its own costs. The auditor must sign a confidentiality agreement. Accurail may withhold other customers' information and details whose disclosure would put the security of the Services at risk.
7.4 Return and deletion. When the Agreement ends, Accurail will return or delete Customer Personal Data, or both, as the Customer chooses. The Customer may export its data through the Services or ask Accurail for an export. Accurail will delete Customer Personal Data within 12 months of the end date, to allow for export or handover, or sooner if the Customer asks in writing, and will confirm deletion in writing on request. Copies in backups are put beyond use, are overwritten on their normal cycle and are not restored except for disaster recovery.
7.5 Clause 7.4 does not apply to data that UK law requires Accurail to keep. Accurail will protect any such data under this DPA and use it only for that legal purpose.
7.6 Liability. Each party's liability under this DPA is subject to the limits and exclusions in the Agreement's liability clause.
7.7 Term. This DPA lasts as long as Accurail processes Customer Personal Data. Clauses 6, 7.4 and 7.5 survive its end.
7.8 Governing law and disputes. This DPA is governed by the law of England and Wales. Any dispute about it is resolved under the Agreement's dispute resolution clause.
| Item | Detail |
|---|---|
| Subject matter | Providing the Accurail platform for planning safe systems of work, running shifts and keeping the related safety records |
| Duration | The term of the Agreement, plus up to 12 months for export and deletion (clause 7.4) |
| Nature and purpose | Storing, displaying, sharing and reporting on safety documents and shift records; sending notifications and emails; using device location where the Customer turns on location features; product analytics; support and security monitoring |
| Data subjects | The Customer's Authorised Users: employees, contractors and agency staff, including persons in charge, COSSes, planners, responsible managers and track workers. Other people named in uploaded documents |
| Categories of data | Identity and contact: name, email, phone, Sentinel number, sponsor, team. Records: signatures, shift and pack records, messages, photos and files uploaded. Technical: IP address, authentication data, device model, app version, push token, login and activity logs. Location Data where the Customer turns on location features |
| Special category data | None intended, and the Customer should not upload it unless the Agreement allows it. If uploaded content, such as an incident photo or report, incidentally contains special category data, Accurail processes it only to provide the Services, under the measures in Schedule 2 |
| Sub-processors | Schedule 3 |
Accurail runs an information security management system certified to ISO/IEC 27001:2022. Each measure below is set out in Accurail's approved information security policies.
| Area | Measure | Source policy |
|---|---|---|
| Classification | Customer data and all personal data are classed as Confidential, the highest class | Data Management Policy |
| Encryption | Confidential data is encrypted at rest and in transit over public networks, using strong ciphers in line with NIST guidance (SP 800-57 for key management). Backups are encrypted | Cryptography Policy; Data Management Policy |
| Access control | Least privilege through role-based access. Unique account per person, no shared credentials. MFA on all privileged access to production. Access removed within 48 business hours of a person leaving. Access reviewed at least once a year. No unauthenticated or anonymous access to confidential systems | Access Control Policy; Data Management Policy |
| Logging | Security-relevant actions, including logins, changes to data and administrator access, are logged with user ID, IP address and timestamp. Logs are kept for at least 30 days and protected against tampering | Operations Security Policy |
| Vulnerability management | Public-facing systems scanned at least every quarter; independent penetration test at least once a year. Fix times from detection: critical 7 days, high 14 days, medium 60 days, low 180 days | Operations Security Policy |
| Secure development | Security is built into the development life cycle, including code review and secure coding practices | Secure Development Policy |
| Resilience | Recovery objectives: production database, recovery time 1 hour and recovery point 6 hours; file storage, 1 hour and 24 hours; application and APIs, 8 hours and 24 hours | Business Continuity and Disaster Recovery Plan |
| Incident response | Single reporting route (incidents@accurail.co.uk), severity levels with set escalation, root-cause analysis for every incident, plan tested every year | Incident Response Plan |
| People | Background checks, including criminal record checks where the law allows. Signed confidentiality and non-disclosure agreements before access. Security awareness training at hire and every year | Human Resource Security Policy |
| Endpoints | Company laptops encrypted, screen lock after 5 minutes, confidential data not stored on personal devices or removable media | Information Security Policy; Data Management Policy |
| Suppliers | Suppliers that handle confidential data are assessed before use and reviewed, including how they protect and dispose of personal data | Third-Party Management Policy |
| Risk | Information security risks are assessed and treated through a documented process with a risk register | Risk Management Policy |
| Data minimisation | Each feature collects only the data it needs. Optional features, such as location checks, run only when the Customer turns them on | Product design |
This Schedule lists the Sub-processors at the date of this DPA. Accurail keeps the list current under clause 5.2 and gives the Customer the current list on request.
| Sub-processor | Purpose | Customer Personal Data | Data location | Transfer route (clause 5.4) |
|---|---|---|---|---|
| MongoDB (Atlas) | Main database | All categories in Schedule 1, including stored Location Data | EU: Ireland (AWS eu-west-1) | Hosting: EU adequacy. Support access by MongoDB, Inc.: UK-US data bridge |
| Google Cloud (Cloud Storage) | File and image storage | Uploaded files, photos, generated documents | EU | Hosting: EU adequacy. Access by Google LLC: UK-US data bridge |
| Vercel | Application hosting and website analytics | All request data in transit; website page analytics | Application functions in Dublin, Ireland; logs and backups may be held outside the EU | UK-US data bridge; ICO UK Addendum |
| Redis | Short-term cache and rate limiting | Names, emails, phone, Sentinel numbers, queued message text | EU: Ireland (eu-west-1) | EU Standard Contractual Clauses with the ICO UK Addendum; Redis Ltd is in Israel, which has UK adequacy |
| Mailgun | Transactional email | Recipient name and email, notification and message content, PDF attachments | EU | EU adequacy |
| Sentry | Error monitoring | Scrubbed error data, user IDs | EU (Germany) | EU adequacy |
| PostHog | Product analytics | User and company IDs and product usage events, some of which include user details | EU | EU adequacy |
| Ably | Real-time chat and presence | User ID, name, chat message content | Ably's global network; Ably is a UK company | Standard Contractual Clauses with the ICO UK Addendum for any transfer to a country without adequacy |
| Expo (with Apple and Google push services) | Push notifications and app updates | Push token and notification text (pack reference, pack name, shift times, assignment notices). App update checks send the device's IP address and an install ID. No names, emails or locations | US | UK-US data bridge |
| Mapbox | Maps | IP address and device data from map loads | US | UK-US data bridge |
| Microsoft Azure (Document Intelligence) | Reading tables from uploaded NR3180 forms | Form content, which may include names and signatures | UK (UK South, London) | Hosting: in the UK, no transfer. Access by Microsoft Corporation: UK-US data bridge |
| Plain | Customer support | Names, emails and messages of Authorised Users who contact support | UK and EEA | Not needed (UK company) |
| Google Workspace | Email and documents, including support and privacy correspondence | Names, emails and the content of messages and files that the Customer or its Authorised Users send to Accurail | Google's global data centres | UK-US data bridge (Google LLC) |
| Linear | Issue tracking for support requests and bug reports | Names, emails and screenshots included in support requests and bug reports | US | EU Standard Contractual Clauses with the ICO UK Addendum |
Transistor Software provides an on-device location library for worksite limit alerts and receives no Customer Personal Data.
Signed for and on behalf of Accurail Ltd
Name: Joseph Boulton
Position: Director
Signature: /Joseph Boulton/ (electronic signature)
Date: 10 November 2026
The Customer signs below or accepts this DPA in the Services under clause 1.4.
Signed for and on behalf of the Customer: ______________________________
Name: ______________________________
Position: ______________________________
Signature: ______________________________
Date: ______________________________