An entire industry is built on collecting birth data. Ours computes the chart where you typed it and does not need the data afterwards.
Date, time and place of birth is about as identifying as personal data gets. It is a primary key for a human being: it is used to verify identity, it never changes, and it cannot be rotated after a breach the way a password can.
In this category it is also the product. Birth data is what an astrology portal collects, and everything downstream — the reports, the retargeting, the "dosha detected, remedy ₹2,100" — runs on having it.
So it is worth being precise about what happens here instead.
The chart is cast in your browser
Your birth details go into an ephemeris that is already on your device, and the positions come out on your device. Nothing is sent away to be calculated. If you switch your connection off after the page loads, the chart still casts, the dashas still compute, and the sky still moves — because none of that was ever happening somewhere else.
This is not a privacy feature bolted on. It is the cheapest architecture there is, which is why it is also the honest one: we do not pay for the servers we do not run, and we cannot leak the data we do not hold.
What is recorded, said plainly
Charts cast here are logged so the engine can be tested against real charts. That is the whole method, and we would rather say it on the welcome screen — where it is written, in the copy people actually read — than bury it in a policy.
What that log holds: the birth details, and the resulting positions. What it does not hold: your name, your email, or any account, unless you choose to sign in. And there is a real switch in You that turns it off. When it is off, nothing about the chart is sent — not a redacted version, not a count. Off means off.
Separately, and deliberately not the same thing, we keep an ordinary web log: country, city, which browser family, where the link came from. What a plain web server records anyway.
One third party, named, with a switch
Until August 2026 this section said there was no analytics script here at all. That was true, and it is not any more, so here is what changed and what did not.
Google Analytics is now on this site. In the European Economic Area and the United Kingdom you are asked before anything loads — a card, after the page has drawn, with two buttons the same size, and nothing is requested until you answer. Everywhere else it is on unless you turn it off. Either way it is the same one switch, in plain words, in the same settings as everything else — the tab marked You — on a screen you can reach from any page.
We would rather tell you that than bury it. While it is on, Google receives what any analytics receives — which page you are on, roughly which city, which browser, where you arrived from — and sets a cookie that can recognise this browser on other sites. That last part is the real cost, and it is the reason the switch is there and the reason this paragraph is written the way it is rather than as a footnote.
Turning it off is not a soft off. Consent is withdrawn, both of Google's cookies are expired on the spot, nothing further is sent for the rest of the visit, and no script is fetched at all on any later one. The setting is remembered, so off stays off — you do not have to turn it off again tomorrow.
What Google never receives, in any state: your birth date, your birth time, your coordinates, your birth place, your name, your email, your account, your Moon sign, or anything else derived from your chart. When you cast a chart it is told that a chart was cast, and nothing whatsoever about it.
So the honest version of the old list is:
- one third party, named, and stopped completely the moment you say so;
- nothing that identifies you reaches it, and nothing about your chart;
- no advertising pixel, no tag manager, no font from a CDN, no embedded widget;
- the advertising features of Google Analytics are switched off in the configuration, not merely unused — no ad cookies, no cross-device signals, no personalisation.
Everything else on the page is still fetched from nowhere but here.
The usage counts we do keep are written by our own code to our own database. Geography comes from the edge, server-side; the IP address that produced it is used for rate limiting and dropped. It is never stored, never returned, and never written to a row.
The part most companies would not print
Personal data here is protected by the database, not by the interface. Every table that holds anything personal — the charts you keep, the notebook, the usage log — is behind row-level security, so an anonymous read returns an empty list rather than a filtered page.
And there is no admin key anywhere in this system. Not in the app, not in the server functions, not in an environment variable. The escape hatch that most products keep for support tickets — the credential that reads any row — does not exist here, by design. It means some things are harder for us. It also means there is nothing to steal that would open everyone's data at once.
What you can do about it
- Turn the chart log off in You. One switch, immediate, no exit survey.
- Delete everything on this device — also in You, one button.
- Delete your account and all its data, if you made one. Actually deleted, not deactivated.
- Use it signed out entirely. The app works completely without an account. Registering only makes your charts follow you between devices.
We would rather have fewer rows and be able to describe them accurately.