Privacy at Astrae
This notice describes the information handled by the Astrae application as currently implemented. The operator of each deployment is responsible for keeping this notice accurate for its services and location.
Information stored
Astrae stores the account email and password hash, session records, saved birth profiles and calculated charts, reports, AI conversation messages, tarot readings, compatibility readings, and notifications when you use those features. Birth details can include date, time, place, coordinates, and time zone. Payment records may be stored when a billing provider is added.
How the service uses it
Account and chart information is used to provide the features you request, secure the service, and support your account. Private reports are searchable only by the account that created them. Birth data and private chart content are not included in public search results.
Local calculation and AI
Astrology calculations run in the locally hosted Swiss Ephemeris service. AI interpretations run through the locally hosted Ollama service. Astrae does not send birth data to an external astrology or AI API. Email verification and password-reset messages are sent through the SMTP service configured by the site operator, which may be a separate provider.
Cookies and operational records
Astrae uses an HttpOnly session cookie to keep you signed in. Operational and administrator audit records may be retained for service security and troubleshooting. The operator should configure access controls and log retention for the deployment.
Export and deletion
Signed-in users can download an account data export and permanently delete their account from My space after confirming their password. Deletion removes the account and related records from the live application database, except audit metadata whose user reference is retained separately. Backup copies follow the site operator’s configured backup and retention schedule.
Your choices and operator
You can avoid saving birth details by using features that do not require a saved chart. For questions about this specific deployment, contact its operator; the deployment owner is responsible for providing applicable regional privacy notices and contact details.