These Business Terms apply when a business signs up to use Driver Codes through app.driver.codes without entering into a separate signed Enterprise Agreement.

By creating an account and ticking the acceptance box at signup, the business agrees to these Business Terms, the Data Processing Addendum (Standard), the Data Sharing Agreement (Standard), the Privacy Notices referenced below, and the rules at signup and in the service. Together these form the agreement between the business and RSMT Limited (trading as Driver Codes).

If a business needs negotiated commercial terms — for example, signed contractual paperwork, a minimum-volume commitment, named account management, or contractual SLAs — Driver Codes offers an Enterprise Agreement on request. Contact hello@driver.codes.

1. Who's who

"We", "us", "Driver Codes" means RSMT Limited, company number 11744436, registered at 19A Queens Road, Hale, WA15 9HF.

"You", "Customer" means the business that has signed up.

"Service" means the Driver Codes business service available at app.driver.codes — including the customer portal, driver invitation workflow, driver authority capture, driver licence checks, and related features.

"Driver" means an individual employee, contractor, or other person you invite into the Service.

"Credits" means prepaid units of Service consumption, purchased and consumed in accordance with clause 3.

"Driver Record Information" means the information returned by the DVLA (and, where linked, DVSA) about a driver, including licence entitlements, endorsements, disqualifications, and similar.

2. Eligibility and use

2.1 You confirm at signup that you are signing up on behalf of a business and have authority to bind that business. The Service is for business use only. Consumer use of Driver Codes is covered by the separate Consumer App Terms.

2.2 You may only use the Service to check drivers in respect of whom you have a genuine, lawful business reason — typically employees and contractors who drive for your business. You must not use the Service to check anyone else.

2.3 You're responsible for keeping your account credentials secure and for everything done through your account. Enable multi-factor authentication on every administrator account. If you think your account has been accessed without permission, tell us at security@driver.codes.

2.4 You are responsible for which of your people get administrator access, what they do, and removing access promptly when someone leaves or changes role.

3. Credits, pricing, and billing

3.1 The Service runs on Credits. You buy Credits up front; you consume Credits as you use the Service. Pricing per Credit and what each Service action costs in Credits is published at driver.codes/pricing and shown in your account.

3.2 You can buy Credits at any time through your account using the published pricing.

3.3 Credits are non-refundable. Once purchased, Credits are not refundable to cash. Unused Credits remain in your account and expire 24 months from the date of purchase unless you reactivate the account or buy further Credits within that period (in which case the expiry resets to 24 months from the most recent purchase). We may extend expiry at our discretion.

3.4 We may change the pricing at driver.codes/pricing from time to time, with at least 30 days' notice through the account. From the effective date of the change, the new pricing applies to all subsequent Service usage, including usage funded by Credits already in your account — Credits are consumed at the rate in force at the time of consumption, not at the rate at which they were bought. If you don't want to accept a price change, you can stop using the Service before the effective date and ask us to refund the cash value of any unused Credits in your account at the rate at which they were bought; we'll process that refund within 30 days of your request.

3.5 If you have paid for Credits and we materially fail to provide the Service, we'll either restore the consumed Credits or refund their cash value, at our option.

3.6 Where you have applied for billing in arrears (rare; available on request), invoices are due within 14 days of issue and we may suspend the Service if invoices are overdue beyond 30 days.

3.7 Prices exclude VAT, which is added at the prevailing rate.

4. What we do — and what we don't promise

4.1 We provide the Service with reasonable skill and care. We continually improve and update it.

4.2 We aim for high availability but don't guarantee uninterrupted, error-free, or always-available service. The Service depends on third-party systems including DVLA, DVSA, app stores, mobile networks, and our hosting provider — none of which we control. If a feature isn't working, we'll work to fix it as quickly as is reasonable.

4.3 If you need contractual SLAs, named support, or guaranteed availability, that's an Enterprise Agreement conversation — see the introduction to these Terms.

4.4 The Service is not a substitute for professional advice. Decisions about your drivers (employment, contractor management, fleet risk) are yours to make. We provide information; you act on it.

5. Driver authority and DVLA

5.1 Driver Codes is registered with the DVLA under the Access to Driver Data (ADD) Controller Operating Model. We are the data controller for capturing each driver's signed authority, retrieving their record from DVLA, and delivering it to you. You are the data controller for deciding to invite a driver and using the result. The Data Sharing Agreement (Standard) sets this out in more detail.

5.2 We will only carry out a check where a valid driver authority is in place. If a driver revokes their authority, we'll let you know and we won't run any further checks against that authority. You'll need to invite them again to capture a fresh authority.

5.3 You confirm that you only invite drivers in respect of whom you have a lawful purpose to do so. We may decline or stop a check that we reasonably believe is being used for an improper purpose or outside the terms of our DVLA registration.

6. Your responsibilities

You agree to:

7. Acceptable use

You must not:

We may suspend or close your account if you breach this clause 7, with notice where reasonably possible and without notice where the breach is serious or urgent.

8. Stopping or pausing

8.1 You can stop using the Service at any time. There's no notice period and no termination fee.

8.2 To close your account, use the in-app account closure flow or email hello@driver.codes. We'll close the account within a reasonable period of receiving your request, subject to clause 11 (data after closure).

8.3 If you don't use your account for 12 consecutive months, we may close it on 30 days' notice. Unused Credits are subject to clause 3.3.

8.4 We may suspend or close your account on notice where you breach these Terms, where required by law or our regulators (including DVLA), where we have credible reason to believe the account is being misused, or where you have unpaid invoices.

9. Data protection roles

9.1 We act as data controller for the driver-facing parts of the Service — driver authority capture, DVLA retrieval, mandate retention, platform security and audit. Our Driver Checks Privacy Notice at driver.codes/legal/checks-privacy governs that processing.

9.2 You act as data controller for your decision to invite each driver, your receipt of the check result, and your use of the result in your business.

9.3 For the customer portal — your workspace, your administrators, your stored reports, your configuration — we act as your data processor. The Data Processing Addendum (Standard) at app.driver.codes/documents/dpa governs that relationship and applies automatically to your account.

9.4 The Data Sharing Agreement (Standard) at app.driver.codes/documents/dsa governs the controller-to-controller handover of check results between us. It applies automatically to your account.

9.5 You are responsible for your own data protection compliance — workforce privacy information, lawful basis, Appropriate Policy Document (where required), data subject requests about your processing, etc.

10. Security

10.1 We maintain a documented information security programme, summarised in our Security and Technical Measures Schedule at app.driver.codes/documents/security.

10.2 You implement appropriate security in your own environment, including:

10.3 If we become aware of a personal data breach affecting your data, we'll let you know without undue delay (and in any event within 48 hours of confirmation) and provide the information you reasonably need to fulfil your own obligations.

11. Data after closure

11.1 When your account is closed, you have 30 days of read-only access to export anything you need, then a further 60 days during which you can ask us for specific exports or, at your choice under Article 28(3)(h) UK GDPR, request a structured return of your customer workspace data in a commonly-used machine-readable format. After that, we'll delete your customer workspace data, except for:

11.2 We can provide a deletion certificate on request.

12. Intellectual property

12.1 We own everything in the Service — the software, the workflows, the look and feel, the documentation. You don't get any ownership rights, just a non-exclusive, non-transferable right to use the Service for your business under these Terms.

12.2 You own your customer data. We use it only to provide the Service to you (and as set out in the DPA and DSA).

12.3 If you give us feedback or suggestions, we can use them without restriction or payment, provided we don't identify you.

13. Confidentiality

13.1 Each of us will keep the other's confidential information confidential and use it only for the purposes of these Terms. This obligation continues for three years after your account closes.

13.2 Confidential information doesn't include information that's public, was already known, is independently developed, or is lawfully received from someone else without restriction.

13.3 Disclosure required by law, regulation, or a competent authority is fine — but where reasonably possible we'll tell each other before disclosing.

14. Liability

14.1 Nothing in these Terms limits or excludes liability for: death or personal injury caused by negligence, fraud or fraudulent misrepresentation, wilful misconduct, or any liability that can't lawfully be limited or excluded.

14.2 Subject to clause 14.1, each party's total aggregate liability under or in connection with these Terms — whether in contract, tort (including negligence), or otherwise — is capped at the total amount paid by you to Driver Codes in the 12 months preceding the event giving rise to the liability. If you've used the Service for less than 12 months at that date, the cap is what you've paid to date.

14.3 Subject to clause 14.1, neither party is liable for: loss of profit, loss of revenue, loss of business, loss of goodwill, loss of anticipated savings, or any indirect or consequential loss.

14.4 We maintain insurance: £1,000,000 professional indemnity (per claim) and £1,000,000 cyber liability (in aggregate per annum). For a significant data protection or cyber incident, this insurance — rather than the contractual cap in clause 14.2 — is the principal mechanism by which liability is intended to be met. Nothing in this clause 14.4 increases the cap in clause 14.2 or expands the categories of recoverable loss in clause 14.3. Certificate of insurance is available on request.

14.5 You'll indemnify us against third-party claims caused by your wilful misconduct, your material breach of clause 7 (acceptable use), or your unlawful use of the Service, subject to the cap in clause 14.2 except where clause 14.1 applies.

14.6 We'll indemnify you against third-party claims that the Service as we provide it infringes a UK intellectual property right, provided you tell us promptly, give us conduct of the defence, and reasonably help. We can choose to modify, replace or withdraw the affected feature with a pro-rata Credit refund. Subject to the cap in clause 14.2 except where clause 14.1 applies.

15. Changes to these Terms

15.1 We may update these Terms from time to time — for example, to reflect legal changes, security improvements, new features, or changes to our Service.

15.2 Material changes (those that materially reduce your rights or materially increase your obligations) — we'll give you at least 30 days' notice through the Service or by email. If you don't accept, you can stop using the Service before the change takes effect; otherwise continued use means you accept the change.

15.3 Non-material updates — we'll publish them at driver.codes/terms with a revised version date.

15.4 Updates to the DPA, DSA, Security Schedule, Sub-processor List, and Privacy Notices follow the change processes set out in those documents.

16. Boilerplate

16.1 Entire agreement. These Terms, the DPA (Standard), the DSA (Standard), the Privacy Notices, the Security Schedule, the Sub-processor List, and any pricing and signup terms shown to you, form the complete agreement.

16.2 No reliance. Neither of us has relied on anything outside these documents in entering this agreement, except for any fraudulent statement.

16.3 Assignment. You may not transfer your account or the agreement without our consent. We may assign to a corporate group member or to a successor in connection with a sale or reorganisation, on notice.

16.4 Severability. If any clause is invalid, the rest still applies.

16.5 No waiver. If we don't enforce something straight away, we haven't waived it.

16.6 No third-party rights. No one outside this agreement has rights under it (Contracts (Rights of Third Parties) Act 1999).

16.7 Force majeure. Neither of us is liable for failure caused by events beyond reasonable control (including failure of DVLA, DVSA, or other third parties we depend on), provided we take reasonable steps to mitigate. Your obligation to pay for Credits already used isn't affected.

16.8 Notices. We'll communicate with you through the Service, by email to your account address, or to your registered office. You can reach us at the contacts in clause 17.

16.9 Governing law. English law.

16.10 Jurisdiction. Courts of England and Wales — exclusive jurisdiction.

17. Contact

Note on regulator naming: at the version date of this document, the Information Commissioner's Office (ICO) remains the operative legal name of the UK data protection regulator. References in this document to the "Information Commission" anticipate the regulator's reconstitution under Part 6 of the Data (Use and Access) Act 2025. Our registration (ZA788385) is held with the regulator and will transfer to the Information Commission by operation of law on commencement of sections 118 and 119 of that Act.