Privacy

Drikganita is a location-based Hindu Panchang. Calculations run on our API using the place and date you choose. An account is optional; every page works without one.

Accounts. If you sign in, we store your email address, an optional display name, the saṅkalpa profiles you save (kartā name, gotra, janma nakṣatra and rāśi), and a copy of your browser preferences (place, saved places, region, display mode and saṅkalpam settings) so they follow you to other devices. We also keep a list of signed-in devices (browser name, IP address, and when each was first and last used) so you can see and sign them out. Our staff see only a shortened form of that address. A device entry is removed when you sign it out or when its session expires after 60 days.

Sign-in and account security. Sign-in codes are sent by email, work once, and expire after ten minutes. We store only a keyed hash of each code, never the code itself, and delete it after a day. Session cookies are HTTP-only and hold a random token, and we store only a hash of that token. If you add a password, we keep only a one-way bcrypt hash of it. Changing your password signs out your other devices. To change your email address you confirm a code sent to the new address, plus your password or, if you have none, a second code sent to your current address. Once the change is made, your other devices are signed out. We email you when your account is created, when someone asks to change its email, when your password or email address changes, when you ask to delete your account, and when it is finally erased. To stop abuse, your IP address and the email address you enter are counted for up to an hour to limit how many codes and password attempts can be made. That count is not linked to your account and expires on its own.

Your data and deletion. You can download or delete your data from Your account. Deleting signs you out everywhere and stops your reminders at once. You can restore the account by signing in within 30 days, even if new sign-ups are paused. After that, your account, profiles, ancestors, settings and devices are erased for good. We keep a short log of account events (for example sign-up, password and email changes, suspension, and any export or deletion by our staff) so we can help you and investigate misuse. When an account is erased, your email address and the details of each event are removed from that log, leaving only the event type and date. Our staff cannot see your saṅkalpa details in the normal course of support. Only a site owner can export or delete an account, and each time they do it is recorded in that log.

Śrāddha reminders. If you add ancestors, we store the name, relation, gotra, date of death or tithi and month, and the place where the rite is performed, and use them only to work out each year's śrāddha day. Reminders are sent as push notifications to devices you turn on and, if you choose, by email. We keep a record of each reminder sent for 90 days so we can fix delivery problems. Suspending, deleting or signing out of a device stops its reminders.

Browser storage. Your selected place, region, favourite places, theme, and display mode are saved in your browser's localStorage. Without an account they stay only in this browser, and clearing site data removes them.

Server cache. Computed Panchang and calendar JSON is stored on the server keyed by coordinates, civil date, timezone, and region, never by account, so repeat visits for the same place and day are fast. This is not a user profile.

Place search. Search queries are sent to our API, which proxies a geocoder (Photon) to resolve coordinates and timezones. Queries are not used to build user profiles.

Analytics. We use Google Analytics 4 to understand aggregate traffic (pages viewed, approximate region, device type). IP addresses are anonymized where supported. Google may process this data under its own terms. See the Google Privacy Policy. We do not sell personal data or build advertising profiles from your Panchang use.

You can limit Analytics with browser settings, extensions, or Google Analytics opt-out tools. Essential site features work without Analytics cookies.

Panchang timings are astronomical guidance and may differ from temple or family custom. See the site footer disclaimer.

Birth chart and match. The date, clock time and place you enter on the birth-chart, Krishnamurti cusp and marriage-match pages are sent to the API so the chart can be calculated. They are not written to the database and are not used as a profile. The browser tab keeps the last birth in session storage until the tab closes, so it can be reused on the match page.

Ask DrikG. Questions you ask, and the almanac facts computed for your place and the dates you name (tithi, timings, observances), are sent to OpenRouter to write the reply. The transcript stays in this browser tab until the tab closes.

Feedback. Notes you send on the Feedback page (name, email if you give one, and your message) are stored so we can improve the site. We do not use them for advertising.