mypanchang.com
mypanchang.com
Drishya Ganit Panchang ("we", "us") provides Hindu panchang, festival-date, muhurtha, and related Jyotisha calculations. This policy describes what information the site collects when you use it, why, and the choices available to you. We have written this from a direct audit of our own code rather than a generic template. Where something isn't fully settled yet, we say so plainly below rather than guess.
One of the cookies below is essential; the rest are optional and every one has a sensible
default if you decline or clear it. We classify preference cookies as functional
(they remember a choice); the one exception is mp_consent itself, which we classify
as essential: a site can't honor "you said no" without storing that you said it.
| Cookie | Stores | Expires | Purpose |
|---|---|---|---|
mp_consent | "accepted" or "rejected", your cookie-consent decision, nothing else | 1 year | Records your consent choice so we don't ask again every visit. Classified essential, not functional (see above) |
panchang_loc | A city ID and city/state name (e.g. "Chennai, Tamil Nadu"), not raw coordinates | 1 year | Remembers your last-viewed city |
panchang_lang | Language code | Up to 2 years | Remembers your language choice |
mp_fsect | Festival-tradition filter (e.g. Vaishnava/Smartha) | 2 years | Remembers which festival set you view |
panchang_ampm | 12h/24h display choice | 2 years | Remembers your time-format preference |
panchang_t24 | 24+ time display choice (after midnight shown as 25:30) | 2 years | Remembers your time-format preference |
panchang_numerals | Native-script numerals display choice | 2 years | Remembers whether numbers are shown in your language's script |
_mpThm | "light" or "dark" | 1 year | Remembers your theme choice |
A small number of older, legacy pages on the site still set a simpler cookie named
location (just a city ID, 30-day expiry) rather than the newer panchang_loc
format above, same purpose, older mechanism, being phased out.
Some information is kept only in your browser's own storage and is never transmitted to us at all. We list it here for completeness, not because it's "collected" in any meaningful sense:
panchang_input_history): your last 50 typed
questions, kept locally purely so the up/down arrow keys can recall them._skfPrefsV1): gotra, family names, and
similar fields you may enter to personalize a Sankalpa reading. Our own code is explicit that
this stays in your browser's local storage and is never sent to or stored on our server.Our main panchang application does not use your browser's GPS/location API. Your city is determined one of two ways: (1) you type a city name, which we look up against our own local database (sourced from GeoNames, but your search text is not transmitted to GeoNames or any other third party; the lookup happens entirely on our server), or (2) if you haven't chosen a city, we make a best-effort guess from your IP address, which is standard practice for approximating a region and is not stored beyond the session unless you save a city choice via cookie.
A small number of older, separate pages (our legacy eclipse-viewing calculator and some retired mobile pages) do request your browser's precise GPS location automatically when opened, in order to show eclipse visibility or a default city for that page specifically. If you use one of those specific older pages, your coordinates are sent either to our own server (the eclipse calculator) or to Google's mapping service to resolve a city name (the older mobile pages), never to any other third party. We are reviewing whether these older pages should be updated or retired.
If you choose to sign in with Google, we use Google's standard identity sign-in flow. We only ever request your basic profile (email address, name, and profile picture), the same information Google shares for basic sign-in on any site; we do not request access to your Gmail, Drive, Calendar, or anything else in your Google account.
What we store: your email address, name, last-viewed city, language, and your display settings (light or dark theme, 12- or 24-hour time, whether seconds are shown, native or English numerals, and the traditions you chose in the festival filter), so your settings follow you when you sign in on another phone or computer. We also note whether you answered our one-time question about the newsletter, so we do not ask again. We do not store your Google profile picture, your Google account ID, or any Google access/refresh tokens.
To remove all of this at once, choose Delete my saved settings in the menu while signed in. It deletes everything we keep for your account and signs you out; the settings on the device you are using stay in that browser until you clear them.
If you register for API access to our panchang data, we collect your name, email address, and organization (if provided) to issue and manage your API key, along with technical records needed to enforce rate limits and detect abuse: which endpoints you call, when, from what IP address, and how often.
We maintain a festival-announcement mailing list. What we store for each subscriber: an email address, a subscription status, and, if you give them, your name, city and language. We also keep a record of when and how you agreed to join.
How you join: on the subscribe page, where we e-mail you a link to confirm; or, after you sign in with Google, by clicking "Yes" when we ask once whether you would like the newsletter. In that case Google has already confirmed the address is yours, so no confirmation e-mail is sent. If you click "No", we do not ask again.
What it's used for: festival dates and important panchang days, about twice a month. Nothing else.
To unsubscribe: every send includes a standard unsubscribe link, or you can contact us directly.
Our site uses Cloudflare for DNS and as a reverse proxy/CDN (content delivery network), which speeds up delivery and provides basic network-level protection. We also use Cloudflare Redirect Rules for certain domain-level redirects. Cloudflare may set its own cookies as part of these services. See Cloudflare's own privacy policy for details of what they collect.
Our city database is built from GeoNames' public geographical data, mirrored into our own database. We do not send your searches to GeoNames live (see "How we determine your location" above).
Our servers are hosted by InMotion Hosting in Ashburn, Virginia, USA.
Our servers are located in Ashburn, Virginia, USA. If you're visiting from the EU, UK, or anywhere else outside the United States, using this site means your information is transferred to, stored, and processed in the US.
Google Analytics. We use Google Analytics to count visits and see which pages
are read. Google sets its own cookies for this (names beginning with _ga). In the European
Economic Area, the United Kingdom and Switzerland, these cookies are not set unless you agree. We do not
send your name, email address or account to Google Analytics. You can
block it with Google's Analytics
opt-out add-on.
Google AdSense. Pages served at www.mypanchang.com may show ads from Google AdSense. Google and its partners use cookies to show these ads, and may choose them based on your earlier visits to this and other websites. We never show ads inside the panchang chat answers, and we do not sell or share your account or mailing-list details with advertisers.
Visitors in the European Economic Area, the United Kingdom and Switzerland see Google's consent message on pages that show ads, and can accept, refuse or choose which uses to allow. Anyone can turn off personalised ads in Google's Ads Settings, or through aboutads.info and youronlinechoices.eu. Google explains how it uses information from sites like ours at policies.google.com/technologies/partner-sites.
Like virtually every website, our web server keeps standard access logs (the pages requested, the requesting IP address, browser type, and timestamp) for security monitoring and diagnosing problems. These logs are automatically rotated and deleted after 14 days.
In summary: preference cookies persist for the durations listed above. Account data (if you sign in) and API registration data are kept until you ask us to delete them; we do not yet have an automatic deletion schedule for either, and we've said so plainly rather than promise one that doesn't exist yet.
Under GDPR (and UK GDPR), you additionally have the right to:
Under CCPA/CPRA, you additionally have the right to:
We do not knowingly collect the categories of information CCPA defines as "sensitive personal information," so there is nothing to additionally limit in that category.
To exercise any of the rights above, for any jurisdiction, use the same contact method (see "Contact us" below).
This site is not directed at children, and we do not knowingly collect personal information from anyone under the applicable age of digital consent in their jurisdiction:
If you believe a child has provided us with personal information, please contact us and we will remove it.
We'll update the "Last updated" date at the top of this page whenever this policy changes materially. We audited our own code directly to write this version rather than starting from a template, and we intend to keep it that way: re-verified against the actual site, not just edited in place, whenever something meaningful changes.
Questions about this policy, or a request to access or delete your data? Reach us via our contact page, or write to Pundit Mahesh Shastriji directly through the site.