Cookie Policy
Last updated:
This page explains how partyyachtrentaldubai.com uses browser storage and similar technologies when you visit, enquire about a charter, or tap a WhatsApp button. It is written for anyone browsing the site and applies alongside our Privacy Policy.
Storage used on this site
- Cookie notice marker (local storage)
- Remembers that you closed the cookie notice so it is not shown again. Local storage, kept until you clear your browser storage.
- Selected yacht (session storage)
- Remembers which yacht you clicked so the enquiry form can be prefilled. Session storage, deleted when the tab is closed or the form is sent.
- Visit identifiers (local storage)
- Random visitor and session identifiers used only for our own visit count. Local storage, expires 30 days after your last visit, can be cleared at any time.
- Google Fonts
- Loads the web font files used on the page; Google receives your IP address as part of this request. No cookie is set on our behalf.
- jsDelivr (intl-tel-input)
- Loads the phone-number input library used in the enquiry form; jsDelivr receives your IP address as part of this request. No cookie is set on our behalf.
1. Cookies and similar technologies
A cookie is a small file a website can ask your browser to keep so the site recognises you later. Local storage and session storage work the same way but sit in different parts of the browser and are not sent automatically with every request. We use the term "storage" below to cover all three.
2. No cookies, no outside trackers
partyyachtrentaldubai.com does not set any cookies of its own, and we have not installed any outside analytics, advertising or social-media tracking tool. There is no pixel, ad network or cross-site tracker running on this site.
We do count visits using a small script that runs on our own domain and talks only to our own server. It records which pages were opened, how long a page stayed open, the site that referred you, any campaign tag in the link (such as a UTM or ad click id), device type, browser, operating system, screen size, browser language, and the country worked out from your IP address; the IP address itself is not kept. If you send an enquiry or tap a WhatsApp or phone link, that action is linked to the same visit so we know which channel brought the booking request. This measurement relies on two identifiers held in local storage, described below, that expire automatically after 30 days of inactivity.
3. What is stored in your browser
Three entries are placed in your browser, none of which contains your name, email or phone number:
- a local-storage flag that stops the cookie notice reappearing once you have dismissed it;
- a session-storage entry holding the yacht you clicked on, so the enquiry form opens pre-filled; it disappears when you close the tab or submit the form;
- a local-storage entry with randomly generated visitor and session identifiers used only for the visit count described above; it expires 30 days after your last visit and can be removed by you at any time.
Full details of each entry are listed in the table above.
4. Third-party requests when the page loads
Two outside services are called when a page loads, each receiving the visitor's IP address as a normal part of that network request:
- Google Fonts, to display the typefaces used on the site;
- jsDelivr, to load the intl-tel-input library used for the phone-number field in our enquiry forms.
Neither of these calls places a cookie for our benefit, and we receive no data back from them beyond the font or script files themselves.
5. WhatsApp buttons and managing storage
A WhatsApp button on this site does nothing to your browser until you click it. The click itself is logged in our booking system (page, referrer, language and the prefilled message) so we can match the chat to the right enquiry, and only then does WhatsApp open in its own app or tab; from that point the conversation runs on WhatsApp under Meta's own policy, not ours.
You can review, block or delete local storage and session storage through your browser's settings, usually under privacy or site data; doing so removes the cookie-notice flag, the selected-yacht entry and the visit identifiers described above. Blocking them will not stop you from browsing or sending an enquiry, though the cookie notice may reappear and the yacht field may not pre-fill.
6. Changes to this page and future cookies
If we ever introduce an optional cookie, for example for a new booking or payment tool, we will ask for your consent first through a clear choice on the site before that cookie is set, consistent with the transparency expected for device storage under the UAE Personal Data Protection Law. We may update this page to reflect such changes; the current version always applies to your visit.
Questions about this policy, or requests to exercise your rights over any linked personal data, can be sent to [email protected]; we reply within one month and may ask you to confirm your identity first. Complaints about how device storage or personal data are handled may also be raised with the UAE Data Office.
Party Yacht Rental Dubai · Dubai · [email protected]