Privacy Policy

This policy explains what happens to data when you use this site. The short version: your birth data never leaves your browser, we run no birth-data database, and the only processing that happens is what a normal website needs to serve pages.

The principle: calculation stays client-side

The Human Design calculator — including the astronomical computation, the timezone resolution and the city search — runs entirely in your browser. The birth date, birth time and birth city you enter are never transmitted to our servers, never written to a database, never logged by the application, and never attached to any identifier.

The city autocomplete works from a bundled offline list shipped with the page. We do not call third-party geocoding or mapping APIs that could observe what you type.

There is nothing to request, export or delete on our side, because there is nothing stored on our side. Closing the tab erases the session completely.

Information we do process

Like any website, our servers receive standard technical request data when pages load: your IP address (as seen by the web server), the URL requested, browser user-agent, timestamp, and referrer. This is infrastructure-level logging used to serve pages, detect abuse and diagnose errors. It is not correlated with birth data — which, again, never arrives at the server.

If you create an optional account (only needed for the signed-in dashboard area, not for any chart tool), we process the account email address and authentication data described in the terms of service. Chart generation itself never requires an account, an email address, or any identifier.

Cookies and local storage

The site sets a small number of functional cookies and local-storage entries:

• Session cookies for the optional signed-in area, if you use it
• A theme preference (light/dark) so the site loads in the appearance you chose
• A language choice when you switch locales
• Standard analytics cookies only if analytics is enabled in the site configuration; when enabled, they measure aggregate page performance (pages viewed, device class, country) without any birth-data dimensions

We do not set advertising cookies, and we do not build advertising profiles. If a third-party chat or support widget is enabled in the dashboard area, it may set its own cookies; that is disclosed in the widget at launch.

Analytics

If analytics is enabled, it operates on aggregate, non-identifying data: page URLs, referrers, approximate geography from IP, and device class. Birth data is not a dimension, because birth data is never sent. Search-terms that lead people here are observed only through the referring search engine's own mechanisms, not by us recording keystrokes.

Children and sensitive contexts

The site is a general-audience tool and does not direct itself at children. Because birth data can be sensitive in context (for example, when charting a child), we minimize what exists at all: nothing typed into the calculator persists after the session. We ask adults charting minors to use only the data they are comfortable computing locally.

Third-party services

Static hosting and a CDN serve the pages. Payment providers are used only in the optional account area, if purchases exist, and process their own data under their own policies. No third party receives birth data from this site, because no birth data leaves the browser.

Data retention

• Browser-session data (birth inputs, computed charts): retained until you close or reload the tab; never persisted server-side
• Infrastructure logs: short operational retention consistent with hosting defaults
• Optional accounts: retained until you delete the account or ask for its removal

Your choices

• Use every chart tool without an account — the strongest privacy choice is built in
• Block or clear cookies at any time; the chart tools keep working
• Use the site's language and theme switches, which store only their own preference values
• For account-related requests, use the in-app support tickets

Changes to this policy

If the policy changes materially, the updated date at the top of this page changes with it, and the summary at the top will state the new behavior plainly. The client-side principle is a design commitment, not just a policy line: the architecture itself is what protects your birth data.

Contact

Questions about privacy can be raised through the channels on the contact page. For anything about account data, use the in-app ticket system so the request reaches the right context.