Privacy policy
Last updated: 2026-10-24
BookMySafari.ae is a Dubai desert safari booking platform operated by BookMySafari (the "platform"). Bookings on this site are fulfilled by Velari Tourism L.L.C, the named Dubai DET-licensed partner operator (DET license #1491675). This policy explains what personal data the platform collects, why, for how long, where it goes, and how a data subject can access, correct, or erase it.
The policy is written against UAE Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data ("UAE PDPL"), UAE Federal Law No. 15 of 2020 on Consumer Protection, and Cabinet Decision No. 66 of 2023 on the Implementing Regulations of the Consumer Protection Law.
1. Data we collect
The platform collects only the personal data needed to answer a booking request and confirm a booking:
- Booking enquiry data: full name, WhatsApp or phone number, email address, how you want the reply (WhatsApp or email), hotel zone or pickup address, party size, the type of group for a group booking, travel date, safari package, and optional notes (allergy, pregnancy, mobility, child age, vehicle preference).
- Booking form requests: a request sent through the booking form on the contact page is saved with its booking reference in the platform's forms database, a file on the platform's Hostinger server, and emailed to the booking desk. When you send the form, your IP address, the site you came from and the pages you viewed here (up to 100 pages over a year) are kept with that request. If Google Analytics runs in your browser, its identifier for your browser and the start time of your visit are kept with the request too (section 9).
- Form drafts: once you have typed a valid email address or a complete phone number into the booking form, what you have typed so far is saved as a draft when you move away from the page before sending (leave it, switch tabs or apps, or move the pointer out of the window), and the booking desk gets an email about it so it can follow up. Nothing you type is saved before that; the platform only notes that the form was started, using the random identifier in section 8. A saved draft keeps the same details as a request, plus your browser type, the full web address of the form page, and the address of the page that linked you there. If you send the form from the same browser within 30 days, the draft becomes part of your request. The platform never emails you about a draft.
- Technical data: with each booking form request and each saved draft, the platform keeps your IP address and the approximate location looked up from it (city, region, country, postal code, approximate coordinates and internet provider). The lookup sends the IP address to ipwho.is, an IP-location service (section 4).
- Analytics data: Google Analytics records the pages you open here and the buttons you use, with your device type and an approximate location, under a random identifier for your browser. Section 9 lists what it records and how to switch it off.
- Payment data: if the booking desk sends you a secure card payment link after confirming your date, you pay on a checkout page run by Stripe, and the card is charged by the partner operator, Velari Tourism L.L.C. Your card details go to Stripe only: the platform never sees or stores card numbers, CVVs, or wallet credentials. The forms database keeps a record of each link: the AED amount, whether it has been paid, the Stripe checkout reference, and the booking it belongs to. Any other card or wallet payment is collected by the partner operator's own payment processor, not by the platform.
- Server logs: IP address, user agent, requested URL, HTTP status, timestamp. Retained 30 days for security audit, then deleted.
- Email correspondence: messages exchanged with the booking team, retained 24 months for partner-operator dispute resolution, then archived in cold storage for the statutory minimum required by UAE consumer-protection law (currently 5 years) and deleted thereafter.
The platform runs no advertising pixels. Google Analytics is its one analytics service.
2. Why we collect it
Booking enquiry data is collected solely to (a) confirm availability with the partner operator, (b) reply on WhatsApp or by email, whichever you chose, (c) hand the booking record to the partner operator for fulfilment, and (d) honour cancellation, refund, or rescheduling requests under UAE Federal Law 15/2020 and the cancellation policy at /legal/cancellation-refund-policy/.
Form drafts let the booking desk follow up with a guest who started a booking request and did not send it. The pages viewed and the approximate location tell the desk where a request came from and show the platform which pages lead to booking requests. The security check on the booking form (section 4) keeps automated spam out, and payment records match each card payment to its booking.
Google Analytics shows which pages and buttons lead to booking requests and paid bookings, and where people give up. The platform uses that to fix the pages that are not helping guests book.
Email correspondence is retained to evidence the booking conversation in the event of a partner-operator dispute, a credit-card chargeback, or a regulator query from the Department of Economy and Tourism.
3. Lawful basis (UAE PDPL Articles 4 to 6)
The platform processes personal data on two lawful bases: (a) performance of a service contract the data subject has requested (Article 4(2) of the UAE PDPL), and (b) legitimate interest (Article 4(7)) in fraud prevention, accounting, statutory record-keeping, and following up booking requests. That basis covers the form drafts, the page list and the location lookup in section 1, which run without a consent banner; you can object to them under section 7. Google Analytics, payment reports included, rests on the same legitimate interest and also runs without a consent banner; section 9 explains how to switch it off. Marketing, if introduced, will operate on a separate consent basis (Article 4(1)) with a documented opt-in.
4. Processors and sub-processors
The platform shares data with the following processors only:
- Velari Tourism L.L.C (UAE, DET license #1491675), the named DET-licensed partner operator. Receives the booking record, pickup details, and special-requirement notes needed to run the safari, and is the merchant for card payments made through a payment link from the booking desk.
- Google LLC (Google Workspace) for the platform's mailbox and for the email the booking form sends through Google's SMTP relay: the booking desk's copy of each request, draft and card payment, and the receipt sent to you. Google's Data Processing Addendum and standard contractual clauses cover any cross-border transfer.
- Google LLC (Google Analytics), as the platform's processor under Google's data processing terms, for the site statistics in section 9. The settings that would let Google use this data for its own products or for advertising are off: the account's data-sharing options, Google signals and ad personalisation.
- Hostinger International Ltd. (EU region, Lithuania) for application hosting, including the forms database that holds booking requests, drafts and card payment records. The site is fronted by Hostinger's reverse proxy and runs as a Node.js Express wrapper.
- Cloudflare, Inc. (United States) for DNS, CDN, and edge security when configured, and for Cloudflare Turnstile, the security check on the booking form when it is switched on. Turnstile loads only on pages that carry the booking form and reads signals such as your IP address and browser type to tell people from automated traffic. Cross-border transfer covered by Cloudflare's data-processing addendum and SCCs.
- Stripe, for card payments made through a payment link from the booking desk. Stripe receives what you enter on its checkout page, plus the amount, the booking reference and, if the desk adds it, your email address, and handles them under Stripe's own privacy policy.
One more service receives data: ipwho.is, an IP-location service, gets the IP address of each booking form request and each saved draft and returns its approximate location (section 1). It handles that lookup under its own terms and privacy policy.
The platform does not sell, rent, or share personal data with marketing networks, ad exchanges, or data brokers.
5. International transfer
The partner operator is UAE-domiciled and processes data inside the UAE. Google, Hostinger, and Cloudflare may process data outside the UAE (EU and United States). The platform relies on (a) the European Commission adequacy decision for the UK and EEA where applicable, and (b) standard contractual clauses with Google, Hostinger, and Cloudflare, in line with UAE PDPL Article 22 on cross-border transfer. Stripe and ipwho.is may also process data outside the UAE, each under its own terms.
6. Retention windows
- Booking enquiry data: 24 months after the safari date, then archived 36 more months.
- Booking requests in the forms database: up to 2 years after they are sent, then deleted, except a request with a card payment, which is kept with its payment record. The copy emailed to the booking desk follows the email correspondence schedule below.
- Form drafts that were never sent: deleted automatically 90 days after your last edit. A draft that became part of a request is kept with that request.
- The note that the booking form was started (the random identifier and the time): up to 2 years, then deleted.
- Card payment records: kept as accounting records for as long as UAE tax and accounting rules require. They are not deleted automatically.
- Backups of the forms database: kept for 35 days, then deleted. The only exception is the card payment records copied out of a backup for the accounts, which are kept as accounting records.
- Google Analytics data: kept by Google for 14 months, then deleted. For your browser's identifier, the 14 months start again each time you come back.
- The Google Analytics identifier and visit time stored with a booking request: kept and deleted with that request.
- Server logs: 30 days, then deleted.
- Email correspondence: 5 years from the last message in the thread, then deleted.
- Marketing data (when collected): retained until the data subject withdraws consent, then deleted inside 30 days.
7. Your rights as a data subject
Under UAE PDPL Articles 13 to 17 the data subject has the right to (a) request a copy of their personal data, (b) correct inaccurate data, (c) request erasure when the original purpose no longer applies, (d) restrict processing pending dispute resolution, (e) object to processing based on legitimate interest, and (f) lodge a complaint with the UAE Data Office at u.ae.
Requests should be sent to hi@bookmysafari.ae. The platform will respond inside 30 calendar days as required by Article 14 of the UAE PDPL. An erasure request covers the forms database too, except card payment records that accounting rules require the platform to keep. Erasure reaches Google Analytics too: the platform removes the analytics identifier stored with your request and asks Google to delete the data recorded under it. Without a request, the platform cannot tell which analytics data is yours; clearing this site's cookies gives your browser a new identifier.
8. Cookies
The booking form on the contact page sets one first-party cookie, _caf_uid,
holding a random identifier, the first time you type in the form or when you move away from
that page (leave it, switch tabs or apps, or move the pointer out of the window). The cookie
lasts 1 year. A copy of the identifier stays in your browser's local storage until you clear
this site's data, and if the cookie is deleted or runs out, that copy sets it again the next
time the form is used. On every page, your browser also keeps in local storage the site you
came from and the pages you viewed here (up to 100 pages over a year), and a marker that you
have started the form. That page list is sent to the site when you move away from the contact
page or send the form, and is kept only with a sent request or a saved draft; sending the form
clears it.
Staff who sign in to the booking desk or the content editor get a sign-in cookie; guests never
do. Google Analytics sets two cookies, _ga and _ga_SVC96YFLTB, which
last 13 months from your last visit (section 9). No advertising cookies are set, and the site
shows no cookie banner. Detailed cookie inventory at
/legal/cookie-policy/.
When your browser sends Do Not Track or Global Privacy Control, the Google Analytics tag does not load, so its cookies are never set. The platform sets no advertising cookies and does not sell or share personal data for advertising.
9. Google Analytics
After a page loads, or at your first scroll, tap or key press if that comes sooner, the site loads Google Analytics from Google. It records the page, the site that sent you, any campaign tags in the link, your device and browser type, and an approximate location that Google works out from your IP address. Google Analytics does not store the IP address.
It also records a short, fixed list of actions: reaching the end of a page, a click on a WhatsApp, email or booking button, a link to another site, a downloaded file, the safari packages you look at or pick, a shared blog post, and each step of the booking form. A WhatsApp click records which button you used and which prepared message it opens, never the text you send.
The booking form steps carry field names and broad values only: the package, the party size and travel date as ranges, how you want the reply, and the country chosen for your phone number. Your name, email address, phone number, pickup details, notes, booking reference and search terms are never sent. The page strips them from page addresses before anything leaves your browser, and Google's own redaction setting removes email addresses a second time. For a link to another site, such as a WhatsApp button whose message carries your booking reference, Google's redaction setting, not the page, removes the message text from the recorded link.
When you send the booking form while Google Analytics is running, the page adds its identifier for your browser and the start time of your visit to your request. Both are stored with the request in the forms database and never put in an email; a saved draft never holds them. If the booking desk later sends you a card payment link for that request, the platform's server tells Google Analytics that a checkout began, with the AED amount and the package. When Stripe confirms the payment, the server reports the purchase the same way, with the platform's internal payment number, and it may report a refund. These reports carry the identifier, the visit time and the amounts, and nothing that names you: no name, contact details, booking reference or card data. Each one is marked as not for advertising use.
Google handles this data as the platform's processor, with the settings in section 4 switched off. For visitors in the European Economic Area, the United Kingdom and Switzerland, Google Analytics does not collect city-level location or detailed device data such as the device model. Google keeps the data for 14 months (section 6).
You can keep Google Analytics off. Turn on Do Not Track or Global Privacy Control in your browser and the tag never loads. Or open bookmysafari.ae/#ga=off once in each browser you use: the site saves that choice in the browser and stops loading the tag, and bookmysafari.ae/#ga=on undoes it. Clearing this site's data removes the choice, and Safari may clear it after 7 days without a visit, so the browser setting is the one that lasts.
Switching Google Analytics off later does not reach a booking request you already sent: its identifier stays with the request, and the server can still report a checkout or payment for it. To have the identifier removed, email hi@bookmysafari.ae (section 7).
10. Security
The platform enforces HTTPS site-wide via HSTS with a 2-year max-age and the
preload directive. On the site's pages, the Content-Security-Policy keeps styles and
frames to this site, plus Cloudflare's security-check frame on the booking form, and blocks inline
scripts that the site's build did not produce. Form input is validated on the server and rate-limited
per connection and per email address. Email transport runs over STARTTLS to Google Workspace on
port 587. Card details are entered on Stripe's own checkout page and never reach the platform's
servers.
11. Children
The platform does not knowingly collect data from any person under 18 without verified parental consent. Booking enquiries naming a child as a participant are processed on the lawful basis of the booking adult's contract, not on the child's consent.
12. Changes to this policy
Material changes are announced on this page with the new "Last updated" date. Subscribers to a marketing list (when introduced) will receive an email summary of the change.
13. Contact
For data-subject requests or privacy questions: hi@bookmysafari.ae.