Privacy
Your birth date, exact time and exact place is one of the most identifying things about you, and it can never be changed. This page says precisely what happens to it.
Last updated 2 September 2026
01The short version
Astroji has no accounts and no database. Your birth details are used to compute a chart, that chart is used to answer your question, and both are gone when the request finishes. Nothing is written to disk. Nothing is written to a server you cannot see.
Your conversation lives in this browser tab and nowhere else. Close it and it is gone — including from us, because we never had it.
This is unusually simple because the product is early, not because we are being clever. When accounts arrive it will get longer, and section 08 says what will change and what will not.
02What you give us
Two things, and only when you choose to.
What you type. The question, and the recent turns of the conversation, which your browser sends back so that “what do you mean?” can resolve against the previous answer. We hold no session; the transcript belongs to your tab.
Your birth date, time and place — asked for inside the conversation, at the moment a question actually needs a chart, and not before. If you only want to know how jyotisha works, you never give us any of it.
Under the GDPR this is personal data. Under India’s DPDP Act it is personal data. We treat it as the most sensitive thing we handle, because a birth moment is a permanent identifier: you can change a password, and you cannot change when you were born.
03What we keep
Nothing. No endpoint in Astroji writes birth data anywhere. There is no user table, no chart table, no conversation log. The chart exists in memory for the length of one request and is discarded when the response is sent.
Our servers keep ordinary operational logs — timestamps, request paths, status codes, errors. Those are what tell us the site is up. They do not contain your birth details or the text of your questions.
Two specifics worth stating, because they are the ones people assume go the other way. If a message suggests you may be in crisis, we record that it happened and nothing else — not the words, not the question, not a fragment. And your birth details are never stored in your browser either: there is no cookie and no local storage holding them.
04Who else sees it
One company: Google, whose Gemini model writes the English of an answer. It is worth being exact about what it does and does not receive, because “we never share your birth details” would be the convenient sentence and not quite an honest one.
What is sent: your question; the computed chart — which grahas sit in which rashis and bhavas, and their dignities; the dates of the period being read and your age range across it; and the classical rules that matched, with their claims and rule ids.
What is not sent: your birth date, your birth time, your place of birth, its coordinates, or its timezone. None of those appear in the prompt. We verify that with a test rather than asserting it in a policy.
The honest caveat. A chart is derived from a birth moment, and the derivation is not one-way in practice: an astrologer given the positions and the age range could narrow your birth to a window of months, and with the rising sign, to a window of minutes on a known day. So while the identifiers themselves stay with us, what we send is not anonymous. Treat it as personal data, because it is.
Google’s handling of API requests is governed by its own terms. Note that Gemini’s free tier permits training on submitted content and the paid tier does not; moving to the paid tier is a launch blocker for us, and until it is done, this sentence is the warning rather than the reassurance.
There is a second, smaller one. Place-name search uses Open-Meteo’s free geocoding API, and your browser calls it directly rather than going through us. So Open-Meteo sees the town name you are typing and, as with any direct request, your IP address. It does not see your date, your time, your question, or anything that would connect the lookup to the rest of your visit — but the IP is a real disclosure and we are not going to bury it. Routing that call through our own server would remove it, and is on the list.
05What we do not do
No advertising. No ad SDKs. No third-party analytics — not Google Analytics, not a pixel, not a session recorder. No selling or sharing of anything, to anyone, at any price. No profiling, and no automated decision-making about you that has legal or similarly significant effects.
When we do add product analytics it will be a privacy-first tool that receives neither birth data nor question text, and this page will name it before it goes live.
06Your rights
The GDPR gives you access, rectification, erasure, restriction, portability and objection. India’s DPDP Act gives you access, correction, erasure, grievance redressal, and the right to nominate someone to act for you.
Today, exercising most of them is instant and needs nobody’s help: close the tab. We hold nothing about you, so there is nothing to export, correct, restrict or delete. If you would like that confirmed in writing, ask and we will confirm it.
When accounts exist, export and deletion will be buttons in the product rather than an email you have to send. That is a commitment, and it is written here so it can be held against us.
07Who to contact
Astroji is built by one person at Paper Kite Labs in Mumbai, and that person reads this inbox himself: paperkitelabs@gmail.com.
That address is also the grievance contact for the purposes of the DPDP Act. If a reply takes more than a few days, send it again — it will be an oversight rather than a policy.
08What changes when accounts arrive
Saving a chart means storing a birth moment, and that is a different product with different duties. When it happens:
Birth data will be encrypted at the field level, not merely on an encrypted disk. Consent will be asked separately from the terms, with the purpose stated at the point of collection. Export and deletion will be buttons, and deletion will mean deletion rather than a flag on a row. Retention will have a stated limit rather than being indefinite by default.
None of that is built yet, which is exactly why this page currently says we keep nothing. We would rather publish a short true policy now than a long aspirational one.