Privacy
Short version: the calculators themselves store nothing. Using them needs an account, which holds your email and the birth details you gave once; the panchang needs none. An account can be erased in one step, and nothing about you is kept anywhere else.
The calculators store nothing
A calculator reads your chart, computes the page and keeps nothing of its own. The chart itself is the one kept on your account, computed once from the details you gave at sign-up. There is no database behind any calculator and no analytics script — every page is served as plain HTML with scripting disabled by policy. If you have not made an account there is no cookie either.
Signed in, your birth details never enter a page address: each page reads the chart kept on your account. Where details do sit in an address — the panchang, or a link someone shares — three protections are set on the result:
- Referrer-Policy: no-referrer — without it, a click on any outbound link would hand your birth date, time and place to that site in the
Refererheader. - Cache-Control: no-store — keeps result pages out of shared caches and proxies.
- noindex on result pages, so a chart computed from your birth details does not end up in a search index.
Server logs have query strings stripped before they are written, so the birth details do not survive in them either.
The questionnaire, if you choose to answer it
It is the only thing here that stores anything, and it is switched off entirely unless the deployment enables it. When it is on, a submission stores exactly this:
| Stored | Why |
|---|---|
| Your answers | the point of the exercise |
| Your birth year | a timing rule is scored against the share of a life its window covers, and that depends on how much life there is. The year only — not the date, time or place |
| A chart reference | a checksum of the chart, used to tell responses apart |
| Which rules fired | the rules that did not fire are the entire denominator of the comparison; a chart cannot be recomputed from a checksum, so this is recorded at submission |
| The date of submission | — |
The chart reference is not anonymous. It is derived from birth data and can be recomputed by anyone who holds the same birth details, so we treat it as personal data throughout. Calling it anonymous would be exactly the kind of claim this page exists to avoid.
The ledger, if you join the cohort by invitation
A cohort round is a separate, invited study: you answer whether a rule's predicted window happened, and how you answer a window it did not predict. The claim itself is not stored — it is reproducible from your chart reference, the rule and the corpus checksum — so what is kept below is the answer and enough bookkeeping to score it, nothing about who you are beyond what the rest of this page already covers.
| Stored | Why |
|---|---|
| The ledger: one row per answer — which rule, the window it was about, what kind of question it was, your answer, the date, and which sitting it belongs to | reproducible from the chart and the corpus, so scoring can be checked by anyone holding the same birth details without trusting a private log we control |
| The sitting itself: a shuffle seed, how many questions, and how long it took | kept so the exact set of questions can be reconstructed later without storing the questions themselves a second time |
| Which questions you were asked, and in what order | the server's own record of what it asked, written once and never rewritten, so a check cannot be told from a real question by anything the page sends back |
| Whether you were flagged, and which criteria fired | computed once at submission from the checks above, and re-computable later from the same stored answers, so a flag can be explained rather than just shown |
| Your invitation: its label, when it was minted, when it was used | the token's own hash IS the row's key, and stays there: that is what stops a spent invitation minting a second account. The label lets the round tell its invitations apart. This row keeps its own clock — 36 months from the day it was minted, not from anything you did — because unlike everything else here, nothing about it depends on you ever answering. |
Joining is by invitation only. More than half of what you are asked is a check on the questionnaire itself, not a question about your chart — a window your chart made no claim about, one event asked twice in different words, a question whose answer is already known. You cannot tell which is which, and that is deliberate. Every answer is kept, including a check's; a check is never scored as a prediction.
A set of answers may be set aside from scoring by a written criterion applied to the answers themselves — never by a judgement about you. You are not told whether yours were set aside. Nothing is deleted for this: a later analysis may re-score with a different rule, so the answers stay.
Your answers, the questions you were issued, any flag, and the sitting itself are erased together by the one-time code the sitting gave you — the same route a questionnaire response uses — but not the invitation that let you in, which keeps its own record (see above). Forget me on the account page reaches an unfinished sitting only, deleting it outright, questions and flag with it; a finished sitting is not touched by forgetting your account — its answers are this study's data and stay, only unlinked from the account, so the code above remains the one way to erase them. Every row the code can reach is erased 36 months after you started that sitting, whether or not you still hold the code.
Proof of an answer — a document backing a yes — is not collected on this deployment. Nothing described on this page holds one.
Accounts, if you choose to make one
Everything above works without one, and an account is never required to compute a chart. What it buys is coming back — saved charts, and a ledger that accumulates across visits instead of resetting.
It costs something real, and this is the page that has to say so. Every other surface here is pseudonymous: a chart reference identifies a chart, not a person. An email address identifies a person directly. Making an account is the one action on this site that moves you from the first category to the second.
| Stored | Why |
|---|---|
| Your email address | the only way to send you a sign-in link, and the only way we could warn you about a breach |
| The parts of life you said bring you here, if you chose any | to put those first in your own reading. It changes the order and nothing else, and is not put into the anonymous record of answers |
| A password, generated for you and sent in the mail that opened your account | kept only as a hash we cannot reverse, so you can sign in without a link; with a count of failed attempts, which holds the account for fifteen minutes after five |
| Your name, and whether you read as a practitioner | to address the reading to you, and to choose which view you are shown. Neither is put into the anonymous record of answers |
| Charts you save, with the birth place, date and time that make them | the point of the account: a kept chart reopens as today's live reading without you re-entering it. This is the only place on the site that stores birth details. Erasing the account erases them |
| The people you keep beside you, with the birth place, date and time you typed for each | to show their running periods beside yours. We hold no address, no email and nothing else that could reach them, and we never contact them. They are erased when your account is, in the same step — and nothing is shown at all for anyone under eighteen. |
| A session cookie | so a signed-in browser stays signed in. Strictly necessary for the account to work; it is not used for analytics, tracking or advertising, and it is set only after you sign in |
| Your email and what you typed at the start page, until you open the link we email | held under the link and no account, and only for as long as the link works; opening the link makes your account and deletes this, because until then we cannot know the address is yours. A link nobody opens leaves nothing behind |
| Whether you asked for the one email | so we send it only to people who turned it on; turning it off deletes this |
| Which pratyantardasha turns we already emailed you about | so each turn is announced once and never again |
| The claims your reading made | each one stored before it can be answered, under a keyed code for the chart and never your name or birth details in the clear |
| Your answers, without an account attached | how we learn whether a rule holds; if you leave, these stay with every link to you removed |
| Your answers under your account | so you can see your own record; deleted when you withdraw or delete your account |
| That you agreed to a record under your account | with the date and the wording you agreed to |
| Your life events, if you record any | dated moments with an optional private note, kept under your account alone; never written into the shared record by name, and deleted with the account |
| Whether you chose to include health in your life events | off unless you turn it on; turning it off deletes every health event you recorded |
| Your answer when we asked whether something we predicted had happened | which claim we asked about, when we asked, your answer, the date you gave if you gave one, and when you answered; kept under your account alone and deleted with it |
| What you marked about a line of your reading | which rule, which day, and which of the two choices, under your account's code; we count the marks per rule to find the lines that need rewording, and a mark you undo is deleted |
| That you said a line's Hindi was not right | which line, which page and which day, under your account's code (or no code, signed out); no words of yours — we read the line again and fix it |
| Which chapter turns and which weeks we already emailed you about, and every email sent, by kind and date | so a turn is announced once, a week is asked about once, and the caps — two a month for a member — are counted rather than promised |
| The one-tap links inside an email, as hashes, and the lines the site showed you on Today and Timing, by rule and day | a link works once and for fourteen days, and does one thing; the shown lines are what the weekly check-in asks about — not a record of your visits, and never joined to your answers |
| Hashes of sign-in links | never the links themselves — a database dump must not hand anyone a working credential |
The password is kept only as a hash, so a copy of our database gives nobody a way in. You can change it from your own page, and changing it signs out every other device. A forgotten one is not reset — a sign-in link to the address we hold opens the account instead, and it works once.
To delete an account, sign in and use Delete my account on your own page. It removes the address, the saved charts, the life events, the sessions and any answers given while signed in. It is immediate and it is not recoverable.
Deleting a questionnaire response
The questionnaire has no account behind it, so deletion cannot be "sign in and delete". Each submission returns a one-time code. We store only a hash of that code, which means a copy of our database cannot be used to find or delete your row — and neither can we. Present the code on the questionnaire page to download or erase your response.
The cost of that design is real: a lost code is a row you cannot erase on your own. We accept it because the alternative is accounts, which would drag in identity, sessions and a far larger body of personal data in order to protect data you could simply choose not to submit. Two things limit that cost.
Everything is erased after three years, code or no code
A response is deleted automatically 36 months after it was given. That happens whether or not you still hold your code, and whether or not you ask. The window is set by what the data is for: a timing claim can take two years to come due, and erasing sooner would destroy the answer before it could be scored. After that the purpose is served, so the data goes.
Reaching us
For access, correction, erasure or a complaint about how your data has been handled, write to myastroreading.live@gmail.com. This channel is the reason the questionnaire will not run at all unless it is published. If you hold an account you can also do all of it yourself from the account page, without writing to anyone.
If there were a breach
We would post a notice on every page of this site, and it would stay up until the matter was closed. Unlike an email, a banner is public, dated and checkable by anyone. If you hold an account we would also email you — that is the one thing an account makes possible that was not possible before, and it is the only use of your address other than sending sign-in links.
What could be exposed is bounded by what is kept. From the questionnaire: a checksum of a chart, a birth year, answers and yes/no outcomes. From accounts: an email address and the charts saved under it. No name, no postal address, no payment details, no password, and no birth date, time or place except in a chart you chose to save.
Third parties
Place names and coordinates come from GeoNames under CC-BY 4.0, bundled with the service. No page fetches anything from a third party while you use it: no fonts, scripts, analytics or trackers.
This site is hosted by Fly.io. Its servers receive every request in order to deliver it, including the birth details in a result page's address, so Fly.io is a processor acting on our behalf, and the one third party that does see a visit.
The data is stored on servers in Singapore, which is outside India.
Sign-in links are sent through Resend, which receives the email address of anyone who asks for a link, in order to deliver it. It is a processor acting on our behalf.