Offices
Maintain accurate information, lawful services, professional support and prepared vehicles and drivers.
Code of Conduct
Professional behavior protects every trip.
The FleetOS Code of Conduct sets expectations for offices, drivers, riders and platform participants.
RespectSafetyAccuracyAccountability
Shared standards
Four participant groups, one operating standard.
Conduct expectations follow the responsibility each participant carries.
Drivers
Follow assignments, communicate professionally, update trip states accurately and drive safely.
Riders
Provide accurate trip information, follow payment rules and treat drivers and office teams respectfully.
FleetOS
Maintain clear workflows, support reporting and apply marketplace rules consistently.
Unacceptable conduct
Behavior that can trigger review or restriction.
Serious or repeated violations may lead to investigation, suspension or removal according to applicable agreements.
Safety violations
Dangerous operation, threats, harassment or intentional misuse of safety tools.
Dishonesty
False profiles, manipulated records, fraudulent trips or misleading service information.
Discrimination
Unfair treatment based on protected or irrelevant personal characteristics.
Platform abuse
Unauthorized access, interference, scraping or misuse of accounts and records.
Complete framework
Conduct, reporting and enforcement standards
Effective 14 July 2026. This public framework should be aligned with each signed commercial agreement and reviewed periodically by qualified Qatar counsel.
1. Purpose
This Code sets minimum professional, safety and marketplace standards for offices, drivers, riders, employees, contractors and partners.
2. Respect and non-discrimination
Treat people fairly and respectfully. Harassment, threats, violence, discriminatory refusal, sexual misconduct, retaliation and abusive communication are prohibited.
3. Office standards
Offices must maintain licenses, verify drivers and vehicles, publish accurate service information, supervise dispatch, respond to riders, keep financial records and investigate safety or quality reports.
4. Driver standards
Drivers must be authorized, fit to drive, follow traffic and safety laws, use the assigned vehicle, avoid unsafe device use, protect rider privacy, follow the confirmed route unless safety requires otherwise and never manipulate fares.
5. Rider standards
Riders must provide correct pickup and passenger information, respect the driver and vehicle, avoid dangerous or unlawful conduct, supervise children and pay valid confirmed charges.
6. Marketplace integrity
Reviews, ratings, availability, prices, documents and identity must be genuine. Offices and drivers may not create fake demand, coordinate misleading reviews, divert protected transactions or conceal material service information.
7. Safety and emergencies
Immediate danger should be reported to local emergency services. Platform safety tools do not replace emergency services. Users should preserve relevant trip details and cooperate with investigations.
8. Privacy and confidentiality
Use personal and trip data only for the authorized service, support, safety or legal purpose. Do not publish contact, location, payment or identity data without authorization.
9. Reporting
Reports can be submitted through the responsible office, FleetOS support or the available safety channel. Provide the trip ID, facts, time and available evidence. Knowingly false reports are prohibited.
10. Review and response
Reports are triaged by urgency. FleetOS or the office may request information, preserve logs, contact involved parties, apply interim restrictions and document the outcome.
11. Corrective action
Actions may include education, warning, refund review, feature restriction, temporary suspension, removal from the marketplace, account termination or referral to authorities. Action is proportionate to risk, history and evidence.
12. Appeal
A person affected by a non-emergency enforcement decision may submit a written appeal within 14 days with new information or a reason the decision was incorrect. A reviewer not responsible for the original decision should assess the appeal where practical.
13. No retaliation
Retaliation against a person who raises a good-faith safety, compliance or conduct concern is prohibited.
14. Contact and updates
Questions or reports may be sent to safety@fleetapp.net or info@fleetapp.net. Material updates will be published with a revised effective date.
Need to raise a conduct concern?
Use the official contact channel and include relevant trip or account information.