Privacy Policy

Who is responsible

Astperia is operated by Astperia. If you have a question about your data, or want to exercise any of the rights below, contact privacy@astperia.com.

If you are in the EU or UK, you also have the right to complain to your national data protection authority.

What we collect

Only what the product needs to produce a reading. There is no tracking pixel, no advertising network, and nothing is sold or shared for marketing.

• Birth data: the name you enter, your birth date, birth time, birth city and country, and the coordinates and timezone resolved from that city. This is the input to every chart and reading.
• Account data: your email address and authentication identifiers, held by our login provider.
• Billing data: a customer and subscription identifier, plan, and status. Card details are entered on the payment provider's page and never reach our servers.
• Derived data: your natal chart, the activations calculated from it, and the interpretations generated for them.
• Usage counts: how many interpretations you generated on a given day, so plan limits can be applied.

Why we hold it

Birth data is processed to perform the contract you enter when you create a chart — it is the service. Billing data is processed to take payment and to apply your plan. Account data is processed to sign you in and keep your data yours.

Precise birth data can be revealing, so we treat it as sensitive whether or not the law strictly requires it. By entering it you consent to it being used to generate your readings, and you can withdraw that consent at any time by deleting your account.

Who else processes it

We use a small number of providers to run the service. Each processes data only on our instructions.

• Convex — the database holding your chart, activations, interpretations and subscription record.
• Clerk — authentication, holding your email and sign-in credentials.
• Stripe — payments and subscription management. Stripe holds your card details; we do not.
• Our own astrology service — receives birth data to calculate a chart, and stores none of it.
• Google Gemini — receives chart-derived astrological facts to write interpretation text. It does not receive your name, birth time, birth place or coordinates.
• Vercel — hosting, and cookieless analytics that counts page views without profiling visitors.
• Sentry — error reporting. It is configured not to collect request bodies, cookies or user identifiers, so birth data does not reach it.

How long we keep it

Your chart and readings are kept while your account exists, because they are what the product shows you. Delete your account and they go with it.

Deleting your account erases your user record, natal chart, activations, interpretations, usage counts and subscription record. This is immediate and cannot be undone. The shared catalogue of astronomical events is not personal data and is not affected.

Deleting your account does not cancel a paid subscription at the payment provider. Cancel the subscription first, or contact us.

Your rights

You can access, correct, export or erase your data. Erasure is available to you directly in settings — you do not need to ask us, and no one else can trigger it for your account.

You can also object to or restrict processing, and ask for your data in a portable form. Write to privacy@astperia.com and we will answer within a month.

Cookies

Astperia sets only cookies it needs to function: one remembering your language, and your sign-in session. There is no advertising or cross-site tracking cookie, and our analytics is cookieless — which is why you are not asked to accept anything.

Security

Birth data is never written to our logs — the logger strips it. Our astrology service requires an API key, rate limits every caller, and keeps an audit trail that records who called what, never the contents of a request.

No system is perfect. If you believe you have found a vulnerability, please contact privacy@astperia.com before disclosing it publicly.

Changes

If this policy changes materially we will say so in the app before the change takes effect. The date at the top always reflects the current version.