Legal
Data Processing Agreement
Last updated: 21 October 2026
The data protection terms that apply to every AutoM8 customer.
This Data Processing Agreement (“Agreement”) applies to every customer of AutoM8. It sets out how Scorpion Automotive Ltd handles personal data on your behalf when you use the AutoM8 platform and Scorpion-supplied cameras and telematics devices, as required by Article 28 of the UK GDPR.
It forms part of your agreement with us for AutoM8 (the “Principal Agreement”), whether that is a signed contract or an online sign-up. It is accepted when your account is created, or by your account administrator in AutoM8.
Parties
- The Controller is the business that uses AutoM8 (you).
- The Processor is Scorpion Automotive Ltd, a company registered in England and Wales (company number 06969452), registered office at Fourth Floor, Unit 5b The Parklands, Bolton, BL6 4SD, United Kingdom.
Where this Agreement and the Principal Agreement conflict on data protection, this Agreement prevails.
1. Definitions
1.1 In this Agreement:
“Data Protection Legislation” means the UK GDPR, the Data Protection Act 2018, the Privacy and Electronic Communications Regulations 2003, and any successor or amending legislation, together with any binding guidance or codes of practice issued by the Commissioner.
“Fleet Personal Data” means personal data processed by the Processor on behalf of the Controller in connection with the Services, as described in Annex 1.
“Services” means the AutoM8 platform and associated in-vehicle camera and telematics hardware supplied under the Principal Agreement.
“Sub-processor” means any third party engaged by the Processor to process Fleet Personal Data.
“UK GDPR”, “controller”, “processor”, “personal data”, “personal data breach”, “processing”, “data subject”, “special category data” and “Commissioner” have the meanings given in the Data Protection Legislation.
1.2 References to an Article are to an Article of the UK GDPR as in force at the relevant time, including as amended by the Data (Use and Access) Act 2025.
2. Roles of the parties
2.1 In respect of Fleet Personal Data, the Controller is the controller and the Processor is a processor.
2.2 The Processor is an independent controller for the processing described in Annex 4, which it carries out under its own privacy notice and not under this Agreement.
2.3 The Controller warrants that it has a lawful basis under Article 6 and, where applicable, a condition under Article 9 and Schedule 1 of the Data Protection Act 2018, for each purpose for which Fleet Personal Data is processed, and that it has given data subjects (including its drivers) the information required by Articles 13 and 14.
2.4 The Processor shall not determine the purposes of the processing of Fleet Personal Data.
2.5 The Controller is responsible for configuring the settings listed in Annex 3. The Processor’s defaults are recommendations only. By accepting this Agreement the Controller instructs the Processor to apply the retention periods in Annex 6.
3. Processing instructions
3.1 The Processor shall process Fleet Personal Data only:
(a) on the documented instructions of the Controller, being this Agreement, its Annexes and any further written instructions; and
(b) as required by applicable law, in which case the Processor shall inform the Controller before processing unless the law prohibits it.
3.2 If the Processor considers that an instruction infringes the Data Protection Legislation, it shall immediately inform the Controller.
3.3 If the Controller does not withdraw or amend that instruction within 10 business days of the Processor’s notice, the Processor may suspend the affected functionality on written notice until the matter is resolved, without liability for that suspension.
3.4 The Processor shall transfer Fleet Personal Data outside the United Kingdom only to the Sub-processors and locations listed in Annex 5, or as otherwise authorised in writing by the Controller, and only where the requirements of the Data Protection Legislation on international transfers are met.
4. Confidentiality of personnel
4.1 The Processor shall ensure that each person it authorises to process Fleet Personal Data is bound by confidentiality, has received appropriate training, and processes the data only as necessary to provide the Services.
4.2 The Processor shall keep a record of the persons authorised to access Fleet Personal Data and review it at least quarterly and on each leaver.
5. Security
5.1 The Processor shall implement and maintain the technical and organisational measures in Annex 2.
5.2 The Processor shall not reduce the overall level of protection in Annex 2 during the term, and shall notify the Controller of any material change to Annex 2 not less than 30 days in advance.
6. Sub-processors
6.1 The Controller gives general written authorisation for the Processor to engage the Sub-processors listed in Annex 5.
6.2 The Processor shall give the Controller not less than 30 days’ prior written notice of any intended addition or replacement of a Sub-processor. The Controller may object on reasonable data protection grounds within that period; the parties shall then discuss the objection in good faith and, if it cannot be resolved, the Controller may terminate the affected Services without penalty.
6.3 The Processor shall impose on each Sub-processor, by written contract, data protection obligations no less onerous than those in this Agreement, and remains fully liable to the Controller for each Sub-processor’s performance.
6.4 Manufacturer diagnostics. Where a fault with a camera or telematics device cannot be resolved by the Processor, the Processor may share with that device’s manufacturer the minimum Fleet Personal Data needed to diagnose and fix the fault: the device’s identifiers, diagnostic and event logs for the period around the fault and, where the fault requires it, video and audio from that device, including by temporarily connecting the device to the manufacturer’s platform. Each manufacturer is a Sub-processor listed in Annex 5. Every such share is recorded in AutoM8’s manufacturer sharing log, which the Controller can view under Settings › Security.
7. Data subject rights
7.1 The Processor shall assist the Controller in responding to requests from data subjects exercising their rights under the Data Protection Legislation, having regard to the nature of the processing.
7.2 The Processor shall not respond directly to a data subject about Fleet Personal Data. It shall forward any such request to the Controller without undue delay and in any event within 3 business days, and tell the data subject that the request has been passed to the Controller.
7.3 The Controller can place a legal hold on footage and related data in AutoM8 itself. On the Controller’s written request the Processor shall also, without undue delay, suspend automatic deletion of specified Fleet Personal Data pending a request, complaint, claim, investigation or proceedings.
7.4 The Controller can view and export AutoM8’s footage access log, which records every view, download, export and live stream of footage.
8. Assistance and cooperation
8.1 The Processor shall assist the Controller with its obligations under Articles 32 to 36, including any data protection impact assessment and prior consultation with the Commissioner, having regard to the nature of the processing and the information available to the Processor.
8.2 The Processor shall maintain a record of processing activities as a processor under Article 30(2) and make it available to the Controller and the Commissioner on request.
8.3 The Processor shall cooperate with the Commissioner and notify the Controller without undue delay of any communication from the Commissioner about Fleet Personal Data, unless prohibited by law.
9. Personal data breach
9.1 The Processor shall notify the Controller of any personal data breach affecting Fleet Personal Data without undue delay and in any event within 24 hours of becoming aware of it.
9.2 The notification shall include, so far as then known: the nature of the breach; the categories and approximate number of data subjects and records concerned; the likely consequences; the measures taken or proposed; and a point of contact. Information not available at once shall be provided in phases without further undue delay.
9.3 Assessing the risk of a breach, notifying the Commissioner and notifying data subjects are matters for the Controller. The Processor shall not notify the Commissioner or any data subject of a breach affecting Fleet Personal Data without the Controller’s prior written consent, unless required by law.
9.4 Breach notifications shall be sent to the breach contact the Controller has given the Processor (or, if none, the Controller’s account administrator), as updated by notice from time to time. The Controller shall notify breaches it discovers that involve the Services to [email protected].
10. Audit and information
10.1 The Processor shall make available to the Controller all information reasonably necessary to demonstrate compliance with this Agreement and Article 28, and shall allow for and contribute to audits, including inspections, by the Controller or an auditor it mandates.
10.2 The Processor may meet clause 10.1 in the first instance by completing a reasonable security questionnaire provided by the Controller.
10.3 Audits shall be on not less than 30 days’ written notice, during business hours, no more than once in any 12-month period, subject to confidentiality undertakings, and at the Controller’s cost, except where an audit follows a personal data breach affecting the Controller’s data or is required by the Commissioner, in which case these limits do not apply and the Processor bears its own costs.
11. Return and deletion
11.1 On expiry or termination of the Services, the Processor shall, at the Controller’s election, return or delete all Fleet Personal Data and delete existing copies, unless the law requires the Processor to keep it.
11.2 Fleet Personal Data shall remain available for export by the Controller for 30 days after termination, and shall be deleted within 60 days of termination. The export is provided as machine-readable data files with stored documents, and stored video footage is supplied on request.
11.3 Deletion shall extend to backups within 30 days of the primary deletion.
11.4 The Processor shall certify deletion in writing on request.
11.5 The Processor may keep records needed for the establishment, exercise or defence of legal claims, or required by law, for the periods in Annex 6, and only for those purposes.
12. Automated processing
12.1 The Services produce automated outputs, including event classifications, driver-behaviour scores and fatigue or distraction alerts, as described in Annex 7.
12.2 Those outputs are decision support, not decisions. The Controller shall not use any such output as the sole basis for a decision with a legal or similarly significant effect on any individual, and shall ensure every such decision involves meaningful human involvement.
13. Liability
13.1 Each party’s liability under or in connection with this Agreement is subject to the limitations and exclusions of liability in the Principal Agreement.
13.2 Nothing in this Agreement limits either party’s liability where the law does not allow it to be limited.
14. General
14.1 This Agreement takes effect when the Controller accepts it (at sign-up or in AutoM8) or first uses the Services, whichever is earlier, and continues for as long as the Processor processes Fleet Personal Data.
14.2 The parties shall negotiate in good faith any amendment reasonably needed to reflect a change in the Data Protection Legislation or binding guidance.
14.3 This Agreement is governed by the law of England and Wales, and the courts of England and Wales have exclusive jurisdiction.
14.4 The Processor may update this Agreement by publishing a new version at this address and giving the Controller not less than 30 days’ notice. A change that reduces the Controller’s protection requires the Controller’s written agreement.
Annex 1: Description of the processing
| Item | Detail |
|---|---|
| Subject matter | Provision of the AutoM8 fleet management platform and Scorpion-supplied in-vehicle cameras and telematics devices |
| Duration | The term of the Principal Agreement, plus the export and deletion period in clause 11 |
| Nature of processing | Collection from devices, storage, display, analysis (event detection and scoring), transmission, export and deletion |
| Purposes | The Controller’s fleet management, vehicle tracking, driver safety, incident investigation, insurance and claims handling, and driver coaching |
| Data subjects | The Controller’s drivers and other staff using vehicles; the Controller’s AutoM8 users; vehicle passengers; members of the public and other road users captured on forward-facing footage |
| Categories of personal data | Forward-facing and driver-facing video; in-cab audio where the Controller enables it; GPS location, speed, routes and journeys; telematics events (harsh braking, acceleration, cornering, speeding, idling); fatigue and distraction alerts; driver-behaviour scores; driver identity (name, driver ID, driver tag, vehicle assignment); AutoM8 user details and activity logs |
| Special category data | Fatigue and distraction alerts are treated as possible health data. AutoM8 does not use facial recognition or create biometric templates. |
Annex 2: Technical and organisational measures
| Area | Measure |
|---|---|
| Hosting | Google Cloud Platform, London region (europe-west2), in an isolated production project. Databases, footage and backups are held in the UK. |
| Encryption in transit | The web application and APIs are served over HTTPS only. Device-to-platform links run over the mobile carrier network. |
| Encryption at rest | Databases and footage storage are encrypted at rest (AES-256). Two-factor secrets and API keys are additionally encrypted by the application; passwords are hashed with bcrypt. |
| Access control | Role-based permissions with per-vehicle-group data scoping, enforced in the application and by database row-level security. Live in-cab viewing requires its own permission. |
| Authentication | Two-factor authentication is mandatory for all Scorpion administrative accounts. It is available to every Controller user, and the Controller can make it mandatory for its whole account. |
| Logging | Changes, logins and security events are logged. Every view, download, export and live stream of footage is logged in a footage access log the Controller can view and export. Changes to camera audio settings are logged. |
| Scorpion support access | Scorpion staff access the Controller’s account only through a time-limited support session (60 minutes) with a recorded reason. Each session is visible to the Controller under Settings › Security. |
| Retention and deletion | Automatic deletion at the periods in Annex 6. Legal holds suspend deletion of held material. |
| Backups | Daily encrypted backups in the London region, kept for up to 14 days. |
| Footage on the device | Continuous recording stays on the camera and is overwritten in rotation; only event-triggered and requested clips are uploaded. |
| Development and change | Production is isolated, with restricted access and controlled release. Automated security scanning runs in the build pipeline. |
| People | All staff complete information security training and are bound by confidentiality. |
Annex 3: Settings the Controller configures
| Setting | Options | Processor default |
|---|---|---|
| Footage retention | 7 to 90 days | 60 days |
| Audio recording | On or off, per camera and per lens | Off |
| Driver-facing camera | Enabled or disabled, per camera | Enabled |
| Behaviour scoring | Category weightings and alert thresholds | Scorpion’s published weightings |
| Alerts and coaching rules | Which events raise alerts or coaching cases | Off until configured |
| League table | On or off; driver names shown or hidden | On, with names hidden |
| Legal holds | Place and release holds on clips, events, vehicles, drivers or date ranges | None |
| Two-factor authentication | Mandatory for all users, or optional | Optional |
| Users and permissions | Roles and vehicle-group access for each user | Set by the Controller |
Annex 4: Processing for which the Processor is an independent controller
Controller account, contact and billing records; platform security, audit and access logs; support requests raised by the Controller’s personnel; and aggregate, non-identifying platform performance and reliability metrics.
Annex 5: Authorised Sub-processors
| Sub-processor | Service | Location | Data accessed |
|---|---|---|---|
| Google Cloud Platform | Hosting: compute, databases, footage storage, backups | UK (London) | All platform data |
| Cloudflare, Inc. | DNS, edge network, DDoS protection | Global | Request traffic in transit |
| Twilio SendGrid | Transactional email | USA | User names, email addresses, message content |
| Stripe | Billing and payments | USA / Ireland | Billing contacts and payment data |
| Google Firebase Cloud Messaging | Mobile push notifications | Global | Device push tokens, notification content |
| Sentry | Error monitoring (camera gateway) | Being confirmed | Device identifiers in error reports |
| 1NCE GmbH | IoT SIM connectivity | Germany | Device and SIM identifiers; data in transit |
| m2m portal | SIM management | Being confirmed | Device and SIM identifiers, usage |
| Teltonika | Tracker firmware updates and SIM lookup | Lithuania | Device identifiers, firmware version |
| Jimi IoT (Tracksolid) | Platform for one tracker model | EU endpoint | Location data for those trackers |
| Howen Technologies Co., Ltd. | Camera manufacturer: fault diagnosis (clause 6.4) | China | Device identifiers, logs and, where needed, footage and audio for a faulty camera |
| Ideal Postcodes | Address lookup | UK | Queried addresses |
| OpenStreetMap Foundation (Nominatim) | Reverse geocoding fallback | EU | Journey start and end coordinates |
| OpenFreeMap | Mobile app map tiles | Being confirmed | Map area requests |
| BigChange | Job synchronisation, where the Controller uses it | UK | Job, site and contact data |
| DVLA / DVSA | Vehicle and MOT lookups | UK | Vehicle registrations |
Annex 6: Retention periods
| Data | Period |
|---|---|
| Continuous footage on the camera | Not uploaded; overwritten on the device |
| Event-triggered and requested footage (including audio) | 60 days by default (Controller can set 7 to 90) |
| Footage and data under a legal hold | Until the hold is released or expires |
| Detailed GPS positions | 35 days |
| Journeys, driving events, driver scores, fatigue and distraction alerts | 12 months |
| Footage access log, security and sign-in logs, support-access log | 12 months |
| Deletion certificates (Processor’s own record) | Retained as evidence of deletion |
Database backups expire within 14 days of a deletion.
Annex 7: How automated outputs are produced
- Event detection (drowsiness, distraction, phone use, smoking, forward-collision and lane warnings where enabled) runs on the camera itself, using the manufacturer’s software. AutoM8 receives the classified event; it does not analyse video.
- Driver scores are calculated by fixed rules, not machine learning, from event counts and rates per distance across weighted categories (speeding, braking, acceleration, cornering, idling and, with cameras, distraction, fatigue and seatbelt). The Controller sets the weightings and thresholds. Drivers with fewer than 20 journeys in the period are shown as provisional and not ranked.
- Alerts and coaching cases are raised only by rules the Controller configures.
- Optional coaching summaries are written by a language model running on Scorpion-owned hardware from the scores already calculated. They make no new judgement about the driver.