When you create an account we store your email address and a hashed password. If you sign in via a third-party provider (Google, GitHub) we receive only the profile fields that provider exposes to OAuth clients — typically name, email, and avatar URL.

To generate your Human Design chart we ask for your birth date, time, and place. This data is stored on our servers and associated with your account so you do not have to re-enter it. You can delete it at any time from your profile settings.

We log page views, feature interactions, and error events. Logs contain a pseudonymous session identifier, not your name or email. Raw logs are retained for 30 days and then discarded.

One-time purchases and subscriptions are processed by Stripe. We receive a transaction reference and your billing country for tax purposes. We do not store card numbers, CVV codes, or full card metadata.

Birth data is used solely to compute your chart and related readings. Account data is used to authenticate you and send transactional emails (password reset, purchase confirmation).

Aggregated, anonymised usage patterns help us understand which features are useful and where people get stuck. We do not build individual behavioural profiles or sell insights derived from your data.

We may process or disclose data when required by applicable law, court order, or to protect the rights and safety of our users.

We set a single first-party session cookie to keep you signed in. It is scoped to our domain, HTTP-only, and expires when you sign out or after 30 days of inactivity.

We do not embed advertising pixels, retargeting scripts, or social media tracking widgets. The site loads no third-party JavaScript that persists data about your visit outside of our own infrastructure.

We run a self-hosted, privacy-preserving analytics tool. It does not use cookies, does not fingerprint browsers, and does not share data with any external analytics vendor.

Data is stored on servers located in the European Union. All traffic between your browser and our servers is encrypted with TLS 1.2 or higher. Databases are encrypted at rest.

Access to production systems is restricted to a small number of engineers, protected by hardware security keys and audited access logs. Passwords are hashed with bcrypt before storage.

Active account data is retained for as long as your account exists. If you delete your account, all personal data is purged within 30 days, except where retention is required by law (e.g. financial records for tax purposes, retained for seven years).

You can request a copy of all personal data we hold about you at any time. We will provide it in a machine-readable format within 30 days.

You can update your birth data, email address, and name directly from your profile settings. If something is incorrect and you cannot fix it yourself, contact us and we will correct it promptly.

You can delete your account and all associated data from the account settings page. Deletion is permanent and irreversible. If you have an active subscription, cancel it first to avoid further billing.

If you believe we are processing your data unlawfully, or you wish to restrict processing while a complaint is resolved, contact us. EU and UK residents may lodge a complaint with their local data protection authority.

Payment processing. Stripe is a PCI DSS Level 1 certified processor. Their privacy policy is available at stripe.com/privacy.

We use a transactional email provider to deliver system emails. Your email address is passed to them only for the purpose of delivering that specific message.

We do not sell, rent, or trade personal data to any third party for marketing or commercial purposes, under any circumstances.

This service is not directed at children under 16. We do not knowingly collect data from anyone under 16. If you believe a child has created an account, contact us and we will delete it immediately.

We will notify registered users by email at least 14 days before any material change to this policy takes effect. Continued use of the service after that date constitutes acceptance of the updated policy. The date at the top of this page always reflects when it was last revised.