Privacy policy
This policy covers Bhagya for ChatGPT and this website, operated by Amol Parab (“we”, “us”), who is responsible for the personal data described here. It explains what we process, why, who receives it and how long we keep it. Questions or requests: amoluparab@gmail.com.
What we process
- Birth details you ask us to use: date of birth, time of birth (if known), place of birth or its coordinates, and an optional time zone or clock offset. We use them only to compute the chart, reading or match you asked for.
- Another person’s details: for Kundli matching or a couple reading you give a second person’s birth details and, if you like, first names. Please share someone else’s details only with their permission. Names are used only to word the reply.
- Today’s place and date: for panchang and daily readings, the town you name or, if you don’t name one, the approximate location ChatGPT provides to plugins (city, region, country, time zone and rounded coordinates). ChatGPT’s country also picks which sellers our remedies page shows.
- Purchases: when you buy, Gumroad or Stripe processes the payment and gives us your name, email address, country, billing details and purchase history. We use them for support, refunds, tax and fraud prevention. We never receive card details.
- Keys: when you sign in, the key you enter is checked with Gumroad (for Gumroad purchases) or against our purchase records (for keys bought on our website). Gumroad’s answer includes purchase details such as the buyer’s email and name; for sign-in we use only the purchase status and don’t store or log the rest.
- Panel preferences: the Bhagya panel in ChatGPT may remember display choices (North or South Indian chart, D1 or D9) in your browser’s storage. It never stores birth details there.
- Technical data: ChatGPT sends anonymized identifiers with tool requests. Our host records standard request logs (such as IP address, browser or app type, time and the address requested).
- Support emails: what you choose to tell us when you write.
Bhagya doesn’t ask for, infer or store health information, so please leave health details out of your requests.
Why we process it
- To provide what you ask for (charts, readings, matching, sign-in and purchases): this is necessary to provide the service under our terms.
- To keep free allowances fair, prevent abuse, and keep the service secure and working: our legitimate interests.
- To keep purchase records for tax and accounting: our legal obligations.
- Optional details, such as first names: used because you chose to provide them.
- ChatGPT’s approximate location, when you don’t name a place: our legitimate interest in giving local timings and relevant sellers.
Readings are produced automatically by software. We don’t use your data to make decisions that have legal or similarly significant effects on you.
What we keep
To count free and included full reports fairly, we keep a small amount of data in our database (Google Cloud Firestore):
- A pseudonymized, one-way identifier made with a secret key from ChatGPT’s user identifier (or from the conversation identifier when no user identifier is sent), and how many free reports it has used.
- For each full report opened, a one-way fingerprint of the pair, computed with a secret key from the two birth dates and rounded birth places, so opening the same pair again is free. It cannot be turned back into birth details or names.
- For report packs and memberships: the number of reports bought and used, with the Gumroad sale or subscription identifiers they came from.
- For purchases on our website: an identifier from which our server can reissue your key (so we can help if you lose it), with the plan, status, paid-through date and Stripe customer and subscription identifiers. The key itself also appears on your Stripe receipts and invoices.
What we do not do
- We do not store birth details, names or readings. They are processed in memory to answer the request. We don’t store Gumroad keys.
- We do not write birth details, names, keys or tokens to our logs; our logs record event names, outcomes and timings.
- We do not receive your ChatGPT conversations, only the details ChatGPT sends to Bhagya tools.
- We do not sell personal data or share it for targeted advertising (including as those terms are defined in California law), we show no ads, and we share nothing with the sellers on our remedies page.
- This website sets no cookies and uses no analytics, advertising or tracking scripts.
- We do not infer or record religious or philosophical beliefs.
Sign-in tokens
When you connect a key, ChatGPT holds sign-in tokens we issue. Access tokens expire after one hour and refresh tokens after 30 days. Refresh tokens contain your key in encrypted form so we can re-check your purchase; only our server can read them. If you continue free, without a key, the tokens contain no key and nothing that identifies you. You can disconnect Bhagya in ChatGPT at any time.
Who receives data
- Google Cloud (Cloud Run) runs the service and keeps request logs for a limited period; Google Cloud Firestore stores the records described above.
- Gumroad processes Gumroad purchases and verifies Gumroad keys; Stripe processes purchases made on our website. Their privacy policies, and the cookies on their checkout pages, apply to your purchase.
- OpenAI operates ChatGPT, which sends your requests to Bhagya and shows our responses. OpenAI’s privacy policy applies to ChatGPT.
- Our email provider stores the support emails you send us.
- Sellers you choose to visit from our remedies page (such as Amazon) receive nothing from us; their own privacy policies and cookies apply on their sites.
- Others when required: we may disclose information if the law requires it, to protect the rights and safety of users or others, or as part of a transfer of the service to a successor (such as a company we form), which would remain bound by this policy.
International transfers
We are based in the United States, and the service runs on Google Cloud in the United States. If you use Bhagya from elsewhere, your data is processed in the US. Where the law requires it, our providers use recognized safeguards such as the European Commission’s standard contractual clauses.
Retention
Birth details, names and readings: not retained after the request. Anonymized report counters and pair fingerprints: kept while the service runs, and deleted on request where we can identify them. Purchase records: kept for the life of the purchase and as required for tax and accounting. Hosting request logs: kept by our host for a limited period, typically no more than 30 days. Support emails: kept until your question is resolved and then for up to 12 months, except where we need them longer for legal, tax or dispute reasons (for example a refund record or an arbitration opt-out).
Children
Bhagya is suitable for general audiences aged 13 and over and is not directed at children under 13. Purchases, Kundli matching and couple readings are for adults 18 and over. Charts for anyone under 18 are read only for temperament, talents and learning, never for marriage or career timing. If you believe a child under 13 has given us personal data, contact us and we will delete whatever we can identify.
Your choices and rights
You can disconnect Bhagya in ChatGPT at any time, and manage or cancel a membership from your Gumroad receipt or our billing page.
Depending on where you live (for example in the EU, the UK, California or Washington), you may have the right to access, correct, delete or receive a copy of your personal data, to object to or restrict its processing, and to withdraw consent. To make a request, email us; we may need to confirm that it comes from you. Because we don’t keep birth details or names, and our stored identifiers are one-way, there is often nothing we can link back to you, and we’ll tell you what we hold. If we decline a request, you can ask us to reconsider by replying to our answer, and you may complain to your local data protection authority.
Security
Traffic is encrypted with TLS. Sign-in tokens are signed or encrypted with keys only our server holds, and stored identifiers are one-way. We keep dependencies up to date and review access regularly. No service can guarantee perfect security, but we work to protect the data we handle.
Changes
If we change how we handle data, we will update this page and its date, and note significant changes at the top of the page.
Contact
Amol Parab · amoluparab@gmail.com