Privacy

The default experience is tab-local. Saving is a separate, explicit action.

Birth facts and reports

Birth facts are sent to Jyotisya's calculation service for the requested calculation. The current calculated report is kept in session storage for this browser tab so an accidental refresh does not erase it. It is not added to an account, shared across devices, or retained as an account record unless you explicitly choose encrypted save. “Delete this report” clears the tab copy; downloaded JSON or PDF files stay on your device.

Ask conversations

The open thread is held in tab memory so follow-up questions make sense. To avoid uploading the full calculated report for every question, the calculation service can keep a bounded derived chart context in process memory for up to two hours and address it by its verified chart hash. It is not durable account storage; after a cold start the browser safely resends the verified context once. Released production answers use the deterministic verified chart service. Generative wording and attachment analysis are production-disabled, so those paths do not send questions, evidence, or uploaded files to a language-model provider.

Panchāṅga locality

On Vercel, a signed-in session can use the city-level locality that the deployment resolves from the sign-in request so sunrise and daily windows open in the right place. Jyotisya encrypts that city-level locality with the session and does not store the raw IP address. Precise device location is requested only when you press “Use my current location,” and the resolved locality is kept in that browser tab.

Accounts and deletion

Encrypted account save, purchase recovery, alerts, sharing, and deletion each require separate controls. Features that lack their required identity, delivery, or storage authority stay unavailable.

Operational logs may contain request identifiers, route templates, timing, release identity, and error status—not birth facts, question text, email addresses, or one-time codes.