Privacy Policy

1. Who we are

SahiKundli is a brand operated by VJS Ventures (GSTIN: 07AUFPS4890R1ZK), a sole proprietorship of Vikram Jit Singh, based in New Delhi, India. Questions about this policy can be directed to [email protected].

2. What we collect

For a chart or report, we may collect the name, birth date, birth time, birthplace, coordinates, timezone, and birth-time confidence you provide. Some products also need a second person’s birth details, education stage, or an optional personal question. For a purchase, we collect your email address, payment and order references, report type, and any WhatsApp number you choose to provide. We also receive basic technical and usage data when you use the site.

The free chart does not require an email address or a sign-up. A paid purchase may create a service record linked to your email so we can fulfil and recover your report.

3. How we use your data

We use this data to calculate charts, generate and quality-check reports, process payment, provide secure report access, deliver the report by email or optional WhatsApp, respond to support requests, prevent abuse, maintain service records, and improve reliability. We do not use birth details or personal questions for advertising targeting.

4. What we do not do

• — We do not sell your data to any third party.
• — We do not share your data with advertisers.
• — We do not use your birth data for commercial purposes beyond delivering your report.

5. Service providers

We use service providers only for the work needed to operate SahiKundli. Google Cloud runs and stores the chart calculations. Supabase supports our database and account records. After the chart is ready, Anthropic helps explain it in clear language and review the writing. Razorpay and Apple process payments, Resend sends email, Meta handles optional WhatsApp delivery, and PostHog provides product analytics. The data sent depends on the task. Payment providers handle payment credentials; SahiKundli does not receive or store your full card, UPI, or banking credentials.

Some providers process data outside India. We require them to handle it for the contracted service, not for their own advertising.

6. Analytics

PostHog records page views, page exits, and selected actions such as a product-link click. It may receive browser, device, network, and session identifiers. We use this to understand and improve the product. We do not send birth details, report text, personal questions, or payment credentials to PostHog.

7. Data retention

We keep purchase, report, delivery, and support records for as long as reasonably needed to provide access, handle disputes, meet accounting or legal duties, and protect the service. Analytics follows the retention settings of our PostHog account. You may request deletion by writing to [email protected]. We aim to complete a valid deletion request within 30 days, except where a record must be retained for law, fraud prevention, or an unresolved transaction.

8. Your rights

You may ask us to access, correct, or delete personal data associated with you, or withdraw an optional delivery choice such as WhatsApp. Applicable rights and exceptions depend on where you live and which provisions of law are in force. Write to [email protected] from the email connected to the purchase so we can verify the request. Our Grievance Officer is Vikram Jit Singh ([email protected]). We acknowledge grievances within 48 hours and aim to resolve them within 30 days.

9. Cookies

PostHog may use cookies or local browser storage to maintain an analytics session. Payment and report-access services may also use storage that is necessary for their function. We do not use advertising cookies. Blocking browser storage may affect payment, report recovery, or analytics behaviour.

10. Security

We use access controls, private delivery tokens, signed report links, and established infrastructure providers to protect personal data. No internet service can promise absolute security. If you believe a report link or account has been exposed, contact us promptly.

11. Changes to this policy

We will update this page if our data practices change materially. The effective date at the top of this page reflects the most recent revision.