¶ Compliance Disclaimer & Client Guidance
¶ 1. Scope of Services & Regulatory Position
MyTaxiCRM provides a fleet-management software platform that allows licensed vehicle-operators to manage the internal booking, dispatching, tracking, driver-workflow and data-recording processes of their limousine, chauffeur & premium-transport operations in the Emirate of Dubai, United Arab Emirates. MyTaxiCRM is used exclusively by the fleet operator (or authorised delegate) – it does not receive booking requests directly from end-passengers, nor does it function as a public customer-booking engine or aggregator app.
Consequently, while MyTaxiCRM is designed to align with and support the regulatory requirements of the RTA (including the rules applicable to luxury-vehicle passenger-transport services) it is not itself an «approved electronic booking system» for end-consumer passenger-requests under RTA’s limousine regulations; the regulatory obligation to hold an RTA-licence for the booking-interface, or to use an RTA-approved public-booking app, remains with the fleet-operator or aggregator that receives the passenger’s request, whichever is required by law or contract.
¶ 2. Regulatory Context & Operator Obligations
Fleet operators in the Emirate of Dubai conducting passenger transport via luxury/limousine vehicles must comply with the RTA regulatory framework (for example: Executive Council Resolution No. 6 of 2016 and Executive Regulation No. 516/2022) which, among other things, requires:
- A permit to operate the activity of passenger-transport by luxury vehicles;
- Linking of the company’s electronic systems or smart-applications to the RTA digital platform as designated by the RTA;
- Full logging/record-keeping of bookings/trips, and maintaining such records for a minimum period (e.g., six months) for reference;
- Ensuring that bookings are only accepted via authorised channels (approved electronic platforms, call-centres, etc.), and that undocumented or unregistered trips and direct driver-to-passenger street pickups without confirmed pre-booking are not permitted.
In addition, recent regulatory circulars issued by the RTA further emphasise the enforcement of the pre-booking mechanism across all luxury transport operations – requiring that every trip be registered through approved electronic channels before commencement, with full passenger and trip details recorded and retained.
To facilitate operator understanding, infographics illustrating the approved pre-booking flow have been introduced, providing visual clarity on the required process and compliance checkpoints.
⚠️ The information shown above originates from official RTA materials. MyTaxiCRM is not the author and assumes no responsibility for the accuracy, completeness, or enforcement of this information by the RTA or its representatives.
¶ 3. How MyTaxiCRM Supports Compliance
By deploying MyTaxiCRM as the fleet-operator backend tool, the operator can significantly simplify compliance with the above obligations. MyTaxiCRM assists the fleet in:
- Recording passenger booking details (name, contact number, trip date/time, pick-up/drop-off) in the system prior to trip commencement;
- Retaining full trip-data and booking metadata for the required retention period (e.g., six months or more) in a secure, auditable format;
- Restricting driver access to trips only via logged and authorised dispatch workflows (thereby reducing risk of undocumented or direct-driver-accepted requests);
- Integrating with vehicle-tracking, driver app and analytics modules to provide oversight, audit-trail and real-time monitoring of trip execution – facilitating transparency and easier regulatory review;
- Supporting generation of internal reports, dashboards and audit-logs that enable the fleet-operator to demonstrate to RTA (or relevant inspectors) that its processes are compliant and that control measures are in place.
¶ 4. Clarification of MyTaxiCRM’s Role
It is important for the fleet operator and its customers to understand that while MyTaxiCRM provides the internal operational platform for the licensed operator, it does not assume the role of the front-end public booking portal or aggregator. Accordingly:
- The fleet operator remains responsible for ensuring that its customer-facing booking interface (whether it is an app, website, call-centre or aggregator integration) is appropriately authorised under RTA regulation or under the license-type held by the operator;
- Any booking requests received outside documented or registered channels (e.g., direct driver acceptance, street hail, undocumented chat requests) remain the responsibility of the operator to prohibit under its licence-conditions, and MyTaxiCRM cannot substitute for the regulatory threshold of «approved electronic booking channel» if the licence requires it;
- MyTaxiCRM should be viewed as the internal compliance-enablement system: the operator uses MyTaxiCRM to manage and document the backend process in accordance with RTA's regime, but MyTaxiCRM itself is not the «regulated booking interface» from the passenger's initial request point.
¶ 5. Clarification for Fleet Operators
By using MyTaxiCRM, a licensed limousine operator in Dubai can:
- Strengthen its compliance-framework by ensuring structured pre-booking logging, record retention and audit-trail capabilities;
- Reduce operational risk of inadvertent breaches of RTA pre-booking or street-pickup prohibition rules;
- Demonstrate to regulators or auditors that the operator’s dispatch and booking-management architecture is aligned with RTA expectations;
- Focus its regulatory-compliant booking interface on the customer-facing side (aggregator app, call-centre, approved platform) while using MyTaxiCRM as the robust internal operations, dispatch and compliance system.
¶ 6. Legal Disclaimers
MyTaxiCRM does not provide legal advice. Fleet operators should ensure that they hold all necessary licences, approvals, and contracts with the RTA or relevant authority for their booking interface and vehicle-transport activity. Operators are responsible for compliance with all applicable laws, regulations and contracts in the Emirate of Dubai.
MyTaxiCRM's role is limited to software provision, configuration and support of internal fleet-operations; it does not replace the operator’s regulatory obligations or licence-holder status.