Privacy · updated 26 October 2026
What we keep, and what we don't.
Jagadhatri Guide is a free guide to the Jagadhatri Puja in Chandannagar, Mankundu and Bhadreswar: this website and an Android app. There are no accounts, no ads, and we never sell or share data for advertising. This page covers both.
In short
- Your location stays on your phone, unless you choose one of the features below that sends a rough or one-off position.
- Sharing your block for the crowd map is off until you turn it on.
- Nothing we receive has your name, phone number or email. The app identifies itself with random numbers, not with you.
- Crash reports help us fix the app. They never include your position.
- Notifications are only the guide team's warnings, such as a procession delay, and you can turn them off at any time.
- A problem you report goes with no name or contact details: from the app with your phone's details, and only your phone can see it again; from the website with a random browser id.
Who we are
The guide is made by Nirjan Munshi, an individual, with friends from Chandannagar. It is not an official service of any puja committee, the police or the municipal corporation. Write to hello@jagadhatri.in with any question about this page.
The website
- No tracking. The site uses no analytics, no advertising and no tracking cookies.
- On your device. If you close an announcement, your browser remembers that in its local storage so it does not show again. If you send a report, it also keeps the random id described below. Nothing else is stored.
- The guide's own service. Every page asks the guide's own service, the same one the app uses, for the latest announcements and the corrections to the map we have approved since the site was last updated. Like any web server, it sees your network (IP) address with the request; it handles it as described under Network addresses below.
- Reporting a problem. The Something wrong? form sends what you wrote, the kind of problem, the pandal it is about if you sent it from one, and a random id that your browser makes and keeps, so the service can limit how many reports one browser sends in a day. There is no name, email or location, and the service stores the id only in scrambled (hashed) form. Please do not type personal details into a report.
- Other services your browser talks to. Map tiles come from OpenStreetMap's servers and fonts from Google Fonts; like any web server, they see your network address when your browser asks for them. The site is hosted on Cloudflare, which keeps the usual short-lived request logs. Links to Google Maps open Google's own site or app, under Google's privacy policy.
The app
Your location
The app asks for location to show the pandals near you and the blue dot on the map. The position is used on your phone and is not sent anywhere, except in the three cases below. You can turn location off at any time in the phone's settings; the rest of the app keeps working.
Crowd sharing (off unless you turn it on)
If you choose Share my block anonymously, every few minutes the app sends the block of about 165 m that you are in, never your exact position, with a random number that is replaced every day. The service only counts how many phones are in each block, and a phone drops out of the count ten minutes after it last checked in. Turn it off at any time in the crowd settings.
Busy reports
When you report how busy a pandal is, the app sends the pandal, how busy you said it was, your block and the same daily random number. Reports fade out of the crowd map after 30 minutes.
Helping fix the map
When you suggest where a pandal is, add a missing one, or confirm a pin, the app sends the spot you marked, any name or note you typed, and a one-off reading of your phone's GPS so the service can check you are really near the pandal. The service keeps the spot you marked, which is within 75 m of where you stood (answers from further away are not accepted), the time you sent it, your note, how far you were from it and how precise your GPS was, but not your GPS position itself. The app keeps a random number for these answers, and the service stores only a scrambled (hashed) form of it, so it cannot be traced back. Please do not type personal details into notes.
Reporting a problem
When you use Report a problem, the app sends what you wrote, the kind of problem, the pandal or walk it is about, the screen you sent it from, the app's language and version, and your phone's make, model and Android version. There is no name, email or phone number, and no location. It goes with the same random number as your map answers, stored only in scrambled (hashed) form, so the app can show you your reports and our replies under My reports, and nobody else can see them. For an app problem it also sends a random key that your crash reports are filed under, so we can find the crash that matches; the key identifies the app on your phone, not you. Please do not type personal details into a report.
Notifications
If you allow notifications, the app shows warnings from the guide team: the procession running late, a road closed, a crowd or safety notice. There are no adverts or reminders. To receive them, the app joins a warnings list for its language through Firebase Cloud Messaging, a Google service, which gives the app an anonymous notification address. We do not keep a list of phones or addresses; a warning carries only its text. Turn notifications off in the phone's settings at any time; the warnings still show as a banner in the app.
Crash reports
Release versions of the app send crash reports to Firebase Crashlytics, a Google service, so we can fix what broke. A report contains the error, the phone model, the Android and app versions, an installation identifier created by Firebase, and a few settings at the time of the crash: the language, the open tab, the filter in use, whether location was on (not where you were), how many pandals were in your plan, and whether the crowd features were on. It can also include which pandals or walks you had opened before the crash. Google's handling of this data is described in the Firebase privacy information.
Stars and shared walks
When you star a pandal for your plan, the app sends the list of pandals you have starred, with the same random number as your reports, stored only in scrambled (hashed) form. The app then shows how many people starred each pandal; only those totals are ever shown, never who starred what. When you see your route as a walk on the map, the app sends the positions of its pandals (never your own) so the service can trace the streets. A walk you share is a link that lists its pandals and nothing else.
Kept on your phone only
The pandals you have ticked off, your route, your settings and a copy of the latest announcements and routes stay on your phone. Uninstalling the app or clearing its data removes them.
Network addresses
Like any web service, ours sees your network (IP) address with each request. It uses a scrambled form of it, held briefly in memory, to stop flooding, and does not store it with what you send.
How long we keep things
- Crowd counts: about ten minutes. Busy reports: 30 minutes.
- Map suggestions and answers: until the end of the 2026 season, then deleted or kept only as the corrected pandal location.
- Reported problems, from the app or the website: until the end of the 2026 season, so you can follow them in My reports, then deleted. A correction they led to stays in the guide's data.
- Stars: while you keep them starred; unstarring removes yours, and all of them are deleted after the 2026 season.
- Crash reports: as long as Firebase keeps them, currently 90 days.
Your choices
Everything that leaves your phone is something you chose to do: turning on crowd sharing, sending a busy report, a problem report or a map answer. Because nothing is tied to a name or account, we usually cannot find a particular person's data; if you think we hold something about you, write to us with what you sent and when, and we will look and delete it.
Children
The guide is for a general audience and is not directed at children under 13.
Changes
If what the app or site collects changes, we will update this page and the date at the top before the change goes out.