Privacy Policy
Driver Hub is an app built solely for drivers who share rides with one another. This page states what we collect, why, who can see it, and how long we keep it.
Three things we do not do
- We do not track your location continuously. The app reads your coordinates only at the moment you tap a button — never in the background, and there is no live map. Four buttons do this, and they are handled in three different ways:
- Request this trip — the coordinates work out how far you are from the pickup point and are then discarded. We keep the distance, not the position.
- Passenger picked up and Passenger dropped off — these coordinates are stored with that trip, so the two drivers can reconcile payment and settle disputes. Only the two people on the trip and the admin team can see them; nobody else on the board can.
- My location on the pickup point picker — this coordinate never leaves your device. It only centres the map where you are standing so the right spot is easier to find; we neither receive nor store it. What is sent is the point you deliberately pin — that is the ride’s pickup address, not your position.
- There is no passenger app. Driver Hub serves drivers only; we collect no passenger data.
- We do not sell your data to third parties, and we do not use it for advertising.
What we collect
| Data | Why we need it |
|---|---|
| Phone number | It is your sign-in identity, and the way two drivers reach each other once a ride is matched. |
| Full name | So other drivers know who they are dealing with. |
| Licence plate, make, model, seat count | The driver posting a ride needs to know whether your vehicle suits the trip. |
| Driving licence photo | To verify you are a real driver holding a valid licence. Visible to administrators only. |
| Portrait photo, vehicle photo | For verification, and shown to other drivers so they can recognise the person and the vehicle. |
| ID card and vehicle registration photos (accounts registered before August 2026) | Part of the former document set. We no longer collect these; photos already submitted are retained and visible to administrators only. |
| GPS coordinates — read per action, when you tap | Three moments, three different purposes: tapping Request this trip estimates how far you are from the pickup point (then discards it); tapping Passenger picked up and Passenger dropped off records those moments of the trip; and tapping My location on the point picker only centres the map where you are — that coordinate never leaves your device. The app reads no location outside those three. |
| The pickup point you drop on the map | This is information about the ride you post, not your own position — you pin where the passenger is waiting, which may be tens of kilometres from you. Stored with the ride so the driver who takes it knows where to go. |
| Notification device token | To send push notifications about new rides or when you are selected. |
| Chat message content | Private one-to-one conversations between two verified drivers. |
| Wallet balance and transaction history | To record top-ups, withdrawals and any amounts arising in the system. |
| Ride history | So both parties can look back if a dispute arises after a trip. |
| Your voice — only while dictation is switched on | Turns what you say into text in the Trip details field. We never receive or store any audio recording — see Third parties. |
Who can see what
| Data | Visible to |
|---|---|
| Name, portrait photo, vehicle photo, vehicle details | Any verified driver |
| Phone number | Shown only after a ride has been matched, and only between the two drivers on that ride. Drivers who requested the ride but were not chosen see nobody's number. |
| Driving licence, ID card, vehicle registration photos | Administrators only |
| Coordinates from Request this trip | Shown to nobody, and not stored. The system works out a distance and discards the position; the posting driver sees only that number. |
| Coordinates from Passenger picked up / dropped off | Only the two people on that trip and the admin team. No other driver on the board can see them. |
| Chat message content | Only the two people in the conversation. Administrators can view it only when a message is reported. |
Photos that show your face
Four photos in your profile may show your face: your portrait photo, your driving licence, and — for profiles submitted before August 2026 — both sides of your national ID card. Because this is sensitive data, we spell out exactly how it is handled.
We store photographs, not biometric data. The system does not run facial recognition, does not measure facial features, does not create any biometric template (face template, faceprint or feature vector), and never uses a face to sign you in or to match identities automatically. The photos are kept as ordinary image files, exactly like every other document photo.
What they are used for. The portrait photo has two purposes: an administrator looks at it to verify the profile belongs to a real person, and it is shown to other approved drivers so they can recognise the person they are about to meet when handing over or taking a ride. The driving licence and ID card photos are visible to administrators only and are never shown to other drivers.
Where they are stored. On our own servers. They are not sent to Firebase, not sent to OpenFreeMap, and not sent to any analytics or advertising service. We do not sell, share or transfer photos showing your face to any third party.
How long we keep them. Until you delete your account. Deleting your account deletes the photos with it — see How long we keep it below. You can delete your account from inside the app, without contacting anyone.
Third parties
We use Google Firebase to store chat messages and deliver push notifications. Conversation data and notification device tokens are held on Google's infrastructure. We never sell your personal data, and we share it with no third party other than the services named in this section.
The pickup-point map. When you open the map to pin a pickup point, the app loads map imagery from OpenFreeMap (tiles.openfreemap.org), a free and open map service built on OpenStreetMap data. Those image requests go directly from your device to that service, so it can see your IP address and which part of the map you are looking at. We do not send your name, phone number, account ID or any other identifying information with those requests, and OpenFreeMap has no way of knowing who is looking. Your current location (the My location button) never leaves your device — it only recentres the map on where you are standing. What reaches our servers is the point you deliberately pin, which is the trip's pickup address.
Route estimates. When you pin both the pick-up and the drop-off while posting a trip, our server sends those two coordinate pairs to OpenRouteService (api.openrouteservice.org, operated by HeiGIT in Germany) to work out the distance and expected travel time, which we pre-fill in the Route field for you to edit. The request goes from our server, not from your device — so OpenRouteService never sees your IP address, your device or your identity, and we do not send your name, phone number, account id or any other identifying information. All they receive is two points on a map, attached to nobody. We keep the result for 30 days so the same route does not have to be looked up again. If the service is unavailable, the app works out a rough estimate on our own server and sends nothing out.
Speech recognition. When you use the dictate button to fill in trip details, the audio goes to your operating system's speech recognition service — Apple on iPhone, Google on Android — which returns the text. Driver Hub receives only the text; we never receive, store or transmit any audio recording. That audio processing is governed by Apple's or Google's own privacy policy. The button is entirely optional — you can type instead, and the microphone is open only from the moment you tap dictate until you tap stop.
How long we keep it
| Data | Retention |
|---|---|
| Coordinates from Request this trip | Not stored. They are discarded within the same request once the distance is worked out — there is nothing to set a deletion date on. (An earlier version said “deleted after 30 days”; since 17/09/2026 we no longer keep them, so the scheduled purge was removed too.) |
| Pickup and dropoff milestone coordinates, and the pickup point pinned on the map | Stored with the ride — they follow the trip-history retention in the row below, because they are part of that trip’s record. |
| Profile, document photos, device tokens | Until you delete your account. This includes the ID and vehicle-registration photos from profiles submitted before August 2026 — we stopped collecting those two, but photos already submitted are kept, because they are the only material available if an old profile is ever disputed. Deleting your account removes them too. |
| Ride history, wallet transactions, chat messages | No predetermined deletion date — see below. |
Ride history and wallet transactions are accounting records; chat messages are the data of both people in the conversation. They are therefore retained after one party deletes their account — but the displayed name becomes “Deleted account” and the phone number is no longer shown to anyone.
Your rights
- View and edit your profile — in the app, under Settings → My profile. Licence plate and vehicle model cannot be changed once your profile is verified, because they appear in the vehicle photo an administrator has already checked.
- Review submitted documents and resubmit if rejected — under Settings → Verify profile.
- Delete your account — see the account deletion guide.
Changes to this policy
When this policy changes, the new version is published on this page with its update date. The app opens this page directly, so you always read the current version without updating the app.
Contact
For questions about your personal data, email support@driverhub.tech.