Your Privacy Matters To Us
Driver App — How We Use Your Data
Last updated: 30 July 2026
Applies to: the Mobvious Driver App (iOS and Android)
This page explains what data we collect through the Driver App, why we collect it, and how we use it. It is intended for drivers who use the app to carry out vehicle transport and delivery missions.
Mobvious processes this information only for operational, contractual, legal, and security purposes related to your work. We do not sell your personal data and we do not use driver data for advertising.
1. Who is concerned
This notice applies to professional drivers who log into the Mobvious Driver App with credentials provided by their employer or by Mobvious.
The app is a work tool. Data is processed so that missions can be assigned, executed, monitored, and documented.
2. Data we collect and why
2.1 Account and authentication
| Data | Why we use it |
|---|---|
| Phone number | Identify you and send a one-time login code (OTP) |
| Login session / authentication token | Keep you securely signed in while you use the app |
Purpose: secure access to your driver account and protection against unauthorized use.
2.2 Location (including in the background)
| Data | Why we use it |
|---|---|
| GPS position (latitude, longitude, accuracy, speed, heading, and related coordinates) | Track progress of ongoing deliveries |
| Location while the app is open and while it is in the background / device is locked (when permission is granted) | Continuity of tracking during active missions |
Purpose:
- support live tracking of deliveries and pick-ups
- help optimize routes and operational coordination
- provide more accurate estimated arrival times
- allow dispatch and operations teams to monitor mission status
- serve as evidence for legitimate operational or legal needs (for example disputes, incidents, or fines related to a mission)
Location is requested with your permission. Background location is used so tracking can continue when the screen is off or another app is in the foreground during a delivery.
We do not use location data for marketing or to sell location profiles to third parties.
2.3 Photos and files (camera / photo library)
| Data | Why we use it |
|---|---|
| Photos taken with the camera or selected from the library | Document vehicles, damage, condition checks, delivery proof, expenses, and mission-related files |
| Uploaded images stored in our cloud storage | Keep mission records for operations, customers, and compliance |
Purpose: create a reliable mission audit trail (vehicle expertise, damage reports, delivery documents, and similar operational proofs).
The camera is used only when you choose to take or attach a photo. We do not access your full photo library for browsing outside the system photo picker flow.
2.4 Signatures and handover details
| Data | Why we use it |
|---|---|
| Digital signature (image of the signature) | Confirm handover / receipt at pickup or drop-off |
| First name and last name associated with the signature | Identify the person who signed |
| Optional confirmation that expertise conditions were agreed | Document acceptance of vehicle condition at handover |
Purpose: formal proof of delivery, collection, or condition agreement between parties involved in the mission.
2.5 Mission and operational activity
| Data | Why we use it |
|---|---|
| Mission status updates (accept, refuse, arrive, complete, pauses, etc.) | Run and monitor the delivery workflow |
| Comments, justifications, and operational notes you enter | Explain delays, refusals, issues, or special circumstances |
| Time-clock / timesheet entries (when enabled) | Record working time for payroll and compliance processes |
| Vehicle expertise and inspection inputs | Record vehicle condition, damages, and related checks |
Purpose: execute contracts with customers, coordinate logistics, ensure quality of service, and maintain accurate operational records.
2.6 Push notifications and device information
| Data | Why we use it |
|---|---|
| Push notification token | Send mission alerts, updates, and service notifications |
| Basic device information (for example platform, model, OS-related device metadata) | Ensure notifications and the app work reliably on your device |
Purpose: inform you of new missions, changes, and important operational events in near real time.
You can control notification permission in your device settings. Refusing notifications may limit your ability to receive mission alerts promptly.
2.7 Technical, diagnostic, and support data
| Data | Why we use it |
|---|---|
| Crash reports and technical error logs (via our error-monitoring tools) | Detect, diagnose, and fix app bugs and stability issues |
| App version and related diagnostic metadata | Support troubleshooting and continuous improvement of the service |
Purpose: maintain a secure, stable application and improve reliability for drivers.
Diagnostic tools are used for error monitoring and product quality, not for advertising analytics.
3. How the data is used (summary of purposes)
We use Driver App data to:
- Authenticate drivers and protect accounts
- Assign and execute vehicle transport missions
- Track delivery progress (including background location when permitted)
- Document vehicle condition, damages, signatures, and delivery proofs
- Coordinate operations between drivers, dispatch, and customers
- Record working time when time-clock features are used
- Notify drivers of operational events
- Secure, maintain, and improve the application
- Comply with legal obligations and defend legitimate rights (including evidence related to missions)
4. Legal bases (EU / GDPR overview)
Depending on the processing activity, Mobvious relies on one or more of the following bases:
- Performance of a contract (providing the driver tools needed to perform missions)
- Legitimate interests (operations, security, fraud prevention, service improvement, evidence of mission execution), balanced against your rights
- Legal obligations where applicable (for example employment, tax, or transport-related requirements)
- Consent where required by law for specific device permissions (location, camera, notifications) — you can withdraw device permissions in system settings, understanding that some app features may no longer work
5. Who can access the data
Access is limited to people and systems that need it to operate the service, for example:
- Mobvious operations and support teams
- Your employer / partner organization (when you drive on their behalf through Mobvious)
- Customer organizations involved in a mission, only for data relevant to that mission (for example delivery status, proofs, or expertise documents)
- Technical service providers acting on our instructions (hosting, push notifications, crash reporting, cloud file storage)
We do not sell personal data.
We do not share driver location or mission data with unrelated third parties for marketing.
6. Data retention
We keep data only as long as needed for:
- mission execution and customer service
- operational records and quality control
- legal, accounting, insurance, or dispute-related requirements
- security and fraud prevention
Retention periods depend on the type of data and applicable legal obligations. When data is no longer required, it is deleted or anonymized according to our internal retention rules.
7. Security
We apply technical and organizational measures appropriate to the risk, including:
- authenticated access to the Driver App and APIs
- encrypted transport of data (HTTPS)
- restricted access to operational systems
- monitoring of technical errors to detect and remediate issues
No system is perfectly secure, but we work to protect your information against unauthorized access, loss, or misuse.
8. Your rights
Subject to applicable law (including the GDPR where it applies), you may have the right to:
- access your personal data
- rectify inaccurate data
- erase data in certain cases
- restrict or object to certain processing
- data portability where applicable
- withdraw consent for processing based on consent (for example by revoking a device permission)
To exercise these rights, contact us using the details below. You may also lodge a complaint with your local data protection authority.
Note: some data must be retained for operational or legal reasons (for example completed mission records or signed delivery proofs) and cannot always be deleted immediately.
9. Permissions you control on your device
| Permission | Used for | If refused |
|---|---|---|
| Location (precise / always) | Live tracking during missions | Mission tracking and some operational features will not work correctly |
| Camera | Photos of vehicles, damages, documents | You may still be able to select existing photos where allowed; camera capture will not work |
| Notifications | Mission alerts and service messages | You may miss time-sensitive mission updates |
You can change these permissions at any time in your phone settings.
10. International transfers
If service providers process data outside your country (for example cloud infrastructure or error monitoring), we take steps required by applicable law to protect that data (such as appropriate contractual safeguards).
11. Changes to this notice
We may update this page when the Driver App or our practices change. The “Last updated” date at the top will be revised accordingly. Significant changes may also be communicated through the app or other appropriate channels.
12. Contact
For questions about this notice or about personal data processed through the Driver App:
- Website: https://mobvious.me/
- Mail: support@mobvious.me
Join our Newsletter
Receive occasional updates on Mobvious services, platform improvements, and insights into vehicle logistics and transport operations.
By subscribing, you agree to our Privacy Policy

© 2025 Hike SRL | VAT: 1007.329.162
Avenue du Gui 1/2, 1180 Uccle