Privacy Policy

To calculate a chart, we process the birth date, birth time and chosen birthplace, including the place coordinates and timezone returned by place search. We do not require a full name, phone number, home address, Aadhaar, GPS permission, contacts or a photograph for a birth chart.

If you create an account, Supabase Auth processes your email address and password or your chosen Google sign-in identity, authentication records and session data. Google Sign-In shares your Google identity and basic account information with Google and Supabase. GrahaGati stores an internal user ID, not a duplicate email, inside its astrology records. Optional profile name and language preferences are saved locally.

Optional features process the information you choose to provide: Ask stores your questions, submitted voice transcripts and visible answers; voice input sends a recording for transcription; and Temples can keep selected temple IDs locally. Please do not put passwords, verification codes, payment credentials or unnecessary personal information in questions or recordings.

GrahaGati Pro is an optional auto-renewing in-app subscription. Apple or Google processes the payment account and payment instrument. RevenueCat receives the app account ID, purchase receipts or tokens, product/transaction information, entitlement status and device/app information needed to validate and restore purchases. GrahaGati uses the verified status to grant subscription access. GrahaGati does not receive or store a card number, CVV, UPI PIN or bank credential.

The standard guest chart flow does not require an account. Birth inputs travel in a private POST request through the GrahaGati server to the private Swiss Ephemeris service and are used to return the result; the guest calculation does not create a saved database profile. The mobile app keeps birth details and a short-lived chart cache in operating-system secure storage so the chart can reopen on that device. On this website, guest chart details and results use browser-tab sessionStorage. They survive page reloads and navigation in the same tab and are cleared when the tab closes or you reset the chart. If browser storage is unavailable, the chart remains in page memory for the current visit.

Birthplace autocomplete sends the typed place text—not the birth date, time, account or chart—to Geoapify through our server. The selected coordinates and timezone are then included in the chart request.

When a signed-in adult creates or updates a chart in the mobile app, the birth profile is saved to the account after calculation. The website also offers a signed-in save-profile action. A saved profile contains the birth date, optional exact time, birthplace, coordinates, timezone and internal user ID. Calculated chart JSON is not stored in that profile. It remains until you replace or delete it, or delete your account. A guest chart stays on that device and does not create a saved account profile.

We keep a minimal account record that the 18+ confirmation was made and which Terms and Privacy Policy versions were acknowledged. It does not contain a second date of birth and remains until the account is deleted.

Ask is available to signed-in users because it needs an owned saved profile and private history. Questions, conversation context, relevant calculated chart information and a one-way hashed account identifier go through GrahaGati's servers to OpenAI to produce replies. We do not automatically attach your account email, phone number, payment details, authentication token or raw internal user ID as model content; anything you include in a question or recording is part of the content sent. The updated mobile app asks you to acknowledge this sharing before first use of Ask or voice.

GrahaGati stores visible user and assistant messages, language, conversation identifiers and the minimum OpenAI response identifiers needed to continue or request deletion. OpenAI response storage is used for conversation continuity. Deleting a conversation removes local rows and requests deletion of every tracked OpenAI response; older chains for which complete provider identifiers were not historically recorded are labelled partial rather than presented as fully deleted.

Voice input sends the recording and chosen language to GrahaGati and OpenAI for transcription. The transcript is then automatically submitted as an Ask question and saved with the conversation. The app attempts to remove temporary recordings after processing; operating-system caches may persist until cleared. Listening to replies uses your device's speech service and its settings.

This is not a zero-retention AI service: our backend requests stored OpenAI responses for conversation continuity. Provider security logs and stored-response retention follow OpenAI's terms and the configured controls. Deleting GrahaGati history does not promise immediate erasure of every provider log or backup.

After the Gita sharing notice, your question and selected language go through GrahaGati to its private Gita engine and OpenAI, together with relevant approved Bhagavad Gita material. Birth details, chart data, account identifiers and authentication tokens are not automatically included in Gita model content. Anything personal that you type in a question is included. Gita uses the existing GrahaGati login. Question access is verified by the server; there is no separate Gita account.

This version keeps Gita questions and answers in screen memory rather than saving a Gita conversation history. Usage records remain linked to the GrahaGati account. Provider security and operational retention still applies; this is not a zero-retention promise. Verified source translations and daily editorial are English, distinct from AI-generated localized question guidance. Where mobile sharing is available, it opens a preview and the device share sheet; the website does not promise a saved Gita history or sharing feature.

Supabase Auth stores the session needed to keep you signed in. On mobile, session tokens, saved birth details and a short-lived chart cache use operating-system secure storage; preferences, the current conversation ID, AI acknowledgement and daily-notification choices use app-local storage. If previously enabled device biometric sign-in is used, the operating system verifies it; the app receives the result, not biometric templates. The website uses a language preference cookie/local-storage value, a user-scoped current-conversation ID and locally saved Temple item IDs. Guest charts and the selected Panchanga location use browser-tab sessionStorage; an authenticated saved birth profile remains in the account until it is changed or deleted.

The updated mobile app asks for foreground location permission after startup. When you open Panchanga or Temples, it can obtain your current coordinates and send them to GrahaGati to resolve the place/timezone and nearby results. Geoapify processes place searches or reverse-location requests when configured. Current mobile location stays in memory, is not your birthplace and does not replace birth details. You can deny permission and choose a place manually. No background location tracking is requested. On the website, current-location access follows the location action you choose.

Microphone access is requested only when you choose voice input; the updated mobile app shows the AI sharing notice before that permission. Sharing a generated reading card uses the operating-system share sheet; GrahaGati does not access your photo library. The website does not register daily-notification tokens. Remote mobile push registration is disabled in the current launch configuration, and the current notification code does not create new on-device daily schedules. You can revoke location, microphone or notification permission in device settings.

Plausible analytics is disabled unless the operator configures it. When enabled, it receives page/event and ordinary network data but our event properties exclude birth details, coordinates, account identifiers, questions and chart results. We do not automatically enrol users in marketing email.

No advertising or dedicated behavioural-analytics SDK is enabled in the mobile app.

Render, Supabase and other infrastructure providers may process IP address, user-agent and request metadata for security, abuse prevention and reliability. Application logs intentionally record event names, status, duration and non-identifying/internal references rather than request bodies, passwords, tokens, birth inputs or model tool outputs.

We process data to provide the requested calculation or feature, authenticate accounts, keep user-owned history, prevent abuse, secure and troubleshoot the service, and comply with applicable law. We do not use birth information for advertising profiles.

Anonymous chart inputs are not permanently stored by GrahaGati. Saved profiles and conversations remain until the user deletes them or the associated authenticated account is deleted. Local preference values remain until cleared. Security and infrastructure logs follow the applicable provider retention settings; legal obligations and provider backups can delay final erasure of limited copies.

Signed-in users can request deletion of their account and associated GrahaGati records from You. Conversations also have their own deletion controls. The deletion flow requests removal of application records, the Supabase authentication identity and tracked OpenAI responses. Cleanup can be partial or fail; versions that support background provider cleanup may report it as queued. RevenueCat customer cleanup is a separate provider action and may require operational follow-up. An app-account deletion response is not proof that every provider copy has been erased. If cleanup remains pending or is not confirmed, contact privacy@grahagati.in. Limited deletion/security records, provider backups, store transaction records or legally required records can remain for their applicable period. We do not promise a fixed provider-retention period that has not been verified.

Deleting your GrahaGati account does not cancel an Apple App Store or Google Play subscription or erase the store's purchase history. Use You → Manage subscription or your Apple/Google subscription settings to stop future renewal.

Configured processors may include Supabase for authentication and PostgreSQL; Render for web and private astrology hosting; OpenAI for astrology chat and transcription; Geoapify for place suggestions and reverse geocoding; RevenueCat plus Apple App Store or Google Play for subscription verification; and Plausible only if analytics is enabled. Google receives identity data only when Google sign-in is enabled and chosen. Their infrastructure may process data outside India under their own terms.

The service uses HTTPS, server-side secrets, input/file validation, request-size limits and authenticated ownership checks. Database row-level security is an additional protection where applicable; it does not replace server-side authorization. No internet service can promise absolute security; report a suspected issue without emailing unnecessary birth or account data.

You can use the standard chart without an account, choose whether to save a profile, access or correct saved birth details by replacing them, delete conversations, sign out and delete the account. You may also ask what personal data is associated with your account or raise a correction, access, erasure or grievance request. The public Delete account page explains both the in-app route and the verified email-request route.

For a privacy or data-deletion request, email privacy@grahagati.in from the address connected to the account when possible. Explain the request without including a password, token, payment credential or unnecessary birth details. We may need to verify account control before acting.

GrahaGati is intended for adults aged 18 and over. You may stop using Ask or voice, clear local app data and revoke optional device permissions at any time.

We may update this notice when the product, processors or law changes. The updated date and material changes will be shown here. This product implementation supports privacy controls but this policy is not a substitute for advice from qualified Indian privacy counsel.