Reading the website before making contact
You can read the service descriptions and Dubai area guides without completing an enquiry form. The pages explain the driver service model, practical pickup details and the questions useful when organising a journey. You do not need to provide your name, telephone number or vehicle information merely to browse that content. If you decide to contact the business later, the enquiry information comes from the details you choose to enter or send, rather than being inferred from a page you happened to read.
As with any hosted website, a connection to the hosting provider is needed to deliver the page and its assets to your device. Standard technical information may be processed for that delivery and for the provider’s operation of its service. This notice does not claim that there are no network connections or that the website controls every hosting record. It distinguishes those technical connections from the journey details requested in the booking form, which are prepared in the browser rather than written to a website enquiry database.
The current public-facing application does not require a customer account to prepare an enquiry. An owner-private preview may instead use the hosting platform’s own access controls before a visitor can view it. That platform authentication is separate from the personal-driver form. If you are looking at a private preview, questions about its sign-in behaviour should be considered alongside the host’s information. The booking interface itself does not ask you to create a driver-service account or enter a password.
Understanding the information requested by the form
The form asks for your name and contact number so the business can understand who is enquiring and how to respond. It also asks for the service, pickup, destination, journey date, Dubai pickup time and vehicle details. These fields describe the practical request. The optional notes field is available for relevant extra stops, waiting requirements or access instructions. The purpose is to prepare an understandable itinerary, rather than gather unrelated background information about the customer.
Consider each field in relation to the journey. A car make and model helps explain the proposed vehicle; a pickup address helps identify where the driver would need to meet you. Neither field is a reason to include a vehicle-registration scan, a copy of an identity document or a detailed history of your travel. If a specific arrangement later requires further information, discuss that request directly with the business and ask why it is needed before supplying it. The website does not ask for those documents as part of the standard form.
Use the notes field with the same care you would use in a message to a business. Provide enough information to discuss the journey, but leave out material that has no practical role in the request. For example, an appointment address and approximate duration may explain the itinerary without disclosing private details about the appointment itself. A clearer request often contains less personal information than a long forwarded conversation, because the logistics can be described directly instead of embedded among unrelated messages.
What happens while a message is being prepared
The current enquiry form combines the information you enter into a text message in your browser. Its validation checks whether required fields have been completed, whether the date is today or later and whether the contact number contains a plausible number of digits. These checks help prepare a usable message. They do not establish the identity of the person entering the details, determine whether a vehicle may be driven or create a confirmed booking in a back-office system.
The website does not upload the completed enquiry to an application database when you prepare the message. It creates a WhatsApp link containing the enquiry text and provides a visible option to open that link again. This design means that preparing the message and sending it are distinct actions. A visitor can review the details before choosing to send them through WhatsApp. The website does not report that an enquiry has been delivered simply because a link was opened or a message was prepared.
The information may remain visible in the form while the page stays open. The current application does not intentionally save the completed form in browser storage for a future visit. Your browser may offer its own autofill or session features, and those are controlled by the browser and your device settings. If you use a shared device, check what remains on screen when you finish. The distinction matters: application behaviour can be described here, while browser-level storage or autofill depends on the software you use.
Choosing to continue through WhatsApp
When you prepare the enquiry, the website opens a link to the supplied business WhatsApp number with your message attached. WhatsApp then handles its own interface and connection. Review the recipient and the message in that application, and press Send only when you want to start the conversation. The website does not control whether WhatsApp is installed, whether you are signed in or whether the external application completes the action. If the window does not open, the page provides a link you can use again.
The message text is included in the link used to hand the enquiry to WhatsApp. Avoid forwarding that link casually if it contains information you do not want another person to see. The link can include the same name, number and itinerary you entered in the form. Treat it as a prepared communication, rather than a generic web address with no personal content. If you want to share the website without sharing an enquiry, use the ordinary homepage or service-page address instead.
Once you send the message, WhatsApp processes the conversation under its own service terms and privacy information. The business can receive the information and use it to answer the enquiry or discuss a proposed journey. This website notice describes the handoff and the current application; it does not replace WhatsApp’s explanation of its service. Questions about a sent message should be directed to the business conversation, while questions about the messaging platform’s processing should be considered using the platform’s own information.
Using the copy-message option
The enquiry result includes an option to copy the prepared text. When your browser permits it, that button writes the message to the device clipboard so you can paste it into the intended conversation. Copying is an alternative way to move the enquiry text; it does not send the message or reserve a driver. The application displays whether the copy action succeeded, and you remain responsible for choosing the destination where the copied text will be pasted.
A clipboard is a device feature rather than an enquiry archive controlled by this website. Other applications or device features may interact with it according to their own settings and permissions. On a shared device, consider replacing sensitive clipboard content after using it and check where you paste the enquiry. The website cannot supervise every application that might use the clipboard later. The practical point is to treat copied text with the same care as the original details entered in the form.
If the browser does not allow clipboard access, the page explains that the copy operation is unavailable and directs you to the WhatsApp option. That failure does not mean the enquiry has been sent another way. Review the visible result and choose an available contact method. An ordinary telephone call or a direct WhatsApp message can still start the discussion without requiring the clipboard feature. Using the simplest workable method is usually clearer than assuming that a blocked copy action has completed a different communication step.
Location and service selections in page addresses
The compact homepage form can carry the selected service, pickup area and date to the contact page. Those selections appear as query parameters in the contact-page address so the longer form can be prefilled. Similarly, a service or location link can open the contact page with the relevant selection already supplied. This reduces the need to enter the same basic information twice, but it also means those particular selections may be visible in the page URL.
A page address can appear in browser history, bookmarks or a link you copy to another person. Use the prefill fields for ordinary service and location information rather than confidential access codes or detailed personal notes. The full form has separate fields for the rest of the enquiry, and those are not used to create the contact-page prefill address. If you want to share a clean contact link, remove the query parameters or use the standard contact-page address from the navigation.
The application uses recognised service values and normal form-field values when reading the query parameters. Prefilling a location does not confirm that the business serves every address in that area at every time. It simply describes the starting point of your request. You can change the supplied values before preparing the final message. Review the fields even when you reached them from a relevant area page, because an approximate neighbourhood name may still need a more precise building, gate or parked-car description.
External calling and map links
Telephone links ask your device to use an available calling application with the supplied business number. The website does not record the conversation or determine what your telephone provider processes. You decide whether to place the call using the application shown on your device. A visible phone link is a contact option; it is not a promise about call availability, response time or the terms of a later booking. Discuss the practical request directly when the call connects.
Location pages also offer a link to explore the named area in Google Maps. Opening it moves you to a separate service with its own information and controls. The website does not request your device’s live location to create that link; it uses the named Dubai area as a search description. If a maps application asks for location permission, that request belongs to the maps service or your device. You can consider its permissions independently from the enquiry form.
The same principle applies to any external service you choose to use after following a link. Review the recipient, destination and relevant privacy information when information moves outside this website. A link is provided because it can help contact the business or understand an area, but it does not make the external provider part of the website’s own application storage. Keeping those boundaries clear helps explain which service is responsible for the interface and information you are seeing at each stage.
Cookies, analytics and locally hosted assets
The current application does not install advertising analytics or intentionally set application tracking cookies. It does not contain a customer profiling system or a marketing account login. Its fonts and main illustrative imagery are hosted with the site, so displaying those assets does not require a separate remote-font request from your browser. This description concerns the application version provided here. If additional tools are introduced later, the notice should be updated to explain their actual behaviour.
The hosting platform can still have its own technical or authentication behaviour, especially for an owner-private preview. A statement that the application has no advertising analytics should not be read as a statement that every hosting or browser feature is disabled. Likewise, your browser extensions, security software or network provider operate outside the website’s control. This notice separates what the site’s own code does from features implemented by the environment through which you access it.
If you want to examine browser-level settings, use your browser’s own privacy controls and help information. Clearing cookies or history can affect several services and is a choice made on your device. The personal-driver website does not require you to enable an advertising profile before reading its guides or preparing an enquiry. Its practical functions are the page content, navigation, location search and a form that prepares a message you choose to send. Those functions do not depend on an advertising analytics integration.
Enquiring for another passenger
A family member, assistant or colleague may organise a journey for someone else. In that case, distinguish the coordinator from the passenger and obtain the person’s agreement before sharing their contact details or private plans. You can often describe the journey using a meeting address, date and time without forwarding the passenger’s entire calendar. Include a contact who is authorised to discuss the practical arrangement, and explain who will be present when the driver meets the vehicle.
The form does not verify that a visitor has permission to act for another person. The person making the enquiry should therefore consider what they are authorised to share and what the passenger actually needs to know. If the passenger will receive updates directly, make that arrangement clear in the conversation. If the coordinator will handle the messages instead, ensure the passenger still understands the meeting point and itinerary. Clarity about roles is useful both for practical planning and for avoiding unnecessary disclosure.
For business travel, separate company logistics from confidential meeting material. A named office and appointment time may be sufficient to explain the stop; internal agendas, client documents or employee records are usually unrelated to the driving enquiry. Ask the relevant person before supplying another individual’s details. The website offers a convenient way to compose a request, but the coordinator remains responsible for deciding which information belongs in that request and which should stay in the original business or personal conversation.
Information after the business receives a message
After you send an enquiry, the business may use the information to answer questions, clarify an itinerary, discuss availability and propose a driver arrangement. If you agree a booking, the relevant details can also be used to coordinate that journey. The website itself does not provide a customer portal that displays every record held by the business. A conversation sent through WhatsApp and a message prepared only in the browser are different situations, and the latter does not establish that the business has received the former.
This notice does not invent a retention period or describe internal systems that have not been verified. If you need to know how a particular conversation or confirmed-booking record is handled, contact the business directly and identify the relevant enquiry. Ask for the operational information that matters to your situation, such as whether a corrected address has replaced an older one or how to request removal of information no longer needed. A clear question about a specific record is more useful than assuming every copy is managed by this website.
Keep your own copy of the information you agree for the journey. That can help you identify the conversation if a correction or privacy question arises later. At the same time, avoid sending extra documents solely to prove which enquiry you mean when an ordinary date and contact reference will suffice. The business may need appropriate information to understand a request, but you can ask what is necessary before providing it. Direct communication is the available route for questions about business-held records.
Corrections and privacy questions
If the prepared message contains an incorrect detail and has not been sent, correct the form and prepare it again. If you already sent the enquiry, contact the business in the relevant conversation and explain the corrected information. Identify what changes and what remains the same so the itinerary can be understood clearly. Changing a field on the website after sending a message does not edit the copy that the recipient has already received through WhatsApp.
For a privacy question, use the published business call or WhatsApp contact. Explain the nature of the question and enough context to identify the relevant enquiry, without adding unnecessary sensitive information. A request might concern a mistaken telephone number, an address supplied for another person or information associated with an old journey discussion. This notice explains the available contact route; it does not claim that the form independently carries out a deletion or applies a correction in external messaging systems.
Different services can hold different parts of a communication. The business conversation, your own device and the messaging provider are not a single website database. If your question concerns an external service’s handling of information, consult that provider’s controls and information as well. If it concerns the business’s use of a received enquiry, ask the business directly. Understanding which service or person holds the relevant information helps you address the question to the appropriate place rather than expecting one browser action to update every copy.
Practical care on a shared device
On a shared computer or phone, review what is visible before you leave the device. The form may still show the information entered during the current session, and an opened WhatsApp window may display the prepared message or an existing conversation. Close the pages or applications you no longer need and follow the device’s normal sign-out procedures where relevant. The website does not provide a shared-device management system, so those choices remain part of using the browser and external applications responsibly.
Consider browser history and autofill when deciding which device to use for an enquiry. The contact-page prefill address can contain an area, service or date, while browser features may remember other information according to your settings. This behaviour is not the same as the site intentionally storing a completed form in a database. If you are unsure how a public or borrowed device is configured, a direct call or a message from your own device may be a simpler contact option.
Review the recipient before pasting copied enquiry text into another application. A message intended for the business can contain a pickup address and contact number, so it deserves more care than a general link to the homepage. If you accidentally paste it into the wrong place, use the relevant application’s available controls and contact the appropriate recipient when necessary. The website cannot retrieve information from another application after it has been pasted or sent. The best practical safeguard is to check the destination before completing the communication.
Understanding the scope of this notice
This guide describes the current website and its enquiry flow. It explains the difference between reading a page, preparing a message, opening an external service and sending a communication to the business. It does not promise that every future version will behave identically. If the site later adds a database, online payment, analytics, customer accounts or another integration, the relevant notice should explain those changes using verified information about the actual implementation.
The current form does not take payment, issue an invoice, reserve a driver or collect card details. Do not interpret the contact interface as a checkout process or a secure-document upload service. If a later conversation introduces another method of payment or information sharing, review that method separately and discuss any questions with the business before using it. A simple enquiry form and a later operational process can have different information requirements, and this website should not be read as silently confirming the terms of a process it does not implement.
For the present enquiry flow, the practical choices remain straightforward. Read the relevant service or area guide, enter only the journey details needed to start the conversation, review the prepared message and choose whether to send it. Contact the business directly for questions about received information or a confirmed arrangement. That sequence gives you a clearer view of what you have shared, which service received it and whether the conversation has progressed from an enquiry to an agreed journey.