Privacy Policy

The mobile app

• Calculations happen on your device. Panchang, festivals, muhurta and kundali are computed by the app itself. The location and dates you use for calculations stay on your device; the app does not upload them to us.
• Sync (optional, off until you turn it on). Sync keeps your saved kundalis and saved tithis the same on all your phones and tablets, through your own Google Drive. The app asks for one permission: its own hidden folder in your Drive, which gives it no access to your other files. The files there hold your saved kundalis (names; dates, times and places of birth; gender if given) and your saved tithis (a name and a lunar date). They travel between your devices and Google directly, never through our servers, and we cannot read them. Your settings and location are not synced. Turning sync off stops it and leaves the copy in your Drive; to delete it, open Google Drive on the web, then Settings, Manage apps, HinduCalendar, and choose "Delete hidden app data".
• Analytics. The Android app uses Google Firebase Analytics to collect aggregate usage statistics (for example, which screens are used and on what device model). This helps us decide what to improve. It does not include your calculation inputs. The iPhone and iPad app carries no analytics.
• Ads (free version). The free app shows ads served by Google AdMob, on Android and on iPhone and iPad. AdMob may use your device's advertising ID to serve and measure ads, as described in Google's privacy policy; on iPhone and iPad it does so only if you allow tracking when the app asks. Purchasing the ad-free unlock removes ads entirely.
• Purchases. The ad-free unlock is processed by Google Play Billing (on iOS, by Apple's App Store). Google or Apple handles the payment; we never see your payment details.

The Kaalshodh watch face

• Nothing collected. The Kaalshodh: Hindu Time Watch face for Wear OS contains no code of its own. It has no network access, no analytics and no ads, requests no permissions, and does not use the advertising ID.
• Its readings come from the app. The tithi, choghadiya and Hindu time on the dial are supplied by the HinduCalendar app on the watch, which computes them on the watch itself, as described above.

The website

• Analytics. hinducalendar.app uses Google Analytics to collect aggregate visit statistics (pages viewed, approximate region, device type). The site carries no ads.
• Calculations. When you view a panchang or kundali page, the date and location you choose are sent to our API to compute the answer. They are processed in memory; the application does not save them. Because they travel in the request URL, they do appear in the standard request log that Google Cloud Run keeps for every request (the URL, your network address, status and timing), which is retained for 30 days and then deleted automatically.
• Preferences. Your language and saved location live in your browser's local storage, on your device. They are not sent to us except as calculation inputs.
• No accounts. The website has no sign-up, login, or user profiles.

The MCP server

The MCP server at hinducalendar.app/mcp lets AI assistants (Claude, ChatGPT, and others) compute panchang, festival dates, muhurta and birth details. It requires no account and no authentication.

• Your questions are not stored. Tool arguments — including any birth date, time or place — are processed in memory to compute the answer and are never logged or saved. They are sent in the request body, which no log records.
• Operational logs. Each request logs only: which tool ran, the response status, how long it took, and a truncated one-way hash of the caller's network address (used for rate limiting and abuse detection). Separately, Google Cloud Run keeps its own request log for every request — your network address, the path, status and timing, but not the tool arguments. Both logs are kept for 30 days, then deleted automatically.
• Your AI assistant is separate. What you type into Claude, ChatGPT or another assistant is handled under that provider's own privacy policy before any of it reaches our server.

Sharing and third parties

We do not sell personal data, and we do not share it with anyone except the service providers that run our infrastructure: Google (Cloud Run, Firebase Hosting, Firebase Analytics, Google Analytics, AdMob, Play Billing) and Apple (App Store purchases), each acting under its own terms. There are no other recipients. The app's optional sync is not a recipient of ours: it stores your kundalis and tithis in your own Google Drive account, under Google's privacy policy.

Data retention

Server operational logs: 30 days. Aggregate analytics: retained per Google Analytics / Firebase defaults. Calculation inputs (dates, places, birth details): not stored by the application — they are processed in memory only. Where they form part of a request URL (website calculations), they are present in the platform request log for its 30 days. Synced kundalis and tithis (app, optional): kept in your own Google Drive until you delete them there; deleting the app does not delete that copy.

Changes and contact

If this policy changes, the new version will be posted at this address with an updated date. Questions or requests: alok.mandavgane@gmail.com.