Privacy
What we collect and why
Short version: nothing at all unless you type it into a form. An email address if you ask for the planning guide, and trip details if you send an enquiry. Never sold, and deleted on request.
Draft. This text describes what the site does and is written to the DPDP Act, but it has not yet been reviewed by a chartered accountant. It must be before the enquiry form accepts a real submission. The registered entity and grievance contact are still to be set.
Who is responsible
The Data Fiduciary — the entity answerable for the personal data described here — will be [registered entity name to be confirmed]. Until that is set, this page is a draft and the enquiry form is not accepting submissions.
What we collect
Only what you type in. There is no account to create, and we do not buy data about you from anyone.
If you ask for the planning guide: your email address, and nothing else.
If you send an enquiry: your name, how to reach you, which park or region you are interested in, rough dates, how many people are travelling, a budget band, and anything you write in the message. If you tell us a child is travelling, that is personal data about them too — see the section on children below.
Automatically: our server keeps standard web logs — IP address, browser, the page requested and when. These are what any web server records, we use them only to keep the site working and to investigate abuse, and we do not use them to build a profile of you.
How we count visits
Two things, and they work very differently. Neither is running at the time of writing.
Our own counting. We record which pages were requested and when, on our own server. No cookie is set, nothing is sent anywhere else, and nothing in that record can be traced back to you — no IP address kept, no device fingerprint, no identifier of any kind. It tells us that a page was read, not who read it. Because it cannot identify anyone, it does not need your permission and there is nothing to opt out of.
Google Analytics. This one does set cookies and does send data to Google, including outside India. So it will not load at all until you have agreed to it. The request will be a real choice with nothing pre-ticked, refusing will not change what you can read here, and you can change your mind later.
We are adding both because they answer different questions. Our own counting is the honest total — it sees everybody. Google Analytics only ever sees the visitors who accept cookies, and a good number decline. Having both is how we avoid mistaking the people who accepted for the people who came.
Why we collect it
The email address is used to send the planning guide you asked for, and occasional notes when something changes that would affect a trip — a permit fee revision, a booking window moving. Nothing else.
The enquiry details are used to answer your question and, where you have agreed to it, to introduce you to a lodge or operator who can quote for the trip. That introduction is the point of sending an enquiry, and we name the partner before we pass anything to them.
Consent, and taking it back
Each use is asked for separately and nothing on this site is ever pre-ticked. Agreeing to receive the planning guide is not agreeing to be contacted about a trip, and agreeing to an enquiry being answered is not agreeing to it being passed to a partner.
You can withdraw consent at any time and it must be as easy as giving it was: one click in any email we send, or one message to the address below. Withdrawing stops future use. It does not undo something already done — if an introduction has been made, that partner already has your details and you would need to ask them directly.
Who else sees it
Lodges and operators, where you have agreed to an introduction. We name them first. Some are outside India, so if you ask to be introduced to one, your enquiry details will be sent there — we will say so at the point we ask.
Service providers we cannot run without: the company that hosts this site, the service that sends our email, and — once it is live — Google Analytics. They process data on our instructions and are not permitted to use it for their own purposes.
Nobody else. We do not sell personal data, we do not trade it, and we do not pass it to advertisers. Operators cannot buy a position on this site and they cannot buy your details either.
How long we keep it
Enquiries are kept for 24 months after we last hear from you, then deleted. A safari is usually planned three to nine months ahead and people come back, which is why it is that long rather than shorter.
Newsletter subscriptions are kept until you unsubscribe. Server logs are kept for a short period for security purposes and then discarded.
Children
This is a family travel site and enquiries often mention children. Under the DPDP Act anyone under eighteen is a child, and we will not knowingly collect their personal data without verifiable consent from a parent or guardian.
We do not track children, we do not advertise to them, and we do not build profiles of them — all three are prohibited outright and we have no interest in any of them. If you tell us a child is travelling, we use that only to answer your question, because parks price and restrict entry by age. If you believe we hold a child’s data without proper consent, write to us and we will delete it.
Your rights
You can ask us to:
Tell you what personal data we hold about you and who we have shared it with. Correct anything that is wrong, incomplete or out of date. Delete what we hold, unless we are required by law to keep it. Withdraw a consent you gave earlier.
You may also nominate someone to exercise these rights on your behalf if you die or become incapacitated, which is a right the DPDP Act gives you specifically.
Complaints
Write to [grievance officer and email to be confirmed]. We will respond within 30 days.
If you are not satisfied with how we handle it, you can complain to the Data Protection Board of India. You do not need our permission to do that, and you do not have to come to us first.
Security
The site is served over HTTPS and access to enquiry data is limited to the people who need it to answer you. No system is perfectly secure, and we would rather say that than imply otherwise. If a breach occurs that affects you, we will tell you and the Data Protection Board, as the Act requires.
Changes
Last updated 2026-08-31. If we change what we collect or why, we will update this page and date it. Where a change needs your agreement, we will ask again rather than assume the old consent covers it.