Op den Inhalt sprangen

This document is not available in this language and is shown in English. Read the binding Arabic version

Versioun 1.27 · Stand 2026-11-16

Privacy Policy — United Arab Emirates

This policy informs you how personal data is processed on the Emaride platform in the United Arab Emirates (www.emaride.ae and the Emaride app for the UAE market). It is information under Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data ("PDPL"). It is not a consent and does not require your acceptance.

1. Controller

EMARIDE L.L.C-FZ Limited liability company (Free Zone), Meydan Free Zone Meydan Grandstand, 6th floor, Meydan Road, Nad Al Sheba Dubai, United Arab Emirates Licence number: 2535707.01 Represented by its manager Ramez Mohamad Alkhalaf E-mail: info@emaride.ae

Data protection requests: privacy@emaride.ae

2. Scope

This policy applies to passengers, drivers and contact persons of fleet partners and business customers who use the Emaride platform in the UAE (together the "Platform"), and to persons who apply to become a fleet partner using the application form on www.emaride.ae, and to persons who report content using the report form, also without an account. Users in the European Union are covered by the privacy policies of Emaride EU on www.emaride.lu; their data is stored separately in the EU.

3. Categories of Data Processed

Category Examples
Master / account data name, e-mail, phone number, language setting
Profile and address data saved addresses (max. 3), preferred settings
Location data pickup and destination, stop, GPS position during an active ride; for drivers, the last position while online (each new position overwrites the previous one, no movement history)
Recurring bookings weekdays, pickup time and route of recurring trips
Ride data bookings, route, timestamps, status, OTP/QR verification, no-show events
Flight data flight number and travel date, only if you enter them when booking a ride to or from an airport (voluntary; a pickup at an airport with a meeting point requires the flight number); the terminal and the scheduled or expected departure or landing time we receive for them
Payment data payment method (token), transaction and invoice data, tips
Ratings ratings given by you and given about you
Driver data date of birth, driver records (see below), vehicle data and vehicle records (see below), weekly photo of the vehicle interior as proof of cleaning
Fleet partner records company records of the establishment (see below)
Fleet partner applications data from the application form (see below)
Support / communication data tickets, chat logs with (possibly AI-assisted) support
Ride chat messages between passenger and driver while the driver is on the way and waiting (preset messages or free text) with delivery and read status; phone numbers, email addresses and links are hidden automatically before storage; push notifications do not contain the content
Device and usage data device and app version, push token, log and error data
Apple/Google sign-in identifier of your Apple or Google account, e-mail address (with Apple, possibly a relay address), name if shared; only if you use this sign-in

Company records of fleet partners. Under D2.4 of the Terms of Use for the UAE, a fleet partner stores the records of its establishment on the Platform: the trade licence of the Department of Economy and Tourism, the tourist transport permit of the RTA, the Emirates ID and the passport of its owner, the VAT registration certificate (or, if the establishment is not registered for VAT, its own declaration to that effect), a certificate of its bank confirming the IBAN and the Memorandum of Association. In addition, the fleet partner may store the operation card of the RTA, proof of insurance, the Tourism Expert certificate of its manager and further documents. We store the file, the document type, the issue and expiry dates, the review status and, where applicable, the reason for a rejection; replaced versions are kept as history. The Emirates ID and the passport relate to the owner in person, the Tourism Expert certificate to the manager in person, and the bank certificate contains the account details; we process them for the same purpose and with the same access and storage as the other company records. The other records concern the establishment and contain personal data, such as the name of an owner, manager or signatory, only insofar as it appears on the document itself; the Platform has no separate fields for such details. The fleet partner submits its records for review; they are reviewed and approved only by Emaride staff. When the fleet partner submits its records and when it is activated, Emaride's partner team receives an internal e-mail with the company name, the owner's e-mail address and, on activation, also name and phone number, and the list of records; the files themselves are not attached. Access is limited to the users of the fleet partner's account and to Emaride staff authorised for fleet partners in the UAE; the files are kept in non-public storage with our hosting provider (Section 5). Before a record expires, the fleet partner's owner receives a reminder. Where the Platform's document lock is switched on, the following applies: if a required company record expires, the fleet partner's drivers and vehicles are locked until a valid record has been verified; optional records never lead to a lock (Terms D2.4).

Electronic signature of the Fleet Partner Agreement. The owner of a fleet partner signs the Fleet Partner Agreement in the portal by entering the full name of the signing person and confirming the authority to sign, in a session confirmed with a second factor. We record the name as entered, the account and establishment, the version of the agreement and the checksum of its text, the date and time, the IP address and the device information, create a PDF copy of the signed agreement and store it unchanged together with its checksum. The copy is sent by e-mail to the owner and to Emaride's partner team. Access is limited to the owner of the fleet partner's account and to Emaride staff authorised for fleet partners in the UAE; the file is kept in non-public storage with our hosting provider (Section 5).

Driver records. Under C3.1 of the Terms of Use for the UAE and the requirements of the Transport Authority, the driver records that Emaride requires for the market at the relevant time and shows in the app are stored on the Platform for each driver, for example the UAE driving licence with its date of issue, the Emirates ID, the passport and the driver permit of the Transport Authority. In addition, the employing fleet partner may store the further records offered in the app, for example a medical fitness certificate, the proof of the training required by the Transport Authority, a certificate of good conduct and the employment contract with the fleet partner. Where they are stored, the medical fitness certificate contains health data, the certificate of good conduct data on criminal records; both are sensitive personal data under the PDPL. We use them only to verify that the driver meets the requirements of the Transport Authority and do not process them for any other purpose. From the date of issue of the driving licence we check whether the driver has held it for at least 2 years (Terms C3.1). We store the file, the document type, the issue and expiry dates, the review status and, where applicable, the reason for a rejection; replaced versions are kept as history. The records are uploaded by the driver or the employing fleet partner and reviewed by the employing fleet partner: records it uploads itself count as reviewed, a record uploaded by the driver remains pending until the fleet partner or Emaride approves it. In addition, Emaride staff authorised for drivers in the UAE may review the records and approve or reject them (Terms D2.4). Once all required records are valid, the driver is released automatically. Access is limited to the driver, the users of the employing fleet partner's account and Emaride staff authorised for drivers in the UAE, who access the records only insofar as necessary for support, supervision, this review and our legal obligations; the files are kept in non-public storage with our hosting provider (Section 5). Before a record expires, a reminder is sent; an expired required record locks app access automatically until a valid record is in place (Terms C3.2).

Vehicle records. For each vehicle, the vehicle records that Emaride requires for the market at the relevant time and shows in the app, and any vehicle records stored in addition, are stored on the Platform, for example the vehicle registration (Mulkiya) with its dates of issue and expiry and the insurance expiry date shown on it (Terms D2.4). We store the file, the document type, the issue and expiry dates, the review status and, where applicable, the reason for a rejection; replaced versions are kept as history. The records are uploaded and reviewed by the fleet partner; records it uploads itself count as reviewed. Drivers can submit photos of the vehicle assigned to them in the app; the fleet partner adopts or discards them. In addition, Emaride staff authorised for vehicles in the UAE may review the records and photos and approve, adopt, reject or discard them (Terms D2.4). Access is limited to the users of the fleet partner's account and Emaride staff authorised for vehicles in the UAE, who access the records only insofar as necessary for support, supervision, this review and our legal obligations; the files are kept in non-public storage with our hosting provider (Section 5). Before a record expires, a reminder is sent; an expired required record locks the vehicle automatically until a valid record is in place.

Proof of cleaning. Under D2.3 of the Terms of Use for the UAE, the driver submits once per calendar week a photo of the interior of the vehicle in the app; the fleet partner confirms it. We store the photo, the week, the status and who confirmed it when. If a confirmed proof is missing, the fleet partner's owner receives a reminder; the missing proof does not lock any account automatically.

Applications as a fleet partner. If you apply using the application form, we store the company name, the legal form, the country, the name, e-mail address and phone number of the contact person and your free-text description, together with the language of the form, the review status and, after the review, the decision, its reason and the reviewing person. As long as no Terms of Use for the UAE are in force, you apply without accepting them; you accept them when we invite you as a fleet partner. Once Terms of Use are in force, we additionally record which version you accepted, when, and from which IP address. To protect the form against mass submissions we count submissions per IP address; for this we store only a keyed code derived from the IP address, which is deleted after 2 days. We compare the e-mail address and phone number with our blocklist (Section 9); a match means that no application is created, and we inform you of this by e-mail without giving reasons. A match on the company or contact name does not stop the application but marks it for review by a person. A new application is notified to the responsible Emaride team by e-mail and in the dashboard and is reviewed by a person; there is no automated decision on an application.

Reports of content. If you report content using the report form on www.emaride.ae (also opened from the app), we process your name (optional), your e-mail address, the reported content or link, the reason, your description and your declaration of good faith. We use them to review the report, to confirm receipt and to send you our decision with reasons (protection of our legitimate interests and of other users). To protect the form against mass submissions we store only keyed codes derived from your IP address and your e-mail address, which are deleted after 2 days. Reports have no automatic deletion period; you can request deletion at privacy@emaride.ae.

Safety reports. If you report a safety concern about a ride in the app (for example harassment, an accident, dangerous driving or a vehicle that does not match the booked one), we process the type of report, your description, the ride, the persons and the vehicle concerned and how our safety team handles it (status, resolution). If the vehicle at pickup does not match the booked one, the app creates such a report automatically. We use the reports to alert our safety staff, to clarify the matter and to take follow-up measures towards the driver concerned; the number of reports about a driver is one factor in the review of drivers prepared automatically (Section 9) (protection of our legitimate interests and of other users). Safety reports are kept for the duration of the usage relationship; you can request deletion at privacy@emaride.ae.

Full payment card data is not stored by us but processed exclusively by the payment provider (Section 5).

We process personal data only for specified purposes and to the extent necessary:

Purpose Ground under the PDPL
Provision of the Platform, arranging and handling rides performance of a contract with you
Location processing to carry out the ride (pickup, routing) performance of a contract with you
Determining the departure terminal for a ride to an airport and re-checking it before a scheduled ride (entering a flight number is voluntary; you may choose an airline or terminal instead) performance of a contract with you
Pickup at an airport: determining the arrival terminal and landing time, moving the pickup time (landing plus 30 minutes) when the flight lands later or earlier, and detecting a cancelled or diverted flight so the booking can be cancelled free of charge (without a flight number you book an ordinary pickup) performance of a contract with you
Showing free vehicles near the pickup to booking passengers, gridded and without an identifier (Section 5) protection of our legitimate interests
Estimating the approach in the fare from the nearest free driver's last position, shown only as whole km (Section 5) performance of a contract with you
Payment processing, invoicing, retention of records contract; compliance with legal obligations
Verification of drivers and vehicles under the requirements of the Transport Authority (documents, age, driving experience, permits and, where stored, medical fitness and good conduct) compliance with legal and regulatory obligations; contract
Weekly proof of cleaning of the vehicle interior (Terms D2.3) performance of a contract; protection of our legitimate interests and of passengers
Storage and review of fleet partner records (Terms D2.4) compliance with legal and regulatory obligations; contract
Electronic signature of the Fleet Partner Agreement and proof of its conclusion performance of a contract; protection of our legitimate interests (proof)
Handling your application as a fleet partner steps taken at your request before entering into a contract
Spam limit and blocklist check of applications protection of our legitimate interests and of other users
Fraud prevention, abuse and penalty checks, safety protection of our legitimate interests and of other users
Support and communication performance of a contract with you
Ride chat between passenger and driver to coordinate the pickup performance of a contract with you
Transactional notifications (ride status, payments) performance of a contract with you
Measuring the website's loading times (Section 8) protection of our legitimate interests
Anything beyond the above (e.g. optional features) your consent, which you may withdraw at any time
Sign-in with Apple or Google and linking it to your account (optional) performance of a contract with you
Sign-in with a mobile number; sign-in codes, confirmation codes and driver invitations by SMS to UAE mobile numbers, limited to prevent abuse performance of a contract with you; protection of our legitimate interests

We do not send advertising or marketing messages and do not use advertising cookies on www.emaride.ae.

5. Recipients and Service Providers

  • Fleet partners and drivers — to carry out the booked ride. Before acceptance the driver receives your first name, the verification status and the pickup and destination address; after acceptance additionally your phone number and rating average. E-mail address, surname and card details are never transmitted. For rides to or from an airport they receive the terminal as part of the destination or pickup and, for a pickup, the pickup time, never your flight number.
  • Passengers — during a booked ride, the passenger sees the driver's first name, average rating with the number of ratings, the languages the driver has stated, the vehicle (category, make, model, colour, licence plate) and the driver's live position; once the driver has confirmed the ride and until it ends, additionally the driver's phone number. The driver's address, documents and bank details are never transmitted.
  • Passengers booking nearby — while a driver is online and not on a ride, a signed-in passenger booking within 5 km may see a vehicle symbol near the driver. The driver's last position is rounded to a grid of about 400 m; only one symbol appears per grid cell, at most 12 in total, only vehicles of the chosen class if the passenger has chosen one, and the number of free vehicles only roughly (1, 3 or 6 and more). No name, vehicle, licence plate, direction of travel or identifier is shown. A driver who goes offline disappears within 4 minutes at the latest. Where a long-pickup surcharge applies, the passenger also sees, before an immediate ride, the straight-line distance from the nearest free driver to the pickup, rounded up to whole kilometres, and the resulting amount in the price breakdown.
  • Authorities — where required by law, in particular the Roads and Transport Authority (RTA) of Dubai for regulatory reporting once the service is authorised. For each Trip this covers the times, pickup and destination, the vehicle plate, the Driver's permit number, the distance and the price lines including tolls and the RTA fee; for complaints the category, the Trip concerned and the status.
  • Service providers acting on our instructions:
Service Purpose Location
Supabase Hosting, database, storage, sign-in India (Mumbai)
Stripe Payment processing USA / Ireland
Google Maps Platform Maps, geocoding, routing USA
Infobip Delivery of sign-in codes, confirmation codes and driver invitations by SMS to UAE mobile numbers; receives only the mobile number and the message Croatia (EU)
Mapbox Map rendering (web) USA
Resend Transactional e-mail, ride OTP USA
OpenAI AI-assisted support triage; content without recognisable contact details and known names, kept for up to 30 days for abuse monitoring, not used for training USA
Expo Push notifications USA
Vercel Hosting of the website and web dashboard; loading time measurement (Speed Insights, Section 8) global (edge), USA
AeroDataBox (via the RapidAPI marketplace) Flight status (terminal, departure or landing time) for the flight number you entered; receives only the flight number and date, no name or contact details Canada; marketplace USA
Apple Sign-in with an Apple account (optional); Apple processes it as an independent controller USA
Google Sign-in with a Google account (optional); Google processes it as an independent controller USA

Signing in with Apple or Google. Instead of a password or passkey, you can sign in with an Apple or Google account and link such an account to your Emaride account in the app's security settings, or unlink it again; one account can be linked per provider. This is voluntary. If you choose this option, we receive a signed confirmation from the provider containing an identifier of your Apple or Google account, your e-mail address (with Apple, a relay address if you wish) and, if you share it, your name. We use the confirmed e-mail address to match the sign-in to your existing account. Through this route we only create a new account as a passenger account in the app, after you have confirmed your country and the Terms of Use. We store the identifier and e-mail address of the link for as long as the link exists; if you unlink it or delete your account, we remove them. If you have set up two-factor sign-in, we also ask for the code after this sign-in. This processing is necessary for the performance of the contract with you. Apple and Google process the sign-in as independent controllers under their own privacy policies, also in the USA, and learn in the process that you are signing in to Emaride.

Sign-in with a mobile number and messages by SMS. In the UAE you can register and sign in with your mobile number (+971) instead of an e-mail address; your mobile number is then your sign-in identifier. We send SMS only to mobile numbers in the UAE: a one-time code to sign in and to confirm a number you add to your account, and an invitation when a partner (Ride Service Partner) or Emaride invites you as a driver. For an invitation without an e-mail address the partner provides your name and mobile number; we create your account with this number and send you the invitation by SMS on behalf of the partner, and you activate your account by signing in with the code. If you register with your mobile number, we record your acceptance of the terms only after your first sign-in, when it is clear that the number belongs to you. If nobody signs in with the number within 24 hours, the registration lapses and we delete it as soon as the number is registered again. If you lose your number, our staff can set a new sign-in number for your account; we record this without the full number. Without an e-mail address we inform you in the app and by push notification instead of by e-mail; to book outside the UAE you need an account with an e-mail address. For delivery we pass your mobile number and the text of the message to Infobip (see the table above). To prevent abuse, we send at most five codes per number and hour and at most 500 invitations per partner and day; for the code limit we store only a keyed code derived from the number, not the number itself, for up to 2 days. The code is valid only for a short time. This processing is necessary for the performance of the contract with you and, for invitations, with the partner, and protects our legitimate interest in preventing abuse.

Avoiding duplicate accounts across regions. When you register, request a password reset or are invited, we check whether an account with your e-mail address already exists in our European database. For these three operations only a pseudonymous code derived from your e-mail address (a keyed hash) is transmitted; your address itself does not leave the region. If an account exists there, we inform you by e-mail how to sign in. This does not apply to signing in, see the next paragraph.

Signing in across regions. When you sign in with your e-mail address and password, we do not always know in advance in which region your account is held (for example on a new device or while travelling). If sign-in fails in the region asked first, we transmit your e-mail address and password in encrypted form (TLS) to the sign-in service of the other region (our European database, Supabase, Frankfurt data centre, or our UAE database in Mumbai, India). Unlike the check above, these are the credentials themselves, not a pseudonymous code. The sign-in service there uses them only to check the sign-in and does not store the password. Every failed attempt is recorded to protect against attacks in the region where it fails, even if sign-in then succeeds in the other region: in the protective log against repeated failed attempts, with a hash of your identifier and the IP address (deleted after 15 minutes), and in the audit log (retention as for log data, Section 7). The purpose is to let you sign in with one account in every region.

Check against known passwords. When you register, we check whether your password appears in known data breaches and reject it if so. For this we send only the first five characters of a SHA-1 hash of your password to the "Pwned Passwords" service of Have I Been Pwned; neither your password nor your e-mail address is transmitted, and the service cannot infer you or your password from these five characters.

6. Cross-Border Transfers

Our database for the UAE market is operated in India (Mumbai); further service providers are located in the USA, Canada and the EU (Section 5). Transfers outside the UAE take place only under the conditions of Articles 22 and 23 PDPL, in particular on the basis of contractual safeguards with the respective provider or where the transfer is necessary for the performance of the contract with you.

7. Retention Periods

Data Period
Account and profile data for the duration of the usage relationship; deletion on request
Driver records, incl. replaced versions for the duration of app access; deleted with the file 24 months after the driver account is closed
Photos proving cleaning 12 months from the week concerned
Fleet partner records, incl. replaced versions for the duration of the contractual relationship; deletion on request
Signature record and signed copy of the Fleet Partner Agreement for the duration of the contractual relationship and 5 years after it ends (proof of the contract), also if the signing person's account is closed
Vehicle records, incl. replaced versions for the duration of the contractual relationship with the fleet partner; deletion on request
Applications, incl. rejected applications no automatic period; deletion on request (privacy@emaride.ae)
Keyed IP code of the application form 2 days
Logged attempts of blocked persons 24 months
GPS coordinates of a ride, incl. stop 24 months, then irreversibly removed
Pickup, destination and stop address of a ride 10 years (description of the invoiced service)
Recurring booking (weekdays, pickup time, route) until the series ends, then 90 days
Invoice and transaction data 10 years (commercial and tax retention)
Support tickets and chat content 24 months after the matter is closed
Ride chat messages 24 months after sending
OTP code for ride verification deleted after verification (at the latest after 1 day)
Flight data (flight number, travel date) 7 days after the date of the flight
Notifications (push/in-app) 90 days
Log data 24 months
Link to Apple or Google (identifier, e-mail address) until unlinked or the account is deleted
SMS code for sign-in or confirmation until it is used or expires
Keyed code of the mobile number (SMS limit) 2 days

8. Cookies

On www.emaride.ae we only use strictly necessary cookies: emaride_lang (display language, 1 year), emaride_country (market, 1 year), the session cookie of our sign-in (sb-…-auth-token, until you sign out or the session expires), emaride_remember (your "stay signed in" choice) and emaride_region (the region in which your account is kept, so that we connect you to the right database; 1 year). We do not use tracking or advertising cookies.

Loading time measurement. On all pages of www.emaride.ae, including the logged-in web area, we use Vercel Speed Insights to measure how fast the pages load and respond to input. After a page is opened, your browser sends to Vercel Inc. (USA) the page pattern without identifiers, parameters or fragment, the measured values (loading time, response time, layout shift), device type, browser, operating system, connection speed and the time; Vercel derives the country from your IP address. No cookies are set and no identifiers are stored on your device that would recognise you; your name, account or rides are not transmitted. The measurement runs without a consent dialog, based on our legitimate interest in a fast and stable website. No such measurement takes place in the app.

9. Automated Decisions

The penalty check for cancellations and no-shows, the automatic suspension when mandatory documents expire, the blocklist and the review of drivers based on cancellations, no-shows and safety reports are prepared automatically. Measures with a significant effect on you — in particular the restriction or suspension of your account — are reviewed by a person at Emaride. You may object to a decision based solely on automated processing and request a human review via privacy@emaride.ae.

10. Your Rights

Under the PDPL you have the right to:

  • obtain information about the processing of your data and a copy of it,
  • request the transfer of your data,
  • request correction of inaccurate data and erasure of data no longer required,
  • request restriction of processing,
  • request that processing stops, and
  • object to decisions based solely on automated processing.

You can trigger a data export and the deletion of your account directly in the app. For everything else, contact privacy@emaride.ae. We respond within the periods set by law.

11. Complaints

You may lodge a complaint with the UAE Data Office if you believe that the processing of your personal data violates the PDPL.

12. Data Security

We use appropriate technical and organisational measures (including encryption in transit, role- and country-based access controls and separate storage of UAE and EU data) to protect your data.

13. Changes and Status of This Version

We update this policy when the processing changes. The current version is available on the website and in the app; it carries a version number and an effective date.