Astro Dadi logoAstro Dadi

Legal

Privacy Policy

Effective 13 September 2026. This policy explains how Astro Dadi collects, uses, shares, retains, and protects your personal data, and your rights under the Digital Personal Data Protection Act, 2023 (“DPDP Act”).

1. Data Fiduciary

Astro Dadi is operated by Hrithik Nayak, an individual based in Jaipur, Rajasthan, India. It is not a registered company. As the Data Fiduciary, they decide the purposes and means of processing your personal data, and are personally responsible for it under the DPDP Act.

You can reach us about anything in this policy at support@astrodadi.com.

2. Personal Data We Collect

  • Birth details you submit: date of birth, time of birth, and birth place.
  • Derived location data: latitude, longitude, and timezone for the birth place.
  • Account data (when you sign in with email, Google, or Apple): name, email address, phone number if you provide one, and profile image. Sign-in is operated for us by Clerk.
  • Usage data: charts you generate, chat messages with the AI, saved sessions, response ratings, and optional feedback comments.
  • Billing data: subscription plan and payment status. Card details are handled entirely by the payment provider and we never see or store them — that is Razorpay for subscriptions bought on this website, and Apple or Google for subscriptions bought inside the mobile app.
  • Pseudonymous analytics data: sanitised page paths, broad product interactions, and a randomly generated browser identifier. If you sign in, we link this activity to an opaque internal account ID. We do not send your name, email address, birth details, chart or chat content, or payment details to analytics.
  • Technical data: IP address and user agent, used for security, rate limiting, and the temporary processing described in Section 6.

3. Purpose of Processing (per category)

  • Birth & location data — to compute your astrological chart and power AI chat answers.
  • Account data — to authenticate you and maintain your saved charts and chats.
  • Usage data — to provide the service, enforce plan limits, and improve answer quality and reliability.
  • Billing data — to operate subscriptions and meet tax/accounting obligations.
  • Pseudonymous analytics data — to understand journeys across visits, measure aggregate use, and improve product flows.
  • Technical data — to protect the service from abuse and fraud.

4. Consent

We process your birth details on the basis of your consent, requested at the point you submit them. You may withdraw consent at any time from Settings → “Withdraw consent,” or by contacting the Grievance Officer. Withdrawing consent does not affect processing already carried out, and may mean we can no longer provide chart-based features.

5. Cross-Border Transfers

To deliver the service we share limited data with the following processors, some located outside India:

  • DeepSeek — the AI model that generates Dadi’s answers (People’s Republic of China). This is the most significant transfer we make, so we are specific about it: to answer a question we send your date, time, and place of birth, the derived coordinates and timezone, your computed chart, and the text of your question. We do not send your name, email address, phone number, or payment details.
  • Clerk — sign-in and account authentication (United States). Receives your email address, phone number if provided, name, and profile image.
  • Nominatim / OpenStreetMap and Open-Meteo — converting the birth place you type into coordinates (Germany / United Kingdom). Receives the place name only.
  • Razorpay — payment processing for subscriptions bought on this website (India). Receives your name, email address, plan, and an internal account identifier.
  • Apple and Google — payment processing for subscriptions bought inside the mobile app (United States). They are the seller of record; we receive only the resulting subscription status.
  • RevenueCat — reconciles those app-store subscriptions (United States). Receives an internal account identifier and your purchase and renewal history, and no other personal data.
  • Vercel — application hosting (United States).
  • Upstash — caching and rate limiting (United States). Holds short-lived keys that can include your IP address, an internal account identifier, and the birth place name being geocoded.
  • Resend — transactional email (United States). Receives the name, email address, and message you send through the contact form.
  • PostHog — pseudonymous product analytics for this website (United States). See Section 6.
  • Sentry — operational error monitoring for this website (United States). See Section 7.

We do not sell your personal data, and we do not use it to serve you advertising.

6. Pseudonymous Product Analytics (website only)

This section describes the astrodadi.com website. The mobile app contains no analytics software at all — see Section 8.

We use PostHog to understand page visits and broad product interactions. PostHog stores a randomly generated first-party analytics identifier in your browser so we can join activity across visits in that browser. If you sign in, we replace that analytics identifier with your opaque internal Astro Dadi user ID. We do not send PostHog your name, email address, or other profile properties.

PostHog may process technical request data such as your IP address, browser user agent, and hostname on its United States servers. We restrict event properties to sanitised routes and predefined product categories; URLs have query strings, fragments, and chart or chat identifiers removed before capture.

Response ratings include a separate random per-response correlation token so we can connect an answer's completion with its rating. Optional feedback comments stay in our application database and are never sent to PostHog. Coupon analytics include a predefined cohort category, never the redeemable code. After account erasure, redemption records retain no account link and only count toward the campaign cap.

We use PostHog session replay to review product usage, with every on-page text element and form input value masked before it ever leaves your browser, so chat messages, birth details, chart data, and other personal content are never visible in a recording. We disable surveys, heatmaps, automatic click capture, advertising profiles, and PostHog's own exception capture. We respect your browser's Do Not Track setting: browser analytics is not initialised, and billing analytics initiated from that browser carries the same suppression signal. Error monitoring is a separate, non-analytics function and is described in Section 7.

7. Operational Error Monitoring (website only)

This section likewise describes the website. The mobile app contains no error monitoring software — see Section 8.

We use Sentry solely to detect and diagnose software faults, so that broken pages, failed chart generation, and failed payments can be fixed. This is reliability engineering, not analytics and not tracking: Sentry receives no analytics identifier, no account identifier, no user record, and no behavioural event properties, and we do not use it to build any profile of you. Because it is not tracking, it is not governed by the Do Not Track behaviour described in Section 6 — but the categories excluded below are excluded for everyone, regardless of any browser setting.

Error reports are processed by Sentry in the United States and retained for 90 days, after which they are deleted. A report contains the error type and message, the source location in our own code, the normalised route (for example /chart/:id), the HTTP method and status, the runtime, the release, and the support request ID also shown to you when an error occurs.

We deliberately exclude, before any report leaves your browser or our servers: your name and email address; your IP address; birth date, birth time, birth place, coordinates, and timezone; chart data; chat questions, answers, and AI prompts or tool data; contact-form content; request and response bodies; form values; URL query strings and fragments; cookies and authorisation, session, and signature headers; chart, chat, session, and account identifiers; coupon codes; payment, subscription, and signature identifiers; API keys, tokens, and database credentials; and cache keys and values. Diagnostic console output is discarded rather than attached, and expected outcomes — validation failures, sign-in and permission checks, usage limits, and cancelled or stopped requests — are not reported at all.

We do not use Sentry for performance tracing, profiling, session replay, or logging.

8. The Mobile App

The Astro Dadi mobile app collects the same categories of personal data described in Section 2, for the same purposes, and sends them to the same processors listed in Section 5. Two differences are worth stating plainly.

First, the app contains no analytics and no error-monitoring software. PostHog and Sentry, described in Sections 6 and 7, run on the website only. The app does not track you across other companies’ apps or websites, contains no advertising identifiers and no advertising software, and never asks for your camera, photos, microphone, contacts, or device location.

Second, subscriptions bought inside the app are billed by Apple or Google rather than Razorpay, and are reconciled through RevenueCat as described in Section 5.

9. Data Security & Storage

Personal data is stored in a managed PostgreSQL database that applies encryption at rest at the infrastructure level, and is transmitted over encrypted (HTTPS/TLS) connections. Access is restricted to the operation of the service.

10. Retention

We retain your personal data for as long as your account exists. When you delete your account it is erased immediately and permanently, as described in Section 12.

Two things outlive the account, and neither is linked to you. Raw notifications from payment providers are kept for at most 90 days and then deleted automatically. A record that a promotional code was redeemed is kept with no link to your account, so that the code’s usage limit stays accurate.

Records of the payments themselves are held by the payment provider, not by us — Apple or Google for purchases made in the app, and Razorpay for purchases made on this website. Deleting your Astro Dadi account does not remove their records, and you can request those from them directly.

11. Your Rights

  • Access & portability — download all your data from Settings → “Export my data.”
  • Correction — edit your birth details and profile name in-app.
  • Erasure — delete your account from Settings → “Delete account.”
  • Withdraw consent — from Settings, at any time.
  • Grievance redressal — contact the Grievance Officer (Section 14).

12. Account Deletion

Deleting your account is immediate and permanent. There is no grace period and no way to undo it. Your charts, chats, saved sessions, ratings, feedback, usage records, and sign-in credentials are erased at once, your sign-in identity is deleted from Clerk, and your purchase record is deleted from RevenueCat.

If you subscribed on this website, we cancel that subscription for you before erasing the account. If you subscribed inside the mobile app, Apple and Google do not allow us to cancel on your behalf — you must cancel it yourself in your App Store or Google Play account settings, or billing will continue after the account is gone. The app tells you this at the point of deletion.

13. Children's Data

Astro Dadi is not directed to children under 18. We do not knowingly collect personal data of minors, and we do not track, target advertising at, or profile minors. If you submit birth details on behalf of a minor, you confirm you are the parent or lawful guardian and consent to the processing. If you believe a minor’s data has been provided without proper consent, contact the Grievance Officer for removal.

14. Grievance Officer

In accordance with the DPDP Act, grievances about your personal data are handled by Hrithik Nayak, acting as Grievance Officer, reachable at support@astrodadi.com. We aim to acknowledge and resolve grievances within 30 days. See our Grievance Redressal page for details.

15. Data Breach Notification

In the event of a personal data breach, we will notify the Data Protection Board of India and affected users in accordance with the timelines and manner prescribed under the DPDP Act.

16. Changes to this Policy

We may update this policy. Material changes will be communicated in-app or by email. The effective date above reflects the latest version.