Laravel

Google Play / user data

User Data Policy

Last updated: 13 September 2026

1. Who we are

This policy applies to the Serv3 dispatch website and the Android driver app used with it. The platform is operated from serv3.co.uk / serv3.org. It is a business logistics tool for dispatchers and employed or contracted drivers, not a consumer social app.

2. What the apps do

Dispatchers create jobs (collections and deliveries), assign drivers, track vehicles on a live map, and store proof of collection/delivery. Drivers log in on Android to receive jobs, update status and ETA, send GPS position, and upload POC/POD photos and signatures.

3. Data we collect

Data type Examples Why
Account Name, email or driver ID, password, plate number, vehicle type Login and job assignment
Location (precise) GPS latitude/longitude, speed, accuracy, time, vehicle ID Live map and route history for dispatch
Photos and files POC/POD photos, signatures, job PDFs, licence/MOT/insurance scans Proof of work and compliance documents
Job / operations Dockets, customer names, addresses, phone numbers on jobs, notes, status, ETA To run collections and deliveries
Device identifiers Firebase Cloud Messaging (FCM) token Push notifications for new or updated jobs
Technical logs App/server errors, request time, IP as processed by the host Security and reliability

4. Location

The Android driver app collects precise location so dispatch can see the vehicle on the live map and keep route history. Location is used only for fleet operations. We do not sell location data. Drivers should allow location while using the app for tracking to work. If location permission is refused, login and job lists may still work, but live tracking will not.

5. Photos, signatures and documents

Photos and signatures are uploaded as proof of collection (POC) or delivery (POD). Driver documents (licence, MOT, insurance, company ID) may be stored with expiry dates. These files are visible to authorised dispatch users of the same platform, not to the public.

6. Notifications

If the driver allows notifications, we store an FCM token on the driver profile and send job alerts through Google Firebase Cloud Messaging. Tokens are not used for advertising.

7. Who can see the data

Data is used by the operating company and its dispatch staff to manage jobs. It is not sold. We do not use it for advertising or credit scoring. Service providers that process data on our behalf include: website hosting, Google Firebase (push notifications), and Google Maps / Document AI when a dispatcher uses distance calculation or document import. Those providers process data only to provide that service.

8. Retention

Account and job records, GPS history, photos and documents are kept while the account is active and as long as needed for operational, legal or accounting reasons (for example proof of delivery). When a driver or user is deleted by an administrator, related access is removed. You can ask us to delete or correct personal data using the contact below.

9. Security

Access to the dispatch website and APIs requires a login. Passwords are stored hashed. The public website is served over HTTPS. Only authorised staff should access driver and job data.

10. Children

The apps are for adult professional drivers and dispatch staff. They are not directed at children under 13 (or under 16 where a higher age applies). We do not knowingly collect data from children.

11. Your rights

Depending on where you are (including the UK GDPR), you may ask to access, correct, delete or export your personal data, or to restrict processing. Drivers should first contact their dispatcher. You can also write to us using the contact below. You may complain to the UK Information Commissioner’s Office (ico.org.uk) if you are in the UK.

12. Contact

For privacy or data-deletion requests: