Working draft: 30 September 2026

Privacy Policy

Pre-launch draft. We describe the data used by the current site and will publish verified operator, contact, retention and rights procedures before live launch.

Data you provide

  • Sign-in identifiers and account profile details processed with Firebase Authentication.
  • Birth date, time and place or coordinates submitted to generate a Kundli or report.
  • Booking participant names, intentions, consultation messages and service history when you use those features.
  • Order, wallet and provider transaction references; raw card numbers and CVVs are not requested by this site.
  • Partner application and verification documents, kept in private storage with restricted review access.

How it is used

We use the information to authenticate you, calculate requested charts, arrange bookings and consultations, provide messages and video sessions, manage TEST payments and refunds, investigate service issues and protect accounts. Birth details may be sent to our calculation service to generate a requested chart or PDF.

Service providers and other users

Firebase supports sign-in; Supabase stores application records; Razorpay handles checkout and refund processing; Agora supports calls; hosting and calculation services deliver the site and charts. A booked practitioner receives the details needed to provide that service. Public visitors cannot browse private bookings or partner documents. We do not sell personal information.

Choices and requests

You can sign out and review your account, orders and bookings in the site. The current change-email, full export and deletion screens do not submit a request; those processes need a verified support channel and server workflow before launch. Please do not treat an on-screen draft as proof that data was deleted.

Security and retention

We use authenticated access and restricted database permissions for account and booking records. No internet service can guarantee perfect security. Retention periods, backup deletion procedures, cross-border processing and the incident contact must be confirmed against the deployed services before this policy is final.


Questions about this document? Contact our support team.

Ask Spirio