01Privacy & cookies

What we hold, and why.

Version 0.1Draft Last updated September 2026Unreviewed Covers wyldexpedition.com

This notice is a draft scaffoldNot legal advice

It describes what the site does today, accurately. The retention periods, the named controller and the processor list are not yet confirmed and are marked. It has not been reviewed by anyone qualified in data protection law.

01

The short version

We collect what you type into the enquiry form. There is no account to create, no payment to take, and no data sold to anyone, ever.

We also run two tags that watch how the site is used: Google Analytics, so we can see which expeditions people actually read about, and Meta's advertising pixel, so the advertising we place on Facebook and Instagram reaches photographers rather than everybody. Between them they tell Google and Meta which pages of this site your browser looked at. That is the part of this page worth reading twice, and section 09 says what they set and how to refuse them.

The rest of this page is the same statement in the detail the law asks for.

02

Who holds it

The company trading as WYLD ExpeditionEntity unconfirmed is the data controller for everything described here. Contact details are in section 12.

We have not appointed a data protection officerTo confirm ; enquiries go to the address in section 12 and reach a person.

03

What we collect

When you enquire
Your name and email address, which the form requires. Optionally a phone or WhatsApp number, your country, the region, dates, species, experience level, longest lens and budget band you chose, and anything you wrote in the free-text box.
When you subscribe
Your email address, and nothing else.
Automatically
Ordinary web server logs โ€” IP address, browser, the page requested and when. These are operational records, not a profile of you.
Through Google Analytics
Which pages you opened, in what order, roughly how long you stayed, the site or search that sent you, and your broad device type. Google derives an approximate location from your IP address and does not keep the address itself in our propertyGoogle Signals setting to confirm . It is a count of behaviour, not a name โ€” we cannot look up who you are from it.
Through the Meta pixel
A script from Meta records that a browser loaded a page here, with the page address, the time, your IP address and your browser, and reads or sets the cookies in section 09. If you are signed in to Facebook or Instagram, Meta can match that to your account. We do not pass it your name, your email address or anything you typed into a formAdvanced matching โ€” to confirm in Events Manager .

We do not ask for, and would rather you did not send us, health information, passport details or anything else sensitive through this website. Where an expedition genuinely needs a medical declaration, we will ask for it separately and tell you how it is handled.

04

Why, and on what basis

  • To answer your enquiry and plan a departure โ€” because you asked us to, and because it is necessary to take steps towards a contract with you.
  • To send the newsletter โ€” only with your consent, which you can withdraw from any email or by writing to us.
  • To keep the site up and stop abuse โ€” our legitimate interest in a working, un-spammed website.
  • To meet accounting and tax obligations once you have booked โ€” a legal obligation.
  • To see which pages are worth keeping โ€” Google Analytics. Ours is a legitimate interest in knowing what a small catalogue is actually read for, but in the EU and the UK the cookies it sets need your consent first.
  • To measure and target our advertising โ€” the Meta pixel. In the EU and the UK this needs your consent too, and there is not yet a banner here to ask for itConsent gate not built . Section 09 says how to refuse both in the meantime.

Nothing here makes an automated decision about you. The pixel does profile you in the ordinary advertising sense โ€” Meta uses it to choose who sees our ads โ€” and it has no bearing on the price you are quoted, the dates you are offered or whether we take your booking.

05

How long we keep it

  • Enquiries that do not become bookings: 24 monthsPlaceholder from your last message, then deleted.
  • Bookings: as long as the law requires us to keep the financial recordPeriod unconfirmed .
  • Newsletter: until you unsubscribe.
  • Server logs: 90 daysPlaceholder .
  • What Google Analytics collects: held by Google, on a retention period set in the propertyRetention period to confirm in GA4 , then deleted or aggregated by Google.
  • What the Meta pixel collects: held by Meta on Meta's schedule, not ours. We cannot delete it for you directly โ€” section 09 says what we can do.

06

Who else sees it

Only the people who have to:

  • Our own team, to answer you.
  • The lodge, camp, vessel or ground handler on a departure you have actually booked โ€” the name on the room, and any dietary or mobility note you gave us.
  • Our hosting and email providers, as processors under contractProviders to be listed .
  • Google, for the analytics in sections 03 and 09, as our processor โ€” it measures on our instructions and the property is ours.
  • Meta Platforms, for the pixel in sections 03 and 09. Meta decides for itself what it does with that data, so for the pixel it is a controller alongside us rather than a processor working to our instructions. That is the difference between the two tags that matters most.
  • Anyone we are legally obliged to give it to.

We do not sell your data, and apart from the pixel above we do not share it with advertisers or data brokers. Nothing you type into the enquiry form goes to Google or to Meta.

07

Sending data out of your country

WYLD operates from India, so an enquiry sent from the EU, the UK or elsewhere is transferred to and stored in IndiaHosting region to confirm . Where a departure runs in Africa or the Polar regions, the necessary details go to the operator there.

Where the law of your country requires a safeguard for that transfer, we rely on standard contractual clausesMechanism to confirm . Ask us and we will tell you exactly what is in place for your booking.

Separately, both tags send what they collect abroad: Google Analytics to Google, and the pixel to Meta, each processing in the United States and the EU under their own transfer terms rather than oursGoogle and Meta terms not yet reviewed .

08

Your rights

Wherever you live, you can ask us to show you what we hold, correct it, delete it, stop using it, or send it to you in a portable form. Where we rely on your consent, you can withdraw it at any time.

We will answer within 30 daysPlaceholder and will not charge you for it. If you are in the EU or the UK you also have the right to complain to your national supervisory authority, and you do not have to come to us first.

09

Cookies & the pixel

One cookie is ours and strictly necessary. The rest belong to Google Analytics and the Meta pixel, both of which start when the page does. There is no consent banner here yetConsent gate not built , so until there is, the only way to refuse them is the browser-side controls at the end of this section.

Session cookie
Set by the application so the enquiry form can protect itself against cross-site request forgery. Strictly necessary; expires when you close the browser.
Google Analytics โ€” _ga and _ga_<property>
Set by this site on Google's behalf, to tell one browser from another so that two visits in a week count as one reader rather than two. Both last two yearsGoogle's default โ€” to confirm unless you clear them.
Meta pixel โ€” _fbp, and _fbc if you arrived from an ad
Set by this site on Meta's behalf, to recognise the same browser on a later visit and to attribute an enquiry to the ad that led to it. Meta sets the lifetime, typically around 90 daysDuration set by Meta . If you are signed in to Facebook or Instagram, Meta also reads cookies of its own.
Local storage
The site remembers small preferences on your own device โ€” whether you last used the grid or list view, for example. It never leaves your browser and we cannot read it.

To refuse both today: use a content or tracker blocker, or a browser that blocks them by default. For analytics specifically, Google publishes an opt-out browser add-on that works on every site. For the pixel, change what Meta may do with it at facebook.com/adpreferences. Or write to us at section 12 and we will ask both to delete what they hold from your visit, as far as their own tools let us.

If any further tag is ever added, this section changes first.

10

Security

The site is served over HTTPS, access to the enquiry inbox is restricted to the people who answer it, and we hold nothing we do not need. No system is perfect; if a breach ever affects your data and the law requires it, we will tell you.

11

Children

This site is not aimed at children and we do not knowingly collect their data. Family departures are booked by an adult, who gives us only what the lodge needs for the children travelling.

12

Asking us about any of this

Write to tarun@wyldexpedition.com, or call or message +91 85888 55599Postal address pending . Say what you want and we will do it โ€” there is no form to fill in.

Write to us. A person answers.

There is no booking engine on this site and there will not be one. Every expedition is confirmed by conversation, because at six guests the fit matters more than the transaction.

tarun@wyldexpedition.com WhatsApp +91 85888 55599

Replies within one working day

Memberships and accreditation

7 slots ยท none confirmedAwaiting client

01Conservation bodyReserved 02Tour operators associationReserved 03Insurance underwriterReserved 04Park authority permitReserved 05Responsible tourism bodyReserved 06Camera partnerReserved 07Guiding certificationReserved