No advertising-data sale
FleetOS does not describe personal information as a product sold to advertisers.
Privacy policy
Data should support the trip—not become the product.
This public policy explains the information FleetOS may process to operate office accounts, bookings, trips, payments, support and marketplace trust.
Public policy edition · Updated July 2026
Collect only what is neededControl accessUse for operationsSupport rights
Data lifecycle
A limited and accountable operating model.
Information is processed according to operational purpose, account role and applicable requirements.
01
Collection
Office profiles, bookings, trip states, payment status, support and device information.
02
Use
Account setup, dispatch, trip completion, reporting, safety and support.
03
Sharing
Relevant trip information between the office, assigned driver and rider.
04
Rights
Requests for access, correction or deletion subject to legal and operational requirements.
Privacy commitments
Clear boundaries for public understanding.
Final contractual and market-specific privacy terms may provide additional detail.
Role-based visibility
Operational information should be accessible according to account role and trip responsibility.
Service providers
Hosting, communications, maps, payments or support providers may process information for defined services.
Retention and security
Retention and safeguards depend on operational, contractual, legal and technical requirements.
Complete framework
Privacy and data-protection framework
Effective 14 July 2026. This public framework should be aligned with each signed commercial agreement and reviewed periodically by qualified Qatar counsel.
1. Who we are
FleetOS for Technology & Software L.L.C. operates the public website and develops Fleet Office, Fleet Ride, DriverX and marketplace services. Contact: info@fleetapp.net, Unit 210-218, Floor 2, Tech 2 Building, Qatar Science & Technology Park, Doha, Qatar.
2. Data we collect
We may collect registration and contact details, office and permit information, user roles, driver and vehicle records, booking locations, trip events, payment references, device and security logs, support communications, preferences and website interaction data.
3. Why we process data
Purposes include onboarding, identity and permission management, bookings and dispatch, trip safety, payments and reconciliation, customer support, fraud and security prevention, reporting, service improvement, legal compliance and communications requested by the user.
4. Legal bases and instructions
Processing is performed as needed to provide contracted services, comply with legal obligations, protect users and systems, respond to consent where required and pursue legitimate operational interests. Offices may act as controllers for records they place in the platform; FleetOS may act as processor or independent controller depending on the activity.
5. Location and trip data
Precise or live location is used only where required for booking, dispatch, navigation, safety, sharing authorized by the user, incident review or service records. Permissions can be controlled through the device, but disabling location can prevent trip functions.
6. Payment information
Card details are handled by licensed or contracted payment providers and are not intended to be stored in full by FleetOS. FleetOS may retain transaction references, amounts, status, refunds and reconciliation records.
7. Service providers and external processors
The public site currently uses Google Fonts. Office and driver registration is handled on FleetOS infrastructure and no longer passes through an external form provider. The operational service may also use hosting and content-delivery providers, map and geolocation services, communications providers, payment gateways, security monitoring and customer-support tools. These providers receive only the data needed for their function and are governed by contracts and applicable safeguards. Opening an external service is disclosed before the user leaves the site.
8. International transfers
Some providers may process data outside Qatar. Where a transfer occurs, FleetOS applies contractual, technical and organizational safeguards and evaluates applicable Qatar requirements before the transfer.
9. Retention
Account and commercial records are retained while the relationship is active and for the period required for legal, tax, dispute and security purposes. Trip, payment and support records follow documented retention schedules. Data is deleted or anonymized when no longer required, subject to legal holds and backup cycles.
10. Sharing
Data may be shared with the selected transport office, assigned driver, authorized account users, payment or technical providers, professional advisers, regulators or law-enforcement bodies where required. FleetOS does not sell personal data.
11. Security
Controls may include role-based access, encryption in transit, logging, backups, credential protection, incident response and supplier review. No system can be guaranteed absolutely secure; suspected incidents should be reported promptly.
12. Your choices and rights
Subject to applicable law, individuals may request access, correction, deletion, restriction, objection, consent withdrawal or information about processing. Requests are assessed against identity, contractual, safety, legal and record-retention requirements.
13. Children and family bookings
The service is not directed to children creating independent accounts. A parent, guardian, office or authorized adult may provide limited information for a family or school booking and remains responsible for authorization.
14. Cookies and website technology
The public site may use essential storage needed for navigation and security. Analytics or advertising cookies will not be activated without an appropriate notice and configuration. Google Fonts may cause the browser to contact Google infrastructure.
15. Complaints and contact
Privacy requests and complaints may be sent to privacy@fleetapp.net or info@fleetapp.net. FleetOS will acknowledge, verify and investigate requests. Individuals may also contact the competent Qatar authority where applicable.
16. Updates
This policy may be updated when products, providers or legal requirements change. Material updates will carry a new effective date and may be communicated to account administrators.
Questions about privacy?
Contact FleetOS using the official company email.