01The purpose of this privacy explanation
This guide explains the information flow in the Private Driver Dubai City website. Its purpose is to help you understand what happens when you browse a page, complete the enquiry form, review a request or choose to contact the business. Those are different actions, and they do not all share the same information with the same recipient. A clear understanding of each stage helps you decide which details to enter and when you actually want to communicate them to the team.
The explanation describes the website application and its current enquiry design. It should not be read as a description of every practice used by your browser, device, internet provider, hosting platform or WhatsApp. Those services operate separately and may process information under their own arrangements. If your question concerns a message already received by the business, contact the team directly and identify the relevant conversation. If it concerns another provider, consult that provider’s information as well as the website explanation here.
02Browsing information pages without making an enquiry
You can read the homepage, service descriptions and Dubai area guides without completing the booking form. Reading a location page does not automatically create an enquiry for that area, reserve a driver or tell the business that you intend to travel there. The directory is an information and navigation tool. Its location names and pickup notes are published website content, not personal details supplied by a visitor. Selecting a service or area link simply takes you to the related page.
As with other hosted websites, delivering a page involves network connections between your device and the services that provide the site. The hosting provider may handle ordinary connection information and security-related records. The website application itself does not add advertising trackers or an analytics system to follow your browsing. These statements concern the application’s design; they do not promise that the underlying network or hosting provider creates no technical records. Check the applicable provider information if you need details about that separate processing.
03What the enquiry form asks you to enter
The form asks for a name, contact number, service, expected duration, pickup location, destination, date and Dubai pickup time. There is also an optional notes field. These fields are intended to describe a driving enquiry for your own vehicle. They help the team understand the person to contact, the proposed journey and the schedule being discussed. You do not need to include a detailed personal history to explain that you would like a driver for a particular appointment or return journey.
The form does not request payment card details, account passwords, a copy of your identity document or a medical record. Please do not put those items in the notes field. When a practical need matters, use the minimum useful description, such as allowing additional time at the entrance or needing to collect keys from a valet. If you are unsure whether a detail is needed, leave it out of the initial draft and ask the team about the requirement before choosing to share more information.
04What happens while you prepare a request
The enquiry interface uses the information entered in your browser to prepare a message. The website application does not submit that form to a website booking database. Reviewing a request therefore does not itself create a dispatch record or an automatic booking notification for the business. This is an important distinction when you are testing a possible itinerary, correcting a spelling mistake or deciding which service to ask about. The preparation stage exists to let you inspect the proposed message before sending it.
The application does not save enquiry details to localStorage or create a customer account from the form. Your browser or device may nevertheless have its own form recovery, autofill or history features. Those features are controlled outside this website application, and this guide does not promise that closing a tab removes information from every device or service. On a shared device, consider the browser’s own settings and avoid leaving a completed form available to another person. Use the review step deliberately before moving to an external service.
05Why validation happens before review
Form validation checks whether essential fields are present and whether certain values have a usable format. It also checks the requested pickup against Dubai time so an already-passed date or time is not presented as an ordinary future request. Validation errors appear beside the relevant field and in a linked error summary. These checks help you prepare a clearer enquiry. They do not verify your identity, confirm the ownership of a phone number or establish that a pickup address is genuine.
Correcting an error changes the information used in the draft. If you entered an incorrect contact number, replace it before reviewing the message. If your intended time is provisional, explain that in the notes instead of assuming the validation system will communicate uncertainty for you. Validation is a local assistance feature, not a driver availability check and not a background verification process. The team still needs to discuss the actual arrangements after you choose to send an enquiry through the contact channel.
06The review screen and your choice to continue
The review screen displays the enquiry message in readable text. It includes the contact information and trip details you entered, together with a statement that availability and price need confirmation. Read that message as though you were about to send it yourself. Look for information you would prefer to remove, an address that is more precise than necessary for the first discussion or a detail that identifies someone who has not agreed to be mentioned. You can return to the form to edit the draft.
The screen clearly distinguishes preparation from sending. A prepared request has not yet been delivered to the business through WhatsApp. You can stop at this stage, edit the details or continue using the provided link. The website does not interpret viewing the draft as a confirmed booking or an instruction to contact another person. If you decide to continue, the next stage involves a separate service. That transition is why the consent wording refers specifically to sharing the details through WhatsApp rather than making a broad statement about unrelated uses.
07Opening WhatsApp with a prepared message
The Send via WhatsApp link includes an encoded version of the prepared message. Opening it passes that draft into the WhatsApp link flow, which may open an application or a browser page depending on your device. This step involves WhatsApp as a separate provider. Do not assume that a draft passed into an external service remains confined to this website simply because you have not yet pressed the final send button in that application. Review the details before selecting the link.
You then decide whether to send the message in WhatsApp. If you do send it, the business receives the message through that service and can respond to the enquiry. WhatsApp’s handling of links, messages, account information, device activity and related records is governed by its own practices. Consult its privacy information if you need an explanation of those matters. The website cannot delete records from another provider merely because you later close the original form or return to a different website page.
08The business conversation after a message is sent
When you send an enquiry to the business, the information becomes part of a direct conversation with the team. The stated purpose of that conversation is to discuss your request, ask relevant follow-up questions and agree any driving arrangement you choose to confirm. The website does not publish a separate automatic customer database or an email campaign signup as part of this process. A message about a proposed journey should be understood as communication for that enquiry, rather than evidence that a driver has already been assigned.
If you want to understand how the business handles a conversation after receipt, ask the team directly. It can explain what records it holds, who needs the information for the arrangement and what can be corrected or removed. This guide does not invent a retention period, a guaranteed deletion deadline or a list of internal systems that has not been supplied. The distinction keeps the published explanation tied to known website behavior while leaving business-specific record questions to the people who actually manage those records.
09Pickup addresses, map pins and access details
A pickup can sometimes be described with an area and building name before a more exact meeting point is needed. Share the level of detail appropriate to the stage of the enquiry. A map pin, parking floor or gate name can be helpful when confirming a real pickup, but an initial discussion does not normally require a private door password or unrestricted access credential. If a venue controls entry, ask the appropriate person how a visitor should be admitted rather than treating sensitive access information as ordinary notes.
Consider whether an address belongs to you, another person or a business facility. If you are arranging a visit on someone else’s behalf, check that the information is suitable to share for the intended journey. A precise location can reveal more than a neighbourhood name, particularly when connected to a date and time. You can begin with a general enquiry and provide the operational meeting details once you understand what is needed. The aim is a workable pickup description without unnecessary disclosure.
10Passenger information and requests made for others
If another person will meet the driver, explain the coordination clearly without adding unrelated personal information. The team may need to know which contact is arranging the journey and which person will be present with the car. A simple description of that role can be enough to begin. Do not automatically include another person’s private contact number, identity document or sensitive circumstances because you are the person completing the website form. Decide what is necessary for the actual task and discuss uncertainty before sharing.
The same principle applies to family arrangements, visitors, colleagues and business guests. Practical requirements can often be described without naming a diagnosis, providing an account credential or sending a document. If a passenger needs a particular form of assistance, state the assistance you want to discuss and ask whether it can be accommodated. This website is not a medical information system or an identity collection portal. Its form is designed to prepare an ordinary driving enquiry, and the information you include should match that limited purpose.
11Phone calls and ordinary contact links
The website includes phone links as another way to contact the team. Selecting a telephone link asks your device to open its available calling interface; it does not send the completed enquiry form as a hidden attachment. If you make the call, the information you discuss is part of that separate conversation. Your phone provider and calling application may process connection information according to their own arrangements. The website application does not describe or control every record associated with the call.
A direct WhatsApp contact link can also open a short general enquiry without using the detailed form. Check the message that is prepared and decide what to add before sending it. The existence of several contact links does not mean that all channels receive the same information automatically. A form review, a telephone call and a sent WhatsApp message are separate actions. Choose the channel that suits your enquiry and keep any later corrections clear so the team understands which details are current.
12Fonts, images and application storage
The website’s fonts and published images are served as local website assets. They are not used as personalised customer records, and viewing an illustrative photograph does not require you to supply your own image or upload a file. The application does not include an advertising cookie banner because it does not add an advertising or analytics tracking system. It also does not create a browser-stored customer profile from the enquiry fields. These are descriptions of the current implementation rather than statements about every service involved in hosting the site.
Hosting security, account access and browser behavior can remain separate from those application features. A private review deployment, for example, may require platform sign-in even though the public-facing enquiry form does not create a customer account. Refer to the hosting platform’s information for that authentication process. If the website later adds a materially different feature, such as a server booking system or an analytics service, the published explanation should be reviewed against that actual change. Do not assume a future feature is covered simply because this page is long or detailed.
13Corrections and questions about information already shared
If a sent enquiry contains a mistake, contact the team and identify the relevant conversation. State the incorrect item and the replacement clearly: for example, the old pickup date and the new date, or the contact number that should be used going forward. Avoid resending an entire collection of personal details when a focused correction will explain the issue. If the correction affects a confirmed arrangement, ask the team to confirm the updated plan rather than assuming the first message has been silently replaced everywhere.
You can also ask the business about correction or deletion of enquiry information it holds. The team can explain what records are involved and whether any information needs to remain for an agreed arrangement or another applicable reason. This website guide does not promise a specific outcome or deadline without knowing the circumstances. A request to the business is different from removing a record in your own browser or WhatsApp account. Be clear about which recipient and which information your question concerns so it can be directed to the appropriate place.
14Using the form on a shared or borrowed device
On a shared device, consider who can see the screen, access the browser or open the messaging application. A draft visible in a tab can be read by someone with access to that tab even though the website has not submitted it to a booking database. Browser autofill, session restoration and device notifications are separate features that may affect what remains visible. Use your own judgment about the device and review its settings if you are concerned about information being available to another user.
Before leaving a shared device, make sure you understand whether you have opened an external messaging account or calling interface. Closing the original website page does not necessarily close those separate applications. Do not enter passwords or payment information in the website notes as a way of passing them to the team. If you want to begin with less detail, use a short general enquiry and continue through an appropriate personal contact channel. The form is a convenience for preparing a message, not a secure document exchange facility.
15Changes to the website and this explanation
The date on the privacy page identifies the published version of this explanation. Website behavior should be assessed against the version and features actually in use. If a new enquiry channel, upload feature or automatic booking system is introduced later, its information flow may differ from the process described here. A longer privacy page is not a substitute for checking those changes. The useful standard is whether the explanation accurately describes what the visitor is asked to do and where the information goes.
You can revisit the page before making a new enquiry if you want to review the current description. For a question about a particular message or arrangement, refer to the direct conversation with the business as well. This page does not create an automatic notification subscription, and it does not claim that every reader will be individually contacted when wording changes. If you need clarification before sharing a detail, ask first. A clear question at the beginning is often more useful than trying to resolve uncertainty after information has already been passed to another service.
16A final review before you choose to share
Before moving from the website to a contact channel, read the prepared request once more. Confirm that it contains the correct number, the intended trip and only the notes needed for the conversation. Check whether it mentions another person, a private address or an access instruction that deserves extra thought. Remove information that does not help the team understand the driving task. You can always ask a focused question first and provide operational detail later once you know why it is needed.
Remember the sequence: browsing published information, preparing a local draft, opening an external contact service, sending a message and confirming a booking are different stages. Understanding that sequence helps you stay in control of the enquiry. The website gives you a review step and clear contact options; it does not make the sharing decision for you. If anything remains unclear, contact Private Driver Dubai City on the published business number and ask about the specific information flow before proceeding with the detail you are uncertain about.
Ready to discuss your plans?
Choose the next step that fits your enquiry. Our team confirms availability, the quote and the driving arrangement directly.