Privacy

Guest birth date, birth time, selected birthplace, coordinates, and timezone are used in the browser to calculate a chart. Guest chart results are not saved as birth profiles by the application.

Birthplace search terms are sent to the site’s geocoding route, which uses the Open-Meteo Geocoding API. Geocoding responses provide location labels, coordinates, and timezone information.

When an enhanced natal interpretation is requested, structured chart facts and deterministic authoring material are sent to the application backend and may be processed by OpenAI to compose prose. The chart calculations remain authoritative, and deterministic fallback content is available if enhanced prose cannot be used.

Compatibility and synastry requests similarly send deterministic two-chart composition material and chart-position data to the backend and may be processed by OpenAI. Optional display names are used in the browser to label the reading and are not part of the interpretation request or semantic cache identity.

Accounts store an email address, display name, password hash, and creation information. Authentication uses a session token that may be carried in an HTTP-only cookie. Server-side session records can include expiry information, user-agent information, and an IP address.

Saved birth profiles store the profile label, birth date, birth time, birthplace label, coordinates, timezone, geocoding identifiers where available, and limited raw location input. Profiles are scoped to the authenticated account. Individual profiles can be edited or deleted from the account page.

For privacy enquiries, account-data enquiries, or requests and questions relating to personal information, email [email protected].

Accepted synastry prose can be cached with a deterministic chart-pair and version identity so equivalent requests can reuse it. The cache excludes account IDs, saved-profile IDs, names, email addresses, usernames, and display labels from its identity. Generic horoscope prose also uses a non-personalized cache.

The application does not currently provide a self-service account deletion workflow or publish fixed retention periods, so this notice does not claim either.

Advertising is not currently active. No real Google AdSense publisher configuration is enabled, and the application does not currently load an active advertising placement without separately validated publisher and ad-unit configuration.

This application has not implemented a custom consent management platform and does not create, store, or fabricate IAB consent strings or Google CMP state.

If advertising is activated, the site may use Google AdSense through manual display units. Google and approved advertising partners may process information and use technologies such as cookies or similar storage or access mechanisms, subject to the final regional, advertising, and consent configuration.

Where required, the launch configuration must use a Google-certified consent management platform. The intended first option is Google AdSense Privacy & Messaging European regulations messages, subject to actual AdSense account availability, current official integration requirements, and final configuration.

Applicable users may be offered choices concerning advertising and related data processing. Once the live certified CMP is enabled, its working controls must allow applicable users to revisit or revoke their choices. No non-functional consent or revocation control is displayed before that integration exists.

Birth Chart and Natal pages, Compatibility and Synastry pages, account and authentication pages, saved-profile states, and legal pages remain outside the advertising surface under the current product architecture.

Birth data, birthplace coordinates, account or saved-profile identifiers, chart facts, interpretation prose, and compatibility material are not inserted into advertising or consent configuration. Consent state cannot make an otherwise ad-ineligible route or personalized state eligible for advertising.

This boundary does not claim that Google can never receive information anywhere on the site after future advertising activation. Any live advertising processing will depend on the final Google-side and certified-CMP configuration described in this notice.