Privacy policy
What we collect when you reserve or write to us, who sees it, how long we keep it, and the cookie choices you have. Optional cookies start switched off.
In short
What does Sooty Tours do with my personal data?
We collect what you send us to arrange your tour. When you send a request we also record technical details, such as your IP address, device and visits. Card details go straight to Stripe. Analytics and advertising cookies are optional and start switched off. Sooty Tours (Canada) and Sooty Tours FZCO are each responsible for their own bookings.
- Responsible
- Each company, for its own bookings
- Cookies
- Analytics and marketing are off until you accept
- Card details
- Entered only into Stripe’s secure fields
Who is responsible for my data?
Applies to: Both companies
Each Sooty Tours company is responsible for the personal data it collects for its own bookings and requests.
Niagara & Toronto
Sooty Tours (Canada)
Responsible for the information collected for Niagara and Toronto requests and bookings.
Dubai & the UAE
Sooty Tours FZCO
Responsible for the information collected for Dubai and UAE requests and bookings.
Both companies share this website. Requests sent through it reach info@sooty.com, one address that both companies use. We pass each request to the company it concerns. If your request covers both destinations, each company looks after the part that concerns it. Both addresses are in our terms of service and in the footer of every page.
In this policy, “we”, “us” and “our” mean the company that handles your request or booking. Under each heading, a tag shows whose information the section covers. “Both companies” means each company, for its own bookings and requests.
What personal data does Sooty Tours collect?
Applies to: Both companies
When you send a request or write to us
- Your name and email address, and a phone number if you give one.
- The tour you are asking about, a preferred date, the number of guests, and any notes you add, such as a pickup area, a celebration, a mobility need or a question.
- If you come from a tour page: the options you chose, the estimate shown, and the page the form was sent from. The form also records the time you sent it and which company the request is for.
When you use the online checkout
- Your guests by age band, the date and time, add-ons, and the vehicle or package you chose.
- Your email address, phone number, the name of the lead guest, the pickup address and any special requests.
- Which payment option you chose, and the total.
- Card details go to Stripe, not to us. You type them into secure fields that Stripe provides. We receive from Stripe a reference to the saved card, its brand, its last four digits and its expiry date, and the result of each payment. We never see the full card number.
- A record of the card-saving agreement you ticked: the time, the version of the wording, and your IP address. We keep it as evidence of what you agreed to.
- A saved cart. Once you enter a valid email address, we save your selections, your email address and your first name, if you gave it, on our servers behind a private link. This lets us email you a link to finish your booking. See emails we send you.
To arrange a booking and your tour
We may need the names of the guests and a pickup place. Some experiences need more: ages for child fares, and health, pregnancy, mobility or dietary details where they affect safety or what the operator provides. Sunrise balloon flights also need passport or Emirates ID details for every guest, because they must match official records. You choose what to tell us, but if you leave out something that matters for safety, the operator may not be able to let you take part.
How you arrived
To know which advertising or link brought you to a tour, we keep a short record of how you arrived. It holds the campaign tags in the address you followed (such as utm_source), any advertising click identifier added by Google, Meta, Microsoft or TikTok, the first and last page you landed on, the site that referred you, the times, and a random session reference such as SY-7K2QX.
When you send us a request, this record goes with it, together with whether you were on a phone, tablet or computer, whether you were inside an app’s built-in browser, and your cookie choice. When you contact us from the site by WhatsApp or email, the same reference appears in the message you send, for example “(Ref SY-7K2QX · google-cpc · AE)”, so you can see it and we can find your request. The last part is the region of the site you were using (CA for Canada, AE for the UAE); it is not personal data. This record is part of your own request. It is not sent to Google or Meta unless you accepted Marketing.
Automatically
Like any website, the services that deliver this site receive your device’s IP address, your browser type and the pages you ask for, in standard technical logs used to keep the site running and secure. What we record with a request you send is described in technical details we record with your requests. The cookies and browser storage the site uses are listed in the cookie tables.
What technical details do you record with my request?
Applies to: Both companies
When we record them
We record these details when you send us something through the site:
- a contact form or a request form;
- a booking request at checkout;
- your email address at the details step of checkout. We save your unfinished booking so that we can email you a link to finish it, and the technical details are saved with it.
We do not store these details when you are only browsing. Our hosting provider keeps its own standard logs of every visit, as the section on who sees your data explains.
If you contact us by WhatsApp or from an email link on our site, the message we prefill may include a short line, for example how you arrived and how many times you have visited. You can see and edit it before you send. It never includes your IP address.
What we record
Recorded by our server when your request arrives. Some of it, such as your device and language, is what your browser announces to us.
- Your IP address.
- An approximate location worked out from your IP address: country, region, city, time zone, the first part of your postal code where available, and the name of the network, such as your internet provider. It is not your address and is never more precise than a city.
- Your device type (phone, tablet or computer) and, if your browser shares it, the device model; your operating system and its version; your browser and its version. We work these out from the description your browser sends about itself, called the “user agent”, and we keep that text too.
- Whether our site was opened inside another app’s built-in browser, such as Instagram or Facebook.
- Your browser’s language settings.
- The date and time of your request.
- The page you sent the request from and, if your browser shares it, the site that sent you there.
- Simple checks on the details above, for example whether a request looks as if it comes from an automated program or a privacy network, or whether your browser’s time zone differs from the location of your IP address.
Reported by your browser. We cannot check these, so we label them “reported by the browser”.
- A random visitor ID (it is not your name, your email address or an account), the number of times you have visited, the dates of your first and last visit, and how many pages you have viewed.
- The last few pages you viewed in this visit: page addresses only, without search terms.
- How you arrived, for your first visit and for this one: the page you landed on, the site that sent you, and any advertising campaign tags (utm) or advertising click identifiers in the link you used, such as those Google, Meta and Microsoft ads add to links. We remember click identifiers between visits only if you accept Marketing.
- Your screen and window size, screen sharpness (pixel density) and whether your device has a touchscreen.
- Your time zone, your list of languages, your browser’s brand and platform details, and your connection type if your browser shares it.
- Whether your browser let our site store data, and your cookie choice (accepted, declined or not made yet).
We do not record your precise location. Card numbers never reach our systems: they go straight to Stripe.
Why we record them
- Security and fraud prevention. To spot spam, bots and misuse of the booking form, to protect payments and to deal with disputes. A time zone that does not match the location of the IP address, for example, is something our team looks at.
- Handling and following up your request. Your language, time zone and device help us reply sensibly, and the number of visits tells us whether you are new or returning.
- Understanding how visitors find and use our site. Visits, pages and how you arrived show us which pages and sources bring people to us.
- Measuring advertising performance. Campaign tags and click identifiers show which ad led to your request, so we know which advertising to keep.
Apart from automatic limits on how many requests one network can send in a short time, we do not use these details to accept, refuse or price a request automatically. We do not sell them, and we do not use them to build profiles to share with others. They are kept in our own system. They are not sent to Google, Meta or any other analytics or advertising service. Those services run only if you accept cookies (see cookies, storage and your choices).
Our visit counter
To count your visits, our site keeps a small record in your browser: a random visitor ID, your number of visits, the dates of your first and last visit and the pages you have viewed. It is stored in your browser’s local storage, or in a cookie set by sooty.com if local storage is not available. “First-party” means that only sooty.com sets and reads it. No other company does. A new visit starts when you return after 30 minutes of inactivity.
The counter runs for every visitor, including if you decline analytics and advertising cookies. We use it to give our team context for your requests and to prevent fraud, not to follow you around the web. Its contents travel with the requests our pages make to our own server, such as checking a price or sending a request. We store them only when you send us something, as described above.
To clear it, delete cookies and site data for sooty.com in your browser settings (in most browsers, “Clear browsing data” or “Manage website data”). A private or incognito window deletes it when you close the window. After you clear it, your next visit counts as your first and gets a new random visitor ID. You can also block site data for sooty.com in your browser: the site still works, and your requests then arrive without visit counts. Some browsers delete this kind of record on their own after a while, so the count is approximate.
How this differs from analytics and advertising cookies. The counter is ours: it sets nothing for anyone else and sends nothing to anyone else. Analytics and advertising cookies are different. They are set by services such as Google Analytics, Google Ads and the Meta Pixel, they stay off unless you accept them in the cookie banner or in Cookie settings, and you can withdraw that choice at any time. Declining them does not switch the counter off; clearing your browser data does.
How long we keep them
We keep these details for up to 13 months after your request. After that we delete them, or we remove the IP address, location, visitor ID, page history and detailed device information and keep only general figures, such as the number of visits, the kind of device and the advertising campaign label, that do not identify you on their own. If we change this period, this page will say so.
Some things are kept differently:
- For a booking, we also keep the IP address and the time of your request with the booking record, as evidence of what you agreed to (for a card payment, your approval of the card step), for as long as a payment dispute could arise: up to 24 months after the tour date.
- In our security records we keep a scrambled, one-way (hashed) form of your IP address, which does not show the address itself: about 24 months in the activity log, and about a day for the limits on repeated requests.
- The notification email we receive about your request also lists these details. Emails stay in our company mailbox until we delete them. Backups kept by our database provider can hold deleted data for up to 30 days.
Who sees them
The people who handle requests and bookings see these details in our private admin page, which needs a sign-in link sent to an approved email address, and in the notification emails we receive at info@sooty.com. They are not in your confirmation emails or any other email to you, and we do not give them to a local operator or partner that runs your tour. Cloudflare, Google Workspace and Stripe handle them or their surroundings for us, as described in the section on who sees your data.
Who is responsible, and your rights
The company your request is for is responsible for the technical details recorded with it: Sooty Tours (Canada) for Niagara and Toronto requests, and Sooty Tours FZCO for Dubai and UAE requests. If a request covers both, each company is responsible for its own part. The two companies use the same website systems (hosting, database and email), and the visit counter in your browser is not sent to either company until you send a request.
You can ask what technical details we hold with your request, ask us to correct them, or ask us to delete them. Email info@sooty.com from the address you used, or give us your booking or request reference, and tell us which company your request was for. We may need to check that it is you. We delete or remove the technical details when you ask, unless we need to keep them to deal with a payment dispute, fraud or a legal requirement. If that applies, we will tell you. To stop the visit counter, clear your browser data as described above. You can also complain to the privacy regulator where you live.
Why do you use my data?
Applies to: Both companies
- To reply to your request and to check availability with the local operator or partner, where one runs your tour.
- To confirm and arrange your booking, to take payment as described in our terms of service, and to contact you about it before the day, on the day and afterwards if something needs putting right.
- To send the booking, payment and reminder emails described in emails we send you.
- To keep records of bookings and of what was agreed, including the records that tax, accounting and other laws require, and to deal with a payment dispute.
- To keep the site, the contact form and our inbox secure and free of spam and fraud, using the technical details we record with a request.
- To understand how visitors find and use the site and which advertising brings requests: through those technical details, and through the optional analytics and marketing tools only if you accept them in your cookie choices.
We do not sell your information. We do not use it for anything else. We do not send newsletters or marketing mailings at the moment, and if we ever want to, we will ask you first.
Who sees my data, and where does it go?
Applies to: Both companies
- The company concerned. The people there who reply to requests and arrange bookings. They also see the technical details recorded with a request, in a private admin page that needs a sign-in link sent to an approved email address, and in the notification emails we receive.
- A local operator or partner that runs your tour. Where a local operator or partner runs your tour, which is always the case in Dubai and the UAE and sometimes the case in Niagara and Toronto when we are busy, we give it what it needs to check availability and run the day: typically names, the number of guests, pickup details and a phone number for the day, plus any health, access or dietary needs you told us about and, for balloon flights, identity details. We share only what that operator needs for your booking. The operator then holds that information for the booking and is responsible for how it looks after it, under its own practices.
- Stripe, our payment provider, which receives your card details, your name, email address and phone number, and the amount, to save your card, authorize or take payment and prevent fraud. Its payment form also collects its own device and network information to detect fraud. Our servers do not send it the technical details described above. Stripe’s own privacy policy applies to what it holds.
- Resend, the email service that delivers our emails to you and to us. Resend processes each message, its recipient and its content, and keeps delivery records for a limited time. This includes the notification emails we receive about your request, which list the technical details above.
- Google, because our mailbox and our backup email delivery run on our Google Workspace account. Google processes the message, its recipient and its content, and keeps the copy in our mailbox. The notification emails we receive about your request, which list the technical details above, are in the same mailbox.
- Google Maps Platform, for address suggestions. When you type in an address box, our server sends the letters you type to Google so that it can suggest matching addresses. It receives those letters and nothing else that identifies you: not your name, email address, phone number, IP address or cookies. Google’s own privacy policy applies to what it holds.
- Cloudflare, which hosts this website and runs the secure service and database behind the checkout and the request form. It sees the IP address of every visitor, works out the approximate location, and keeps its own technical logs.
- Cloudflare Turnstile, a security check from Cloudflare on our contact form and on the request forms of request-only tours. It receives your IP address and some browser and device signals so that it can tell a person from an automated program, and gives us only a one-time pass or fail. See the security check on request forms.
- WhatsApp, if you choose to message us there. WhatsApp handles your messages and phone number under its own terms, as well as delivering them to us.
- Google and Meta, only if we switch on analytics or advertising measurement and you accept the matching cookie choice. What they receive is listed in the cookie tables.
- Authorities, where the law requires it or to protect someone’s safety.
We do not sell your information, and we do not share it with anyone for their own marketing.
Because the two companies share one inbox and phone line, and the providers above may store information in other countries, your information may be handled in Canada, the United Arab Emirates, the United States and elsewhere. We take reasonable steps to protect it wherever it is handled.
How are analytics and advertising cookies used?
Applies to: Both companies
By default the site stores only what it needs to work, plus our own visit counter. Analytics and advertising are optional, they start switched off, and nothing from Google or Meta loads unless you accept it.
Your choice
The first time you visit, a banner asks you to Accept all, Decline or Manage. The buttons have equal weight, and the banner tells you that our own visit counter is always on. There are two optional categories, and both are off until you switch them on:
- Analytics measures how the site is used.
- Marketing lets us measure advertising and, where you agree, show our ads to people who visited us on Google and Meta.
If your browser sends a Global Privacy Control signal, we treat it as a choice to leave Marketing off, and the banner offers “Accept analytics” instead of “Accept all”. We remember your choice for 12 months, then ask again. You can change it at any time. Withdrawing a category deletes the Google and Meta cookies that this site can reach and forgets stored advertising click identifiers.
Always on
Which region's tours we show first depends on the country Cloudflare works out from your IP address when you open a page. That choice is made for that request only and nothing about it is stored. If you choose a region yourself in the footer, we remember your choice in the sooty_mkt cookie below.
These are set by sooty.com itself and do not need a choice. They hold no advertising identifier and are never sent to Google or Meta. Most of them keep the site working; the visit counter is on for the reasons given in the section on our visit counter. Personalisation on this device is also on until you turn it off, and has its own section below.
| Name | What it does | How long | What it holds |
|---|---|---|---|
sooty_mktCookie | Remembers the region you chose in the footer (Canada or UAE), so the site keeps showing it. | Up to 12 months | The region code (ca or ae). It is set only when you choose a region yourself. |
sooty_ctxCookie | Keeps the home, tours and contact pages on the region of the tour page you are looking at, so a Dubai tour page is followed by Dubai pages. | 30 minutes from the last tour or destination page you opened | The region code (ca or ae). No identifier. |
sooty:vc and sooty_vcBrowser storage, or a cookie if storage is blocked | Our visit counter: counts your visits so that a request you send can say whether you are new or returning. | Until you clear it. The cookie version lasts up to 395 days, or less if your browser shortens it. | A random visitor ID, your number of visits, the dates of your first and last visit, pages viewed, and how you arrived (campaign tags and, only after Marketing, click identifiers). It is sent only to our own server, with a request. |
sooty_consentCookie, or browser storage if cookies are blocked | Remembers your cookie choice. | Up to 12 months | The version of the notice, Analytics yes or no, Marketing yes or no, and the time. No identifier. |
sooty_probe and sooty:probeA cookie and browser storage | Checks whether your browser lets the site store a choice. It is written and deleted at once. | Removed at once (the cookie is set for at most a minute) | A test value, nothing about you. |
sooty:consent-dismissedSession storage | Remembers that you closed the banner without choosing, so it does not return during this visit. | Until you close the tab | A single flag. |
sooty:attrSession storage | Remembers how you arrived, so your request or WhatsApp message can carry its source. | Until you close the tab | The arrival record described above, including the session reference. |
sooty:form:…Session storage | Keeps what you typed in a form if you leave the page and come back during the visit. | Until you close the tab, or you send the form | The values you typed. |
sooty:checkout:v1Session storage | Keeps your selections and the details you typed while you move between the checkout steps, or if you reload the page. | Until you close the tab, or you send your request | Your selections and the details you typed. Never card details. |
sooty:widget:…Session storage | Remembers the date and guest choices you made on a tour page during your visit. | Until you close the tab | Your date, time, number of guests and the options you picked. Never card details. |
sooty:addons-planSession storage | Remembers the add-ons you picked while you plan a Niagara day during your visit. | Until you close the tab | Your picked add-ons, the number of guests and the date you typed. |
sooty:received:v1:…Session storage | Carries your booking summary to the confirmation page after you send a request. | Deleted as soon as the confirmation page has shown it | Your tour, date, guests, payment choice and amount, and the email address you gave, so a typo can be spotted. Never card details. |
sooty:tracked:…Session storage | Stops one booking request being counted twice if you reload the confirmation page. | Until you close the tab | A single flag for that booking reference. |
sooty:pay:t and sooty:unsub:tSession storage | Hold the secure link from your email so a reload of the payment or unsubscribe page still works. | Until you close the tab, or the page has finished | The secure token from the link in your email. Never card details. |
sooty:saved:v1Browser storage on this device | Keeps the list of tours you save with the heart, so the Saved tab can show them again. It exists only after you save a tour. | Until you remove the tours from Saved or clear your browser data | Only the identifiers of the tours you saved. It never leaves this device: it is not sent to us, to Google or to Meta, and there is no account. |
Personalisation on this device
Your country chooses the region you see first. On top of that, the site learns from what you search for and which tours and places you open, and uses it to show a “pick up where you left off” shelf, your recent searches, and a more useful order. A tour from another region appears there only because you searched for it or opened it. It is on by default and needs no cookie choice, and you can clear it or turn it off below.
Everything it learns is kept in your browser on this device and nowhere else. Nothing you have stored here is sent to us, to Google or to Meta. If you accept Analytics or Marketing, a click on one of the suggested tours is counted like any other click on a tour card, and says which tour was clicked and that it came from the suggestions.
| Name | What it does | How long | What it holds |
|---|---|---|---|
sooty:pz:v1Browser storage on this device | Remembers what you searched for and which tours and places you opened, so the site can show you where you left off and put what interests you first. | Searches: 30 days, and only the last 7 days appear as suggested searches. Tours and places you opened: 90 days. Older entries are deleted. You can clear it any time. | Your last few search texts, and the tours and places you opened, with times (about 1 KB). It is not sent to our server, to Google or to Meta, and it is not put in a cookie. |
sooty:pz:offBrowser storage on this device | Remembers that you chose “Clear and turn off”, so nothing is stored again. | Until you choose “Turn on again” or clear your browser data | A single flag. |
sooty:pz:t:… and sooty:pz:d:…Session storage | Stops one visit to a tour or place page being counted twice while you move around during your visit. | Until you close the tab | A single flag for each tour or place page you opened. It is not kept if you turned personalisation off. |
Only if you accept Marketing
| Name | What it does | How long | What it holds |
|---|---|---|---|
sooty_attrCookie | Keeps the arrival record for repeat visits, so a request later in the 90 days can still carry its source. | 90 days | The same arrival record: first and last visit. |
Optional tools
This site is set up so that analytics and advertising measurement can be switched on. When we switch them on, the tools below load only if you accept the matching category, and no request goes to Google or Meta before then. If you decline, none of them loads. Google’s consent signals start as denied, and the tools are not loaded until you accept, so nothing is collected from visitors who decline.
| Tool | What it is for | Cookies it sets | What it receives |
|---|---|---|---|
| Google AnalyticsAnalytics | Counting visits and seeing which pages and tours people look at. | _ga and _ga_…, about 2 years | The page address and title (our own events carry only the advertising campaign tags and click identifiers from the address; Google’s automatic page view can carry the whole address, so Google Analytics is set to replace the parts that could hold what you searched for or chose, such as search words, dates and guest numbers, with “(redacted)” before it stores them), the referrer, our events (such as the tour viewed, or that a search was made and how many results it found, never the words you typed), which regional site you are viewing (Canada or the UAE) and whether you chose it or we picked it from your country, your device and browser details, your approximate location worked out from your IP address, and your consent state. |
| Google AdsMarketing | Measuring which ads lead to requests and bookings, and showing our ads again to people who visited. | _gcl_au, and _gcl_aw and _gac_… when you arrived from an ad, 90 days | The advertising click identifier, the pages viewed, and conversion events (a request, a booking request, a WhatsApp or phone click) with a value, a currency and a reference. |
| Meta PixelMarketing | The same, for ads on Facebook and Instagram. | _fbp and, when you arrived from a Meta ad, _fbc, 90 days | Page views, and events such as a tour viewed, checkout started, a request sent or a contact click, with the tour, a value and a currency, which regional site you are viewing, plus Meta’s click and browser identifiers. Meta’s pixel also reads the page address itself, including any search words in it (for example when you open “See all results” or use the tour search on the Tours page). |
If we use Google Tag Manager to run these tools instead, the same rules apply and this table will say so. We set Google Analytics to keep its data for no longer than 14 months.
What we never send to Google or Meta
No name, email address, phone number, message, pickup address, booking notes or payment details is put in any tracking event. If we ever turn on enhanced conversions in Google Ads, which would pass a protected (hashed) email address and phone number to Google for visitors who accepted Marketing and sent a request, we will say so here first.
The security check on request forms
The contact form, and the request form on a tour that is request only, are protected by Cloudflare Turnstile. It works in the background, usually without asking you to do anything, to confirm that the person using the form is not an automated program that sends us spam or floods our inbox.
- When it runs. When you open a page with one of these forms and the form comes into view, or when you start to use it, your browser loads a script from
challenges.cloudflare.com. It does not run on other pages, and it is not used on the checkout. - What it checks. Cloudflare receives your IP address and some browser and device signals, and may keep a small amount of data in your browser to run the check. It uses them to tell people from automated programs. When you send the form, your browser passes us a one-time result, and we ask Cloudflare to confirm it. We receive only that pass or fail. We use it for nothing else.
- No choice in the cookie banner. It is a security measure that keeps the forms usable, so it runs whether or not you accept analytics or advertising cookies, and it is not one of the optional tools listed above. Cloudflare’s own privacy policy applies to what it holds.
- If it cannot run. If your browser or an extension blocks it, the form may ask you to try again. You can always message us on WhatsApp or write to us by email instead.
Payments, fonts and links
- The payment step. On the payment step of the checkout, Stripe loads its own scripts and may set its own cookies to run the payment securely and prevent fraud. This is not advertising. See Stripe’s privacy policy.
- Address suggestions. When you type in an address box, the letters you type are sent from our server (not from your browser) to Google Maps Platform, to suggest matching addresses. Google receives those letters and nothing else that identifies you: not your name, email, phone number, IP address or cookies. We do not keep what you type there unless you send the form. Your browser makes no request to Google and no cookie is set.
- Fonts. The site’s typefaces are served from our own site. Your browser makes no request to a font service.
- Links. Our pages link to maps, attractions’ websites and WhatsApp. Those services have their own privacy policies, and we do not control them.
- Your browser. You can also block or delete cookies in your browser settings. The site still works, but your choice may not be remembered. You can manage Google’s ad settings at adssettings.google.com and Meta’s ad preferences in your Facebook or Instagram settings.
Which emails will I get?
Applies to: Both companies
We email you about your booking. We send a reminder email only in the two cases below, and each has an unsubscribe link.
- About your booking. We email you when we receive your request, when we confirm it or cannot, before and after a payment is taken, if a payment fails, and with your receipt. These are about a booking you asked for, so you receive them whatever your other choices.
- Finish your booking. If you enter your email address in the checkout and leave without sending your request, we may email you up to four times: about 20 minutes, 24 hours, 48 hours and one week after you left. Each has a link to continue where you stopped. We say so beside the email field. We stop as soon as you send your request or unsubscribe, and we do not send them for a tour date that has passed.
- After your tour. Once, after a confirmed tour, we may email to ask how it went. For Niagara and Toronto tours the email can include a link to leave a Google review. Whether to write one is your choice.
Every email names the company sending it and shows its postal address. To stop the reminder emails, use the link in any of them, or write to info@sooty.com. We keep a protected record of your address so that we do not email you again. We do not use tracking pixels in these emails.
How long do you keep my data?
Applies to: Both companies
- Requests that do not become bookings: we remove the personal details after 24 months.
- Saved carts: the email address, name and selections are removed 30 days after your last activity, or at once when you send your request or unsubscribe.
- Bookings: phone number, pickup address, special requests, internal notes and the IP address in the card-saving record are removed 24 months after the tour date, and the last name is cut to an initial. The booking’s money records (the reference, the tour, the date, the amounts, the status and the payment references) are kept for 7 years, because tax and accounting laws in Canada and the UAE require us to keep them.
- Email records: the log of which emails we sent, without their contents, is kept for 13 months.
- Technical details recorded with a request: up to 13 months, then deleted or reduced to general figures. A booking also keeps the IP address and time of the request for up to 24 months after the tour date, as evidence. The details are in technical details recorded with a request.
- Cookies and storage: as shown in the tables above.
We take reasonable steps to keep your information safe: connections to this site are encrypted, payment is handled by Stripe, and only the people who need your details to arrange your booking can see them. No method of sending or storing information is perfectly secure, so please do not put payment card details in the contact form, in a WhatsApp message or in an ordinary email.
What choices and rights do I have?
Applies to: Both companies
Depending on where you live, you may have the right to ask us what information we hold about you and for a copy of it. You may also be able to ask us to correct it, delete it, limit or object to how we use it, or withdraw a consent you gave us. You can ask us at any time to stop emailing you.
To use any of these, write to info@sooty.com, say which booking or request it concerns and, if you can, which company. We may need to check that it is you. We cannot always agree, because we may have to keep booking records the law requires, but we will explain why.
If you are unhappy with how we have handled your information, tell us first and we will try to put it right. You may also be able to complain to the privacy regulator where you live.
Children
Applies to: Both companies
This site is for adults planning trips. Details about children, such as an age for a child fare, should come from a parent or guardian, and only as much as the booking needs. If you think a child has sent us information directly, write to us and we will delete it.
Changes to this policy
Applies to: Both companies
We update this page when the way we handle information changes, for example when we switch on a new analytics or advertising tool. The date at the top shows when it last changed. Our terms of service and cancellation policy are on their own pages.
How do I contact Sooty Tours about my data?
Applies to: Both companies
Write to info@sooty.com, call, or message us on WhatsApp. Say which booking or request you mean and we will answer you directly. To start a booking request instead, use the contact form.
We reply to every request personally.






