How can I verify that my birth details are not sent anywhere?

Open your browser’s developer tools, switch to the Network tab, and complete the quiz. You will see the astronomy engine being downloaded, and requests to Google Analytics carrying the page address, and no request carrying your birth data, because none is made.

Only outside the EEA, the UK and Switzerland, and only one: the Google Analytics cookie that lets two visits from the same browser be counted as one person. Inside those regions consent defaults to denied and no cookie is set at all, which is why the site has no consent banner. The calculator sets no cookie of its own anywhere. It does use browser storage: your answers sit in session storage while you are using it, and the browser empties that when the tab closes; a payment reference goes into local storage after a purchase, so the reading you paid for is still there when you return.

Privacy

Your birth date, time and place are processed on your own device and never sent anywhere. This page explains exactly what that means and what else the site does.

Birth details

What you type into the calculator — your name, date, time and country of birth — stays in your browser’s memory for the length of your visit and is not transmitted to any server. The astronomy engine is downloaded to your device and runs there.

While you are working through the calculator your answers are held in your browser’s session storage, so that a reload — or a step out to your bank and back during payment — does not lose them. Session storage is emptied by the browser when the tab is closed. None of it is written to a cookie, and none of it is transmitted: the analytics described below never sees any of it, because there is nothing for it to see.

There is no account to create. The free calculator asks for no email address; buying a reading does, and that is handled entirely by the payment processor described below.

Third parties

Two. Google runs on every page: the site loads Google Tag Manager, which loads Google Analytics, and that tells us which pages people reach and roughly where they came from. Google receives the address of the page you are on, the page you arrived from, your approximate location derived from your IP address, and basic device and browser information.

Whop runs only if you open the checkout, and is described in the next section. Nothing of it is loaded on a page you merely read.

It does not receive your birth details. Those are never transmitted to any server, so there is nothing for analytics to collect, and no page address on this site contains them.

There is nothing else. Fonts are served from this domain rather than a font CDN, and there are no advertising, social or heat-mapping pixels.

Payment

Readings are sold through Whop, which runs the checkout and handles the money. The payment form is served by Whop inside a frame on this page: card details are typed into Whop’s form, on Whop’s systems, and never reach this site. We could not read them if we wanted to, and no code here tries.

Whop receives what taking a payment requires — your email address, your card or wallet details, your IP address and the amount. It is told nothing about your chart. No birth date, birth time, place or reading text is included in anything sent to it, because the checkout is opened with a price and nothing else. This is a deliberate limit on the integration, not an omission.

When a payment succeeds, this browser keeps the payment reference in local storage so that the reading you paid for is still unlocked if you close the tab and come back. It is a transaction id and nothing else, it stays on your device, and clearing your site data removes it along with the unlock.

Somebody else’s birth details

The reading can be read against another person’s chart. Those details belong to somebody who has not visited this site and has agreed to nothing, so they are held to a stricter rule than your own: they are used to work out a chart in your browser and are never written down at all, not to a cookie, not to local storage, not to session storage. Reloading the page loses them, which is intended rather than a limitation.

They are not transmitted anywhere either, for the same reason nothing else in the calculator is: the astronomy runs on your device.

Whether analytics sets a cookie depends on where you are. If you are in the EEA, the UK or Switzerland, consent defaults to denied and Google Analytics runs without storage: no cookie is set, and measurement is aggregate and modelled rather than tied to a returning visitor.

Everywhere else, consent defaults to granted and Google Analytics sets its usual cookie so that two visits from the same browser can be counted as one person rather than two.

There is no consent banner, and that is the reason there is no cookie to ask you about in the regions where asking would be required.

Server logs

The site is served as static files by a hosting provider, which keeps standard request logs — IP address, timestamp, the page requested, user agent — as every web server does. Those logs are the hosting provider’s and are used to serve and protect the site.

They contain no birth details, because birth details never reach a server to be logged.

Changes to this page

This page is updated before a change goes live, not after it. The most recent change added the payment section above, when checkout was switched on, and rewrote what the birth-details section says about storage.

Common questions

How can I verify that my birth details are not sent anywhere?: Open your browser’s developer tools, switch to the Network tab, and complete the quiz. You will see the astronomy engine being downloaded, and requests to Google Analytics carrying the page address, and no request carrying your birth data, because none is made.
Do you use cookies?: Only outside the EEA, the UK and Switzerland, and only one: the Google Analytics cookie that lets two visits from the same browser be counted as one person. Inside those regions consent defaults to denied and no cookie is set at all, which is why the site has no consent banner. The calculator sets no cookie of its own anywhere. It does use browser storage: your answers sit in session storage while you are using it, and the browser empties that when the tab closes; a payment reference goes into local storage after a purchase, so the reading you paid for is still there when you return.