Last updated: October 2026
Your most personal questions deserve real privacy. This summary explains, in plain language, what AstroSignal collects, how it is protected, and the choices you have.
To compute your chart we ask for your birth date, time, and place. To run your account we store your email address, and — if you choose to set one — a password. If you subscribe, our payment processor handles your card details; we never see or store them.
We also keep the questions you ask and the readings we generate, so your experience compounds over time and each answer can build on your actual context.
We no longer ask how you heard about us. Sign-up used to carry an optional box for it, and that box is gone. Answers people gave while it was there are kept — encrypted, like the rest — and somebody here reads them. That is what asking was for: a recommendation from a friend is the one way people find us that no analytics or advertising measurement can see. Nothing is collected this way any more.
Your birth data, the questions you ask, the interpretations and readings we generate, and anything people wrote when we still asked how they heard about us, are encrypted at rest. Our search and logging systems carry identifiers only, never your plain-text content.
A few details are kept in readable form so the service can run — your email address, so we can sign you in, and the names and labels you give your charts, so we can list and organise them. These identify your account; it is the birth details and readings attached to them that we encrypt.
When you arrive from an advertisement or a shared link, we keep what the address bar brought with you — the campaign labels, and the click identifier an ad network adds if there was one — along with the name of the site that sent you (the site, not the page you were on) and which page of ours you landed on. That is written once, beside your account, from your first visit, and a later visit never overwrites it, so we can tell which campaigns bring people who stay. Like the details above, it is kept in readable form rather than encrypted: these are labels we group and count, and counting them is all they are for.
No human astrologer or staff member reads your chart or your questions. Readings are generated automatically. The one exception is the answer described above: where somebody wrote how they heard about us, a person here reads that. It is the only thing a person reads, and it is the only reason that question was ever asked.
Your data is used to compute your chart, generate readings, answer your questions, and operate your account and subscription — and, for anyone who answered it while we still asked, to read what they told us about how they found us. We do not sell your personal data.
We do use analytics and advertising measurement to understand how people find the service and how they use it. Some of it comes from tags that run in your browser, and some of it is reported from our own server directly to the provider — and not only when someone buys. Our server reports the events listed below as well, alongside the tag in your browser, so that an event a browser setting or an ad blocker stopped is still counted.
Meta receives these events, both from the tag in your browser and from our server: which pages were visited; that a birth chart was created, with a yes or no on whether an exact birth time was given (a time you did not mark as an estimate), but never the time itself; that the free reading was shown; that a price page was viewed; that a checkout was started and that a purchase was made, each of those two with its amount and the plan it was for; and deeper engagement with a reading, meaning that it was read further, and which section of it.
We do not load Google’s analytics tag in your browser, so Google receives nothing from your browser on our pages. From our server it receives only the purchase, with its amount and its plan, a browser identifier if Google’s own tag stored one on an earlier visit, and no form of your email address, your account number or your phone number at all.
The events our server sends to Meta carry identifiers with them, so Meta can tell it is the same person who saw the ad rather than a stranger. They carry your IP address; the user-agent line your browser sends with every request, which names your browser, its version and your operating system; the identifiers the Meta tag had already stored in your browser; and the address of the page the event happened on (for a purchase, the page you started it from). That address is the page itself and nothing after it: anything after the question mark or the hash sign is removed before it is sent. When you are signed in, an event also carries three values that have been scrambled (hashed): a scrambled form of your email address, which is a one-way hash and never the address itself; a scrambled form of the number our database uses for your account, which is a number of ours and not your name or your email address; and a scrambled form of your phone number, but only if you gave one in full international format, starting with + and your country code. A phone number written any other way is not sent in any form.
A purchase also carries a marker saying how the sale came about: whether any of those identifiers were attached to it at all, and whether the buyer had redeemed an invite code. That is there so the sales we make by hand are not counted as advertising results.
Every event is also given a reference number, so that when the same event arrives from your browser and from our server it is counted once, not twice. For a birth chart, the free reading or deeper engagement with a reading, it is built from the internal id of the chart; for a checkout or a purchase, from the id our payment processor gives that checkout; for a page view or a price page, it is a random number. Google is given the same reference number for a purchase. It is a reference to the event, not to you.
They receive nothing else. Your birth date, time and place are never sent — only whether an exact time was given — and what your chart says, the questions you ask, the text of your readings, and anything written when we still asked how you heard about us, are never sent to an advertising or analytics provider either. That last one is worth saying plainly, because it is the answer most obviously about them: it stays with us and is read by us.
We use PostHog to understand how people use AstroSignal: which steps of the app they reach, such as opening the landing page, swiping through its sample cards or tapping to get started, and where they stop. PostHog receives these events from your browser only; our server sends it nothing. Each event is a fixed name with a few fixed labels: the kind of device you are on (phone, tablet or computer), the version of the app, the campaign labels from the link that first brought you here if there were any, and your type of plan once we know it.
Those events never carry your email address, your name, your phone number or your birth details. They do not carry the address of the page, the site that sent you, or anything you type. When you are signed in, the only thing that identifies you to PostHog is the internal number our database uses for your account, which is a number of ours and not your name or your email address. When you are not signed in, you are an anonymous visitor.
PostHog also makes a session recording: a replay of how the page was laid out and where you scrolled and tapped, so we can see where a page is confusing. Everything you type is hidden in your browser before the recording leaves it, on every page without exception, and so is anything the app has written about you. One thing is legible: the wording of the landing page itself, which is our own writing and reads the same for every visitor, so that we can tell which part of it you were looking at. On the Signal page, which is about you, every letter is replaced before the recording leaves your browser.
Session recording runs only on the landing page and the Signal page, and it stops when you leave them. Nothing on any other page, including this one, is recorded.
You can opt out at any time with the button at the end of this page. It switches analytics off on this device: PostHog stops, session recording included, your browser sends nothing further to Meta, and it no longer asks our server to report a page view for you. The choice is remembered in this browser until you clear its site data. Our server still reports a checkout or a purchase to Meta and Google as described above, because those come from the payment itself rather than from your browser.
We rely on a small number of service providers to operate. To generate your readings, an AI language-model provider processes your birth details and your questions; a payment processor handles billing; and infrastructure providers host the service. Each processes your data only as needed to provide its part of the service.
Meta and Google provide the advertising measurement described above, and PostHog the product analytics and session recording. What reaches Meta and Google is the event data named there — pages, a birth chart being created, a reading being shown or read further, a checkout or a purchase with its amount and its plan, and the identifiers listed above — and what reaches PostHog is what the section on session recording describes. None of them receives the content of your account.
Checkout is the one place some of those identifiers pass through somebody else on the way. The browser identifiers, your IP address, the user-agent line and the address of the page you started from are attached to the checkout before you are sent to pay, so our payment processor holds those too. The scrambled forms of your email address, your account number and your phone number are not among them — our server works those out for itself and sends them to Meta directly. Every other event goes from our server to Meta directly and never passes through the payment processor at all.
Two more providers handle email, and they receive different things, so they are worth separating. Resend delivers the messages we send you: the code that signs you in, the code for changing your password, and a family invitation if you are sent one. It receives the address the message is going to and the message itself — that is what sending an email is — and nothing beyond it.
Loops holds our mailing list, for the emails that are not something your account needs. It receives contact details only: your email address, your first and last name if you gave them, an internal id for your account, and whether you are subscribed. That is the whole of it, and the rest is worth being exact about, because it is the part people assume. Your birth date, time and place, your chart, your readings, your daily insights, your monthly forecasts, the questions you ask, the conversations they belong to, and what you wrote when we asked how you heard about us are none of them sent to Loops, or to any other email provider. They are encrypted where they are stored, and the mailing list is built from plain account fields that contain none of them.
Depending on how we have set the site up, you may be asked first, when you arrive, whether to allow analytics; if you are, nothing is measured until you agree, and declining there is the same as the button below. Either way, you can switch analytics off on this device with the control at the end of this page.
You can update your details from your account page, and you can delete your account, which removes your associated personal data.
The mailing-list emails described above are the ones you can turn off, and there are two ways to do it. Every one we send from that list carries an unsubscribe link in its footer, and opening it takes your account off the list — you do not need to sign in, and you do not need to write to us. Your account page does the same thing from the other side: it shows whether you are currently on the list, and it is where you can take yourself off or put yourself back on whenever you like.
Leaving that list does not touch the emails your account needs in order to work. The code that signs you in and the code for changing your password are not on the mailing list at all — they are sent as part of using the service, by the other provider named above — so unsubscribing has nothing to switch off there and they keep arriving. That is deliberate rather than an oversight: signing in here means receiving a code by email, so an unsubscribe that silenced those would take your account away from you. It also means there is no setting that stops them. If you would rather hear nothing from us at all, deleting your account is the way, and it is on the same page.
If you have a question about your data, contact us any time.
This page is a plain-language summary provided for transparency and is not a substitute for formal legal advice. Questions? Email hello@astrosignal.ai.