TravelServe Limited Privacy Policy

This policy has two parts: section 1 covers this website, and section 2 covers the TravelServe Driver mobile app used by drivers and Meet & Assist agents.

1. Website

Location and Technical Data Collection

We are committed to protecting and respecting your privacy. This section explains how location and technical data is collected and used when you visit or use our website or services.

1.1 Location Data

We may collect information about your geographical location derived from IP address or similar technical indicators. Location data is used to:

Improve website performance and user experience
Provide location relevant content and services
Detect and prevent fraud and unauthorized access
Support internal analytics and reporting

Location data does not directly identify individuals and is processed in accordance with applicable data protection laws.

1.2 Technical Data

When visiting our website we may automatically collect:

IP address
Browser type and version
Operating system and platform
Device type
Referral source
Pages viewed
Website navigation paths
Date and time of visits
Location

This data is collected using cookies, server logs and similar technologies.

1.3 Purpose of Processing

Technical and location data is processed to:

Maintain website security and stability
Administer and manage website systems
Analyze website usage and interaction
Improve website functionality, structure and content
Monitor performance and usage trends

1.4 Legal Basis

Processing is based on legitimate business interests in operating, improving and securing services. Consent will be obtained where required by law.

1.5 Data Sharing

Location and technical data is not sold, rented or traded. Data may be shared with trusted service providers subject to confidentiality and data protection obligations.

1.6 Data Retention

Data is retained only for as long as necessary for legal, operational or regulatory purposes.

1.7 Your Rights

You may request access, correction or deletion of personal data and object to or restrict processing in accordance with data protection law.

2. TravelServe Driver App

Last updated: 16 October 2026

2.1 Who we are

TravelServe Driver (the "App") is provided by Travelserve Limited ("TravelServe", "we", "us"), registered in England and Wales, company number 08814015, registered office Novotel London Heathrow Airport, Cherry Lane, West Drayton, UB7 9HJ.

The App is used by professional drivers and Meet & Assist agents who work for, or are contracted to, a transport operator that uses the TravelServe platform (your "Operator"). Your Operator decides why your personal data is collected and is the data controller for it. TravelServe processes that data on the Operator's behalf as a data processor, and is the controller only for the account security and service-operation data described in section 4.

If you have a question about how your Operator uses your data, contact them first. You can also contact us at zafir@travelserve.net.

2.2 Who can use the App

You can only sign in if your Operator has created a profile for you. The App does not offer self-registration and is not intended for anyone under 18.

2.3 What we collect and why

2.3.1 Identity and contact details

Phone number — used as your login. A one-time code is sent to it by SMS each time you sign in.
Name and profile photo — set by your Operator. They are shown to dispatchers alongside your live position, and to passengers on the jobs you are assigned to.
Email address, date of birth and home address — entered by you during onboarding, so your Operator can verify your identity and meet licensing requirements. Your email is verified with a one-time code.

Lawful basis: performance of your contract with your Operator; the Operator's legal obligations under private-hire licensing.

2.3.2 Compliance documents

You upload photographs of documents your Operator needs to keep on file. Depending on your Operator these can include a driving licence, PCO/private-hire licence and badge, DVLA check code, proof of address, right-to-work evidence (passport, visa or share code), National Insurance proof, a Group 2 medical certificate, an Enhanced DBS certificate, safeguarding and disability-awareness training certificates, airside passes, vehicle V5C, MOT and insurance documents, plus the document number, issuing authority and expiry date you type in.

Some of these are special category data (health) or criminal offence data (DBS). They are processed because your Operator is legally required to hold them to allow you to drive or work airside, under the employment and legal-claims conditions in Schedule 1 of the Data Protection Act 2018, and your Operator maintains an appropriate policy document covering this.

Documents are stored in a private storage area. They are viewable by authorised staff of your Operator (for example onboarding and compliance staff) and by TravelServe engineers only where necessary to run or support the service.

2.3.3 Location

This is the most important part of this policy, so we describe it exactly.

When tracking runs. Location tracking starts when you go online in the App (start a shift or check in) and stops when you go offline, check out, sign out, or close the App. It runs for the whole shift, including between jobs, and continues in the background when the App is minimised or your screen is off. It does not run when you are offline, and it does not restart by itself after a reboot.
How often. Roughly every 10 metres of movement while you are moving, and a heartbeat position about every 10 seconds while you are stationary. During turn-by-turn navigation the position is snapped to the road.
What is sent with each position. Latitude and longitude, heading, speed, accuracy, altitude, a timestamp, your name and profile photo, your device battery level and whether it is charging, and a motion-activity label (see 3.4).
Who sees it. Your Operator's dispatch team, live on their map. On active jobs, your position and estimated arrival time are also shown to the passenger and to anyone they have shared a tracking link with.
Why. So your Operator can assign the nearest suitable driver, monitor jobs, detect arrival at pickups and airports, and give passengers accurate arrival times.
Where it goes. Positions are sent to the TravelServe servers over an encrypted connection and held in a short-lived live store: a live position expires after 2 minutes without an update, and your last position is kept for up to 12 hours after you go offline so dispatch can see where you finished. Positions are also relayed through a realtime messaging service (Ably) to the dispatch screens.
What is kept longer. When you enter or leave a defined area (for example an airport or a pickup zone), and when a job changes status (arrived, passenger collected, completed), the position at that moment is stored with the job record and kept for as long as the job record is kept (see section 6). Your full movement history is not stored long-term.

Lawful basis: performance of your contract with your Operator, and the Operator's legitimate interest in running a safe and efficient dispatch operation. You control tracking by going online and offline; you can also revoke the permission in your phone settings, but you will not be able to receive jobs while it is off.

2.3.4 Motion and activity

With your permission the App uses your phone's motion sensors (Core Motion on iOS, Activity Recognition on Android) to classify whether you are in a vehicle, walking, or still. This is used to reduce battery use, to detect when you have parked and walked away from your vehicle, and to record the approximate parking spot so dispatch can see it. The current activity label is sent with each position and shown to dispatch. Raw sensor data never leaves your phone.

2.3.5 Device and notification data

Push notification token, device model, device name (as set in your phone settings) and operating system version — so we can deliver job offers and alerts to the right device.
Battery level and charging state — sent with your position so dispatch can see if your phone is about to die during a job.
Error reports. If the App hits an unexpected error, it sends us the error message, the screen it happened on, your phone model, operating system version and App version, so we can fix it. No third-party analytics or crash-reporting service is involved, the App contains no advertising SDKs, and map-usage telemetry is switched off.

2.3.6 Jobs, messages and earnings

Job details including pickup and drop-off addresses, passenger name, phone number and flight details — shown to you so you can do the job. You must only use passenger details for that job.
Messages you exchange with dispatch or passengers through the App, including read receipts and typing indicators, and any location you choose to share in a message. Messages are stored with the job.
Earnings and job history — your per-job fare, daily, weekly and monthly totals. The App does not collect bank or card details; any payment details are held by your Operator outside the App.
Shift history — when you started and ended shifts and which vehicle you used.

2.3.7 Vehicle details

Registration number, make, model and year of the vehicle you drive, plus its documents (3.2). A stock image of the vehicle model is fetched from a third-party image service using only the make, model and year.

2.4 Data we are the controller for

TravelServe is the controller for: your login session and authentication tokens, security and audit logs, and technical records needed to keep the service running. We use these to keep your account secure, prevent misuse, and meet our legal obligations.

2.5 Who we share data with

We do not sell your data and do not share it for advertising. We use the following processors, each bound by a data processing agreement:

Provider	Purpose	Data involved
Supabase	Database, file storage and sign-in	All data in this policy
Railway	Hosting for the TravelServe API	All data passing through the API
Twilio	Sending SMS sign-in codes and invitations	Phone number, code
Resend	Sending emails (verification codes, notifications)	Email address, name
Upstash	Short-lived live position store and job queues	Live position and status data
Ably	Realtime delivery of positions and messages to dispatch	Live positions, status, message content
Mapbox	Maps, routing, address search and turn-by-turn navigation	Your position during navigation and search; telemetry disabled
Expo, Apple and Google	Push notification delivery	Push token, notification text
TransistorSoft	Background-location software licence validation	Anonymous licence check only; no location data

Hosting locations: the European Union (our servers run in the Netherlands and our database provider's EU region). Where data leaves the UK we rely on the UK International Data Transfer Agreement or UK adequacy regulations.

Your Operator also sees your data, as described above, and passengers see your name, photo, vehicle and live position on active jobs.

2.6 How long we keep data

Data	Retention
Live position	Expires 2 minutes after last update; last position kept up to 12 hours after going offline
Positions attached to job, geofence and terminal events	2 years, to allow for fare disputes, insurance claims and regulator enquiries. After that, geofence and terminal position records are deleted and the GPS position is removed from job status records. The job status history itself (without location) is kept for the life of the job record for accounting
Account, profile and documents	While you work with your Operator, then removed or anonymised within 30 days of offboarding, unless the Operator must keep specific documents longer by law
Messages	For the life of the job record
Sign-in and security logs	12 months

2.7 Your rights

Under UK GDPR you can ask to access, correct, delete or restrict your data, object to processing, and receive a copy in a portable format. Because your Operator is the controller, we will pass your request to them or help them respond. You also have the right to complain to the Information Commissioner's Office (ico.org.uk).

Deleting your account

You can request deletion from inside the App: open your profile, choose Delete Account, and confirm. This signs you out and sends the request to your Operator, who will close your account and remove your personal details within 30 days. Completed job records are kept for accounting but are anonymised so they no longer identify you. Documents your Operator must keep by law are retained for the legally required period only. You can also email zafir@travelserve.net with the phone number you sign in with.

2.8 Security

Data is encrypted in transit (TLS) and at rest. Access to documents is by short-lived signed links limited to authorised users. Sign-in uses one-time codes rather than passwords, and your session is stored in your phone's secure keychain.

2.9 Changes

We will post changes here and, for material changes, notify you through the App or your Operator.

2.10 Contact

Travelserve Limited, Novotel London Heathrow Airport, Cherry Lane, West Drayton, UB7 9HJ. Email: zafir@travelserve.net. We have not appointed a Data Protection Officer; privacy questions go to the email above.