Nava Panchangam
Privacy Policy
What Nava keeps, why, for how long, who helps us run it, and the rights you have.
Last updated: 2026-10-27
Who we are
Nava Panchangam (“Nava”, “we”, “us”) is a panchangam (Hindu calendar and astrology) service at navapanchangam.com and in the Nava Panchangam Android app. Nitin Srinivas K, a sole proprietor trading as Nava Panchangam decides why and how your personal data is used, and is the data controller (a “data fiduciary” under India's Digital Personal Data Protection Act, 2023). Based in: Mysuru, Karnataka, India. Email: privacy@navapanchangam.com. This policy covers the website, the Android app and the emails we send. If the English and the Tamil versions differ, the English governs.
What we keep, why, and for how long
This table lists everything we keep. The sections below explain how each part works and what you can do about it.
| Account | Email address, a hashed password (never the password itself), display name, your preferred calculation place and panchang system, your Google account identifier if you sign in with Google (we never receive your Google password), the state of your account (for example whether it is suspended, and why), and short-lived links we email you to verify your address or reset your password. Why: To run your account and sign you in, and to email you occasional announcements about Nava, which you can stop at any time with the unsubscribe link in every announcement. Basis: Our agreement with you (the Terms) and your consent. Kept: Until you close the account. |
| Birth details and tradition | Birth date, time and place, if you add them; your tradition (sampradaya). Why: To calculate your chart and choose which festivals and rules apply to you. Basis: Your explicit consent. Kept: Until you change them or close the account. |
| Location | Your current city; until you choose one, your approximate town, estimated from your IP address; and your device's position when you tap “Use my location” or “Use exact location”. Why: To compute times for your place. Basis: Our agreement with you. Kept: The city, until you change it or close the account. The approximate town only on your device. The device position and the IP estimate are never kept. |
| Family members, guests and invitees | Family members' names, relationships and birth details; gift ledger guests' names, places, relations, amounts and notes; email addresses of people you invite. Why: To provide those features. Basis: The person's own consent, which you confirm you have obtained before adding them; for a child, your consent as their parent or lawful guardian; for gift ledger guests, keeping the record of gifts you receive for your family's own use (for readers in the European Union or United Kingdom, our and your legitimate interest). Kept: Until you delete them or close the account. |
| Things you create | Alert rules and their notifications, your personal calendar events and reminders, reminders you mute, groups of email addresses you make, feeds and the rules you post in them, reports you file, feedback you send us. Why: To provide those features to you and, where you share them, to the people you invite; and to answer you. Basis: Our agreement with you. Kept: Notifications for up to 90 days; the rest until you delete it or close the account (see Account closure). |
| Records of actions | A record of important actions on your account and in shared feeds and gift ledgers (for example who added or removed an entry, and when you agreed to these terms), with the name shown at the time. For a gift ledger entry, the record can include the guest's name and the amount. Why: Security, settling disputes between people who share a feed or ledger, and proof of consent. Basis: Our legitimate interest and legal duty. Kept: Without a time limit; when you close your account, your name and email are removed from the records that carry them (see Account closure). |
| Usage counts | For each day you use a feature, a count against your account; the first day you used each feature; and the time you were last active. Why: To see which features are used and to keep the service healthy. Basis: Our legitimate interest in running and improving the service (for readers in India, the consent you give when you create your account, which covers this use). Kept: Daily counts for 90 days; the first-use dates and last-active time until you close the account. |
| Server logs | For each request: network address, time, and the address of the page or data asked for. Why: To keep the service running and secure. Basis: Our legitimate interest and legal duty. Kept: 180 days, on our server in India, as Indian cyber-security rules require (one year once the data-protection rules that require it are in force); never used for analytics. |
| Notifications | A push registration for your device or browser, if you turn notifications on. Why: To send the alerts you set up. Basis: Your consent, given when you turn notifications on. Kept: Until you sign out, revoke permission, or it stops working. |
| Usage statistics (optional) | Only if you allow it, and only while you are signed in: page views and a short list of in-app events, with an identifier stored on your device. Why: To learn which screens and features help readers. Basis: Your consent. Kept: Until you turn it off or sign out; either deletes the identifier from your device. |
| Error reports | Technical details of a failure, with personal fields removed. Why: To find and fix failures. Basis: Our legitimate interest. Kept: By Sentry, under its retention settings. |
Birth details and your tradition
Birth details are optional; without them the daily panchangam still works, and personal readings ask for them. Your tradition (sampradaya), such as Smartha or Sri Vaishnava, can reveal religious belief, which some data-protection laws, such as the European Union's, treat as sensitive. Choosing a tradition is optional. We keep it only if you choose one, with your explicit consent, given when you choose it, use it only to choose which festivals and rules apply to you, and never use it for anything else. You can set it to “General / Common Hindu” or remove your birth details at any time in Profile.
Device location
If you tap “Use my location” (or “Use exact location”), the app asks your device for its position once, with your permission. Your phone may let you choose between a precise and an approximate position; either way, the position is rounded on your device to about 11 km before it is sent, and is used only to find the nearest city in our list; we do not store it or keep a history of it. The city you end up with is saved like any city you pick by hand. The app never reads your location in the background, and asks your device for its position only when you tap the button.
Until you choose a city, the app opens on your approximate town. Cloudflare, which delivers every request, estimates a point from your IP address; we use it only to find the nearest town in our list, and calculate for that town, never for the point. We do not store the point. The town is remembered on your device, marked “approximate”, until you choose a city, or until “Use exact location” finds yours.
People you add
Some features hold details about people other than you: family members, gift ledger guests, and people you invite to a feed, a group or a gift ledger (the table above lists the details). Add someone only with their permission, or as the parent or guardian of a child. We use these details only to provide the feature to you and to the people you share it with. Anyone whose details are held this way can ask the person who added them, or us at privacy@navapanchangam.com, to remove them; we find and delete them within 30 days of verifying the request.
Account closure and retention
Account closure removes or anonymises the identifying profile and deletes personal configuration described on the account-deletion page. Some shared, financial, product-accuracy, and accountability records may be retained under an anonymised account identifier; that page lists the current categories and how to ask for additional review. Database backups are kept for 35 days so we can recover from a failure; a closed account's data leaves the backups when they are replaced. A record that you agreed to these terms is kept after closure, without your name or email, as proof of consent.
Sessions and cookies
When you log in, we set a single first-party session cookie to keep you signed in. This cookie is not used for advertising or cross-site tracking. On Android, the app displays the same service over HTTPS inside its embedded WebView, and the same session mechanism applies. A session ends after 90 days without use, or when you sign out.
Offline data and notifications
The app caches previously viewed panchang data on your device (browser storage) so it can work offline. Android notifications are delivered through Firebase Cloud Messaging; browser notifications use Web Push. Cached data stays on your device. You can remove the server-side push registration by signing out, and you can revoke notification permission in your device or browser settings.
Usage statistics
Nava counts page views and a short list of in-app events with PostHog only if you allow it, and only while you are signed in. When you create an account, and on the one-time screen that asks an existing account to agree to the Terms of Use and this policy, there is an optional box, “Share anonymous usage statistics to help improve Nava”. It starts unticked, and if you leave it unticked PostHog is not loaded at all. Visitors who are not signed in are never counted. You can change your choice at any time in the app, under Profile → Privacy & account. Automatic interaction capture and session recording are disabled, and the events are not linked to your account. When allowed, PostHog stores an analytics identifier in your browser's storage; turning usage statistics off, or signing out, deletes it from that device. We do not send your name, email, birth details or panchang readings in these events, and we do not use them for advertising or cross-site tracking.
Each event also says which language the app is shown in and whether you are using the website or the Android app, and one event records which screen you open, such as Home, Calendar or You. The events go to PostHog through our own address (navapanchangam.com/ingest/), which removes your session cookie before passing the events on, together with your internet (IP) address, as any website receives it when you visit.
Error reporting
When error reporting is enabled, we use Sentry to receive technical error and diagnostic information so we can find and fix failures. Performance tracing is disabled and Sentry is configured not to send default personal information. On our server, request bodies and local variables are excluded, and sensitive fields such as email, birth details, credentials, tokens, and precise coordinates are redacted before an event is sent.
Service providers
These companies process personal data for us under contracts (their data-processing terms) that limit them to the purpose named and require them to keep it secure. None of them is used to serve advertising in Nava Panchangam.
- Cloudflare — delivers every page and request, protects the site from attacks, and forwards email sent to privacy@navapanchangam.com (global network)
- Oracle Cloud — runs our server and database (Hyderabad, India)
- Google Sign-In — signs you in, only if you choose Sign in with Google (United States)
- Resend — sends account emails and announcements (United States)
- Firebase Cloud Messaging — delivers Android notifications you turn on (United States)
- Web Push — delivers browser notifications through your browser maker's push service (depends on your browser)
- PostHog — counts usage statistics, only if you allow them (United States)
- Sentry — receives error reports with personal fields removed (United States)
- Google Drive — keeps our database backups (Google data centres in several countries)
- Razorpay — would process payments; no paid plan is on sale today (India)
Where your data goes
Our server is in Hyderabad, India. Some service providers above are in other countries, including the United States, so your data may be processed outside the country where you live. Where the law requires it, we rely on the transfer safeguards those providers offer, such as the European Commission's standard contractual clauses (and the United Kingdom's addendum to them). Indian law currently allows these transfers; if the Government of India restricts transfers to a country, we will follow that.
Why we may use your data
If you are in India, we use your personal data on the basis of the consent you give us (which you can withdraw, see below) or, where the Digital Personal Data Protection Act allows it without consent, for a legitimate use it lists, such as meeting a legal duty. The other bases named in this policy (“our agreement with you”, “our legitimate interest”) are the bases the law of the European Union and the United Kingdom requires us to name for readers there.
You can withdraw your consent at any time, as easily as you gave it: turn usage statistics off in Profile → Privacy & account; remove your birth details or set your tradition to “General / Common Hindu” in Profile; delete a family member or gift ledger entry where you added it; or withdraw all consent by deleting your account in Profile → Privacy & account → Delete account, or by writing to privacy@navapanchangam.com. Withdrawing consent does not make unlawful what we did before you withdrew it. If you withdraw consent for details an account needs to work, such as your email address, we will close the account.
Your rights
You can ask to see the personal data we hold about you and who we shared it with, correct it, delete it, receive a copy (Profile → Privacy & account → Download my data), object to a use, restrict our use of it, withdraw consent, and name someone to act for you if you die or cannot act. Most of it you can change yourself in Profile; for anything else write to privacy@navapanchangam.com. We answer within 30 days. You can stop announcement emails at any time; we will still send emails you need for your account, such as password resets. We do not make decisions about you based only on automated processing that have legal or similarly significant effects on you; readings are calculations you choose to view. If you are not satisfied, you can complain to our grievance officer (below) and then to the Data Protection Board of India, through the online complaint process the Board publishes (you must first use our grievance process, as the law requires), or, if you live in the European Union or the United Kingdom, to your local data-protection authority.
Children
Nava accounts are for people aged 18 or over. When you open an account you confirm that you are, and we refuse an account whose own birth date shows the holder is under 18; we do not knowingly keep an account for anyone younger. Anyone may read the daily panchangam without an account. A parent or guardian may add a child as a family member and gives consent for the child by doing so. If you believe a child has an account, write to privacy@navapanchangam.com and we will close it.
How we protect it
Every connection is encrypted (HTTPS). Passwords are stored only as salted hashes, sessions are checked against our server on every request, staff need two-factor authentication, and staff see personal details only when they record a reason. No system is perfectly secure; if a breach affects your data we will tell you and the authorities as the law requires.
Data deletion
You can request deletion of your account and associated data at any time. In the app, open Profile → Privacy & account → Delete account, or open the account-deletion page in any browser. That page explains what is deleted, what may be retained, and how to submit the request.
Changes to this policy
When we change this policy in a way that matters, we tell you in the app and by email before the change takes effect and ask for your agreement again.
- 2026-10-27 — until you choose a city, the app opens on your approximate town, estimated from your IP address.
- 2026-10-18 — usage statistics: what each event carries (the app language, website or Android app, the screen opened) and that events go through our own address; PostHog is listed in the United States, where our PostHog project is.
- 2026-10-08 — rewritten in full: who we are, everything we keep and why, service providers, transfers, your rights, children, people you add, and usage statistics now off until you allow them.
- 2026-09-26 — the device may share a precise or an approximate position; either is rounded on the device.
- 2026-09-23 — “Use my location” added.
Contact and grievance officer
Questions, requests and complaints: privacy@navapanchangam.com. Grievance officer: Nitin Srinivas K, Mysuru, Karnataka, India, at the same email address. We acknowledge a grievance within 24 hours and resolve it within 15 days.