Last updated: 4 October 2026 · Applies to kpstellarastro.com and the KP Stellar Astro app
KP Stellar Astro ("we", "the app") is operated as an individual proprietorship by the site's developer. This policy explains what personal data we collect from visitors and account holders, why, how long we keep it, and how you can access, correct, or delete it — consistent with India's Digital Personal Data Protection Act, 2023 (DPDP Act).
| Data | Purpose | Retention |
|---|---|---|
| Email address (confirmed with a code or link), name, password (hashed) if you set one, and your Google account ID if you sign in with Google. | Account creation & sign-in | Until you delete your account |
| An email sign-up you have not confirmed yet (the address, name and hashed password you entered) | Creating your account once you confirm the code | Deleted after 30 minutes if not confirmed |
A cookie named __Host-kp_proof (a random value; the server keeps only a one-way code of it) set when you ask for a sign-in link, a sign-up code or a password reset, when an older account confirms its email with a code at sign-in (the password step-up), and when you add or change your sign-in email in Settings. It is a strictly necessary security cookie: it makes sure an emailed link works only in the browser where you asked for it, and it signs nobody in by itself | Device check for emailed links | Expires after 15 minutes at most |
Entries in your browser's local storage: kp_proof_pending (the email address, purpose and request number of a code you just asked for) kp_google_conflict (the email address Google was refused for), kp_signin_next (the page to return to after signing in, so an emailed link can bring you back) and kp_rp_saved (a Ruling Planets reading you chose to save on the Ruling Planets page). Nothing secret; none is sent anywhere by itself | Recognising the emailed link on this device, and offering to connect Google after you sign in with your email | kp_proof_pending is removed when you sign in (any way), abandon the request, or after 15 minutes (also when a page next loads). kp_google_conflict is removed when you answer the offer or after 15 minutes. kp_signin_next is removed when you finish signing in or after 30 minutes. kp_rp_saved stays on this browser until you replace it or clear your browser data; it is never sent to us |
| Sign-in and reset requests (the address, a one-way code of the link and code) | Letting you sign in or reset your password; limiting abuse | Deleted 24 hours after the request |
| Birth details you enter (date/time/place) for charts you generate | Computing your astrology chart — processed statelessly, only stored if you click "Save chart" | Guest use: not stored. Saved charts: until you delete them or your account |
| Saved charts, clients, rectification sessions | Letting you reload your own saved work | Until you delete them or your account |
| Your email, or a one-way code derived from it, from your Google sign-in, or (for accounts that signed in with a phone number) from that number, if you claimed a free welcome-credit offer (signup bonus, or the astrologer-registration bonus) | Preventing the same offer being claimed repeatedly by deleting and re-registering an account | Retained indefinitely — not removed when you delete your account, since its only purpose is recognising those details if they register again. Holds no other profile data |
| If you started a free desktop trial: a one-way code of your email, of your Google sign-in account, or (for accounts that signed in with a phone number) of that number | Giving one free desktop trial to each person, so it cannot be claimed again by deleting and re-registering an account | Retained indefinitely — not removed when you delete your account, since its only purpose is recognising those details if they come back. Holds no other profile data |
| If you activated a free desktop trial: a one-way code of your computer's device ID (the app cannot be traced back to the computer from the code), also noted on your account while it exists | Giving one free desktop trial to each computer, whoever signs in | Retained indefinitely — not removed when you delete your account, since otherwise a trial could be repeated on the same computer. Holds no other profile data |
| Older accounts only: a phone number you may once have added to your profile (it appears under profile in Download my data), and, for accounts that were created by signing in with a phone number, that number as the account's identifier | No longer used for anything. We no longer ask for a mobile number | Still held until we finish retiring phone-number sign-in and clear these stored numbers from older accounts; deleting your account removes them at once |
| Payment records (Razorpay order/payment IDs, amount, status) | Crediting your purchase, refunds, accounting | Retained indefinitely per Indian tax/accounting record-keeping law, but de-linked from your identity if you delete your account |
| Usage logs (which feature you used, when) | Abuse prevention, support, product improvement | 180 days, then automatically purged |
| Contact Us / feedback submissions (name, email, message) | Responding to your query | 180 days, then automatically purged |
| AI Explanation question history (your questions & the AI's answers about your own charts) | Letting you revisit a past answer from AI Explanation > Previous questions without spending another question | 180 days, then automatically purged, or immediately if you delete your account |
| The text of questions you ask a chart (Horary and AI Explanation), stored separately from your account under a one-way tag rather than your name, phone or email | Improving how accurately the engine works out which KP house a question belongs to — real wordings are the only way to find questions it reads wrongly. Reviewed in aggregate; the admin sees the question and the domain it matched, not who asked it | 180 days, then automatically purged, or immediately if you delete your account |
| Predictions you choose to track, and what you later report actually happened (signed-in users only) | Building your own track record on your saved charts, and letting us measure honestly how often our predictions are right. Reviewed in aggregate only — the accuracy figures we look at are counts, and never include your question text, your account, or which chart it came from | Until you delete the tracked prediction or your account. Unlike question history, these are not purged after 180 days — a track record with a hole in it would be worthless, and the whole point is checking a prediction against what happened years later |
| Known life events you add to a saved chart (what happened and roughly when), and the month you say a tracked prediction happened | Checking your chart's birth time against your own past, shown only to you | Until you remove them, delete the chart or prediction, or delete your account |
| IP address (rate-limiting only) | Preventing abuse of sign-up, sign-in and AI endpoints | Purged once the associated rate-limit window is stale (within 180 days) |
| Aggregate page-view counts, with an approximate city/country derived from your IP address at the moment of the visit | Traffic monitoring (e.g. which regions we're reaching) | Your IP address itself is never stored — only the resulting city/country and a same-day count are kept, aggregated with other visitors, indefinitely |
| When a signed-in account downloads or activates the desktop app, or uses the installed web app (with the device type, e.g. "iPhone") | Knowing which customers have the desktop app or installed app, so support and update notices reach the right people | Kept under the same retention as other account logs, and erased if you delete your account |
| The approximate city worked out from your IP address when you open Horary and have no saved place | Pre-filling the place field on Horary so you do not have to type it | Not stored and never shared: it is used for that one page view only, and the IP address itself is never kept |
| A random, anonymous ID stored in your browser's local storage (not a cookie, not linked to your account, name, or IP) | Distinguishing "unique visitors" from repeat page views in aggregate traffic statistics | Kept in your browser until you clear site data; server-side, only how many distinct anonymous IDs were seen per day is kept, aggregated with other visitors, indefinitely |
We do not sell your personal data to anyone.
As a data principal under the DPDP Act, you can:
If you have a complaint about how your personal data is handled, contact:
Email: support@kpstellarastro.com
We aim to acknowledge grievances within 7 days and resolve them within 30 days.
Passwords are hashed, never stored in plain text. Payment card/UPI details are handled entirely by Razorpay — they never reach our servers. Admin credentials and API keys are kept server-side only.
If this policy changes materially, we'll update the "Last updated" date above. Continued use of the app after a change means you accept the revised policy.