Cookie Policy

This policy explains the cookies and similar technologies used on mumbaitempledarshan.com. It sits alongside our Privacy Policy, which covers personal information generally — what we collect when you enquire or book, and your rights over it.

Reading this website requires you to give us nothing. Nothing here identifies you by name, and none of it is used for advertising.

A cookie is a small text file a website asks your browser to keep, and which the browser sends back on your next visit. Websites use several other mechanisms that do the same job, and this site relies on them more than on cookies. So that this policy describes reality rather than a template:

Session storage

Information your browser holds only until you close the tab. Cleared automatically. This is where we keep how you arrived at the site.

Local storage

Like session storage, but it survives closing the tab. Our analytics tool uses it to remember its anonymous identifier for you.

IndexedDB

A small database inside your browser. Ours holds a copy of page content so the site can work offline, and — for our staff only — a sign-in session.

Cache storage

Where the site's offline copy lives: pages, fonts, images and scripts saved by a service worker so the site loads instantly and works without a connection.

Service worker

A small script that manages that offline copy. It is why you can read a temple page in a basement with no signal.

Throughout this policy, "cookies" is used loosely to mean all of these.

Stated plainly, because it is unusual enough to be worth saying:

• No advertising cookies. We run no advertising on this website.
• No tracking pixels. There is no Meta Pixel, no LinkedIn or X tag, and no conversion pixel of any kind.
• No tag manager. Nothing can be injected into this site later without a code change and a fresh deployment.
• No cross-site profiling, no audience building, no retargeting, and no data broker.
• No third-party font request. Every typeface is served from our own domain, so reading a page sends nothing to Google Fonts or any font CDN.
• No selling or sharing of anything stored on your device.

4.1 · Strictly necessary — the site cannot work without these

4.2 · How you found us — session only

Four small values, all cleared when you close the tab. They exist so that when an enquiry arrives we can tell where it came from, and so that we can see which of our guides actually help people:

These stay in your browser and are sent to us only if you choose to submit an enquiry, in which case they are attached to it — see clause 2.2 of the Privacy Policy. If you never use the form, they are simply discarded when you close the tab.

4.3 · Analytics — optional, and how to switch them off is clause 9

Neither is used for advertising. Neither receives your name, your phone number or your email address from us — see clause 6.

Two parts of the site load content from someone else's servers. When they do, that company can set its own cookies and will see your IP address. This happens because your browser fetches their content, and their own policies govern it, not ours.

Google Maps

An embedded map appears on each temple and attraction page. Opening one of those pages loads the map from Google, which may set Google cookies. Other pages load no map.

Instagram (Meta)

The feed on our home page shows our own recent posts. The post images load directly from Meta's servers, so Meta can see your IP address and may set cookies. We fetch only our own posts, and we send Meta nothing about you.

WhatsApp (Meta)

Tapping a WhatsApp button takes you to WhatsApp. From that point you are on Meta's service under Meta's terms, and your conversation with us is covered by clause 2.3 of our Privacy Policy.

If you would rather avoid the map and the feed altogether, our packages, guides and booking pages carry neither.

Our analytics tool can record a session — a playback of how a page was scrolled and clicked — so we can find the places where the site confuses people. Two limits are built in deliberately:

• Everything you type is masked before it leaves your browser. We can see that a field was filled in. We cannot see your name, your number, your email address or your notes.
• Your phone number is never used as your analytics identity. It would be the easy way to connect a recording to a booking, and we have deliberately not done it — an analytics product has no business holding a guest's phone number. Recordings carry a random identifier only.

Recordings are also disabled entirely when the site runs on our own machines during development.

Every typeface on this site — the serif, the sans, and the Devanagari faces used for Hindi and Marathi — is served from our own domain. There is no request to Google Fonts or any third-party font service, which is a small but real privacy improvement: reading a page tells no font provider that you did.

Photographs, artwork and video are served from our own domain or from Google's storage, which we use as our own file store. The only exception is the Instagram feed described in clause 5.

Analytics data is processed by PostHog, in the United States, and by Google Analytics, outside India. Our own site content and files are hosted on Google's infrastructure. Clause 7 of the Privacy Policy covers these transfers and the basis for them.

The strictly necessary items in clause 4.1, and the session values in clause 4.2, never leave your device unless you submit an enquiry.

Nothing here is essential except the items in clause 4.1, and you can remove even those. There is no setting on our site to toggle analytics today — see clause 11 — so the controls are in your browser, and they work.

9.1 · Block or clear everything from this site

Chrome

Settings → Privacy and security → Third-party cookies, and Settings → Privacy and security → Site settings → View permissions and data stored across sites, to clear data for this site.

Safari (Mac)

Safari → Settings → Privacy for tracking prevention, and Manage Website Data to remove this site's data. On iPhone, Settings → Safari → Advanced → Website Data.

Firefox

Settings → Privacy & Security → Enhanced Tracking Protection, set to Strict, and Cookies and Site Data → Manage Data to clear this site.

Edge

Settings → Cookies and site permissions → Manage and delete cookies and site data.

Any browser

A private or incognito window discards everything when you close it, so nothing survives the visit.

9.2 · Block analytics specifically, and keep the site working

• Google Analytics: install Google's official opt-out browser add-on from tools.google.com/dlpage/gaoptout. It applies everywhere, not just here.
• Either tool: most tracking-protection features and content blockers already block them. Firefox's Strict mode and Safari's tracking prevention both do, as do the common browser extensions. We do not attempt to work around blockers, and the site is built to function normally when they are active.
• Turn off JavaScript for this site and no analytics load at all — but neither does the booking form.

9.3 · What stops working if you clear everything

Not much, and nothing important:

• offline reading stops until the cache rebuilds on your next visit;
• the first load of a page becomes a little slower;
• we lose the record of how you arrived, so if you enquire we may ask how you found us;
• our own staff are signed out of the internal booking system.

Your bookings, your ticket and your verification link are unaffected — they live with us, not on your device.

Some browsers can send a "Do Not Track" header or a Global Privacy Control signal. There is no agreed standard requiring a site to act on them, and we will be straight with you: our analytics tools are not currently configured to detect these signals automatically.

We would rather tell you that than let you assume you are covered by a setting that is doing nothing here. The controls in clause 9 do work, and asking us directly works too — write to contact@mumbaitempledarshan.com and we will exclude your analytics data.

Our reasoning, for what it is worth: we set nothing for advertising, we build no profiles, we share nothing with an ad network, and what we do collect is used to make the website clearer. We think that is a fair use of a website you have chosen to open, and we have made the opt-out routes in clause 9 as specific as we can rather than burying them.

We are working on a proper consent choice on the site itself. When it arrives, this clause will be rewritten to describe it, and the choice will be genuine — analytics off means off.

In the meantime, if you would prefer your visits were not measured, use clause 9 or simply tell us on +91 89764 23389 or at contact@mumbaitempledarshan.com and we will exclude your data from our analytics.

We will update this policy whenever we add, remove or change a tool that stores something on your device. The revision date is shown on this page. Because this is the one policy you can verify for yourself in your browser's developer tools, we would genuinely welcome being told if you find something here that does not match what you see — see clause 13.

If you have a question about anything on this page, or you have looked in your browser and found something we have not described, tell us. Message +91 89764 23389 or write to contact@mumbaitempledarshan.com and we will either explain it or correct the page.

Whichever of these documents your question is about, the fastest route to an answer is WhatsApp. We answer messages every day of the week, and usually within minutes.

Bookings and WhatsApp

+91 89764 23389

Tours and support

+91 79001 77209 · +91 90041 04537

Email

contact@mumbaitempledarshan.com

Website

mumbaitempledarshan.com

Hours

Tours daily 5:00 AM – 9:00 PM · WhatsApp answered every day

Operating base

Mumbai, Maharashtra, India

Our full registered address is available on request — ask on WhatsApp or by email and we will send it to you. If you need to serve a formal notice, please request it in writing at contact@mumbaitempledarshan.com so that we can confirm the correct address for service.