Skip to content

Privacy Policy

Last updated 25 October 2026

Who is responsible

K3 Moves Ltd is the controller for the personal information described in this notice. We are registered in England and Wales under company number 12175783, with our registered office at Kitteon House, Kettering Parkway, Kettering Venture Park, Kettering, England, NN15 6XW. For questions about your information, a rights request or a complaint, email [email protected], call 020 3971 5888, or write to K3 Moves Ltd, Kitteon House, Kettering Parkway, Kettering Venture Park, Kettering, England, NN15 6XW.

This notice covers our vehicle movement services, website, driver applications, K3M office system, driver and client portals, mobile and watch apps and business communications. Staff may also receive privacy information specific to their employment.

Information we collect and its sources

We receive information from you, your device, the business arranging a movement, collection and delivery contacts, DVLA, our underwriter and the providers supporting our services. Information about another person, such as an emergency or handover contact, is used for the relevant contact or operational purpose. We ask clients to provide appropriate privacy information to contacts whose details they supply to us.

Enquiries: names, contact and company details, enquiry text, collection and delivery postcodes, service and fuel choices, browser details and a keyed hash of the IP address. Infrastructure and security logs may separately record the IP address.

Applicants and drivers: contact details, home address, date of birth, gender where provided, work history, parking information, emergency contacts, licence details and images, signatures and DVLA authority records. Compliance information can include identity documents, passport or DBS certificate references, CPC and tachograph details, training and signed forms. We use tax, company and bank details where needed for engagement and payment.

Movement and work records: assignments, vehicle and handover contacts, photographs and signatures, uploaded documents, messages, attendance, expenses, receipts, fuel and charging transactions, waiting time, equipment, damage, accidents, breakdowns, account transactions and disputes. Health, injury or offence information may form part of a relevant insurance or incident record.

Accounts, devices and payments: sign-in history, password hashes, two-factor settings, IP address, browser and device information, app version, push tokens and security events. Supported driver-app features can record screenshot events and battery information. Client records include billing contacts, invoices and payment references. Stripe processes card payments; K3M retains limited card information rather than the full card number.

Location and restricted operational visibility

We record location and time from driver check-ins, job and evidence actions, and background arrival or departure detection where the app supports it and device permission allows it. Fuel and charging transactions also provide times and merchant or charging-site information from which location observations can be derived. Transaction-derived observations differ in accuracy from device GPS and do not establish a person's current position.

Location information supports planning, safety, movement evidence, expense verification and disputes. Authorised staff can view operational records. Our access-code-protected driver map can show driver identifiers or operational names, recent locations, timestamps and sources to authorised map viewers for coordination.

A handover contact using a driver's name and validation code can see the driver's photograph and approval status. Relevant movement progress and handover evidence are available to the client or its nominated contacts. We limit these disclosures to their operational purpose; routine handovers do not include access to the driver's complete compliance file.

You can change location permission in device settings. Disabling it can prevent location-dependent features from working and may require another way to verify work. Device permission and the legal grounds for using information already collected are separate matters.

Why we use information

We use information to assess driver applications, verify driving entitlement, arrange training and appropriate insurance, plan and deliver movements, communicate with contacts, record handovers, manage payments and resolve enquiries, incidents and disputes. Account and security records help protect the service and prevent misuse.

Under Article 6 of the UK GDPR, contract necessity applies to steps you request towards your own contract and to fulfilling that contract, including agreed work and payments. For contacts or employees of a client company, our basis is normally legitimate interests in managing the business relationship and arranging and evidencing movements, rather than a contract with that individual.

Our legitimate interests also cover necessary application assessment, entitlement checks, insurance and training arrangements, operational planning, reliable evidence, security and dispute handling. We consider the need for those uses and their effect on people. You can object to processing based on legitimate interests.

We rely on legal obligation where needed for applicable tax, accounting, employment or road-transport duties. Consent is used for optional screen recording and where a particular use requires explicit consent. Reading a privacy notice or signing a DVLA authority does not give blanket consent to other processing.

Information identified as required for an application, driving entitlement, insurance, safety, payment or a particular job is needed for that step to proceed. Without it, we may be unable to assess an application, offer work or make the relevant payment. Optional information is not a condition of unrelated services.

DVLA, health and criminal offence information

For a DVLA driver check, we send the licence identifiers and other details required for that enquiry and receive the corresponding driving record. It can include licence status, entitlements, endorsements, points, disqualifications and restrictions. Checks support application assessment, training check-in and continuing entitlement or insurance assessment. Vehicle enquiries use vehicle registration details and are separate from driver-record checks.

The D906 Access to Driver Data (ADD) declaration separately authorises DVLA to release driver information. The declaration presented for signature sets its scope and expiry, including stopping driving for us or three years, whichever happens first. It does not authorise unrelated disclosure. You can contact us to withdraw or correct an authority; driving work may need to pause if entitlement cannot be verified.

For criminal offence information needed for an insurance purpose, our statutory condition is the Data Protection Act 2018, Schedule 1 paragraph 20, extended by paragraph 37, together with an Article 6 lawful basis. The use is limited to relevant insurance advice, arranging, underwriting, administration or claims, subject to the statutory conditions. We do not request spent convictions unless legally permitted and necessary.

For health information needed for insurance, we may rely on Article 9(2)(g) with Schedule 1 paragraph 20 where its conditions are met. Health information needed for legal claims may be processed under Article 9(2)(f). Other uses need their own applicable condition, such as explicit consent where appropriate. Our Data Protection and Retention Policy includes the appropriate policy document and the safeguards for insurance-related health and offence information.

Underwriters, accidents and other recipients

We do not sell personal information or disclose it for another organisation's marketing. We send driver information to our underwriter only where needed for a specific insurance assessment, cover decision, accident or claim. Depending on the matter, this can include identity and contact details, relevant licence results, incident reports, vehicle evidence and necessary health or injury information. Disclosure is limited to the relevant evidence and the people handling the matter.

The underwriter makes its own insurance decisions and may act as a separate controller. You can ask us for the identity and privacy notice of the underwriter handling your case.

Service providers receive the information needed for their part of our work. These include UK application hosting and DigitalOcean file storage; MailerSend SMTP email and Vonage SMS; Apple push notifications and Google/Firebase where used by the Android app; Meta for WhatsApp; Stripe payments; Soldo expense cards and Paua charging, including card-user setup and transactions; Network Hub/AFD address lookup; Mapbox and Google Maps routing and location services; Google reCAPTCHA; Microsoft staff sign-in where used; Sentry app diagnostics and Laravel Nightwatch server monitoring; and MoDel/LeaseLink and client fleet systems for agreed movement details. Depending on the service, providers act on our instructions or as controllers for their own activities.

We may also disclose necessary information to police, courts, regulators, tax authorities and professional advisers where legally required or justified to protect rights or handle a claim. Those disclosures are considered individually. Operational disclosures to clients, handover contacts and authorised map viewers are limited as described above.

Diagnostics, messaging and optional recording

The iOS app uses Sentry for crash and performance diagnostics. Its configuration minimises direct identifiers and scrubs selected location, token and file-link details. Optional session replay requires a separate choice in the app. Text and images are masked when replay is enabled. You can change your choice in Settings, Diagnostics and screen recording. Withdrawal does not affect earlier lawful processing.

WhatsApp messages are processed by Meta as well as K3 Moves. Reply STOP to stop optional WhatsApp messages, or contact us to choose another channel. Essential contractual, safety or legal messages may still need to reach you through another channel. Application acknowledgements are not marketing consent.

Storage, security and international transfers

Access to personal records is restricted by staff responsibilities. Sensitive database fields, including DVLA payloads, are encrypted, and passwords are held as one-way hashes. HTTPS, account controls and audit records support security. These safeguards reduce risk, although no system can guarantee that an incident will never occur.

Our application servers are in the UK. Our designated standard for file storage is DigitalOcean London (LON1). Some records are held in EU storage, and service providers may store or access information outside the UK. Sentry uses its EU (Germany) region.

UK adequacy regulations cover EU destinations. Our policy for other restricted transfers requires a valid route, such as another applicable adequacy decision or the UK International Data Transfer Agreement or UK Addendum, with the necessary assessment and additional protection. You can ask which destinations and safeguards apply to your information and request a copy of relevant safeguards, subject to necessary redactions.

Retention and account closure

We keep personal information for its purpose, applicable legal duties and necessary claims evidence. Our retention schedule explains the normal periods and exceptions. Website enquiries normally expire after 24 months. Application personal details and licence images normally enter the purge process 90 days after a decision or being marked stale, unless a justified hold applies. Ongoing driver records and separately retained authority or insurance evidence may remain necessary.

Routine DVLA history retains the newest three checks plus the newest successful check if older. Checks used in an insurance case can be kept as case evidence beyond that count. Our policy is to review their continuing need when the case and driving engagement end; the count limit is not an expiry date.

Clients can request account deletion through the mobile app where available. Drivers cannot delete their account in the mobile app: contact our office to close it or to request erasure. Closure deactivates access. Client and staff accounts normally enter the purge process after 90 days. If a closed driver account has no work, payment or supplier history, we delete data we do not need to keep 90 days after closure, such as unsigned documents and uploads, photographs, location check-ins, unsigned bank details requests, availability, device data, messages and training attendance. We keep audit records and signed copies, including a signed bank details confirmation and the bank details it records. We keep DVLA records and licence images until two years after the last check, or two years after signing a DVLA authority if no check was made. The account record is deleted when none of these remain. A driver record with work, payment or supplier history is kept: 12 months after the driver leaves we delete the location check-ins recorded from their device, their profile photographs and any unsigned bank uploads. We keep signed bank confirmations. Each DVLA check is deleted two years after it was made, once the driver has left, and licence images and the signed DVLA authority go when no check remains inside that period. If a charge, dispute, claim, balance, expense or pay is open at that point, we delete them once it is settled. The driver record and remaining records are kept and reviewed under our retention schedule. Invoices, claims and other necessary legal records may remain. We consider erasure and restriction requests separately. Restricted backup copies expire through rotation and remain subject to earlier erasure or restriction decisions if restored.

Automated checks and your rights

DVLA rules can automatically suspend access to new driving work if a record is invalid or shows disqualification or another critical result. The rules compare returned licence status, dates and entitlements, so incomplete or incorrect information can affect the result and work opportunities. You can obtain an explanation, give your view, challenge the result and request meaningful human review by contacting us. A review cannot permit unlawful or uninsured driving. Additional safeguards apply to decisions involving sensitive information.

Depending on the processing, you can request access, correction, erasure and restriction. Portability applies to information you provide that is processed automatically on the basis of consent or your own contract. You can object to legitimate-interest processing, explaining your circumstances. We stop that processing unless overriding legitimate grounds or legal claims justify its continuation. You can always object to direct marketing and withdraw consent where we rely on it. We explain any legal limit on a request and your options to challenge our decision.

Rights requests do not require a special form. We normally respond without undue delay and within one month, free of charge. If a legally permitted extension, identity check or clarification affects the deadline, we explain what is needed and why. Any exceptional charge or refusal is subject to the statutory requirements.

Complaints and updates

Our Complaints Procedure provides a route for privacy concerns. We acknowledge data-protection complaints within 30 days, investigate appropriately, keep you informed and communicate the outcome without undue delay. You may also complain to the Information Commissioner's Office, telephone 0303 123 1113, or seek a judicial remedy. Contacting us first does not remove those rights.

We review this notice when our use of information changes and publish the revised date. We explain material new uses before they begin, unless a legal exception applies.