Privacy Policy

This is AstroGuide's privacy policy, written in plain English. If anything is unclear, contact us through the support form.

What we collect

AstroGuide processes the following data to provide the app and operate it safely:

• Birth data — date, time (optional), and place of birth.
• Current place (optional) — approximate city or town text that you enter for place-aware readings. AstroGuide does not read GPS or request Android location permission.
• Display name — what to call you in the app.
• Journal entries — text you write yourself, on your own device.
• Account data — Google account identifier, email, and display name if you choose Sign in with Google.
• Technical data — an installation identifier, signed session token, app language/version, notification token if enabled, and purchase status/token when you use Google Play Billing.
• Usage analytics — release 1.0.1 (version code 4) enables allowlisted first-party analytics by default and lets you turn it off in Settings. Release 1.0.2 (version code 5) and later keep it off until you explicitly opt in. Because 1.0.1 may remain installed, we declare this data as collected. It covers events such as app open, screen view, paywall view, purchase outcome, and restore outcome.
• AI content reports — the content type/identifier, selected reason and up to 500 characters of optional context when you choose Report.
• Support and deletion requests — email, optional name, topic/reason, and the message you submit through the website.

We do not access precise device location, GPS, background location, contacts, photos, microphone, calendar, browsing history, or anything from your other apps. We process only the birth place and optional approximate current city/town that you type yourself.

Why we collect it

Birth data, display name, and an optional current place are used to calculate and write the reading you request. Journal entries stay local so the journal works. Account and purchase data restore your chart and entitlements across devices; Google Sign-In is required before a purchase so it can be recovered after reinstall. Notification data delivers messages you enable. Usage analytics shows which product flows work and where users stop; it never includes names, birth data, current place, journal/chat text, email, purchase tokens, URLs, or exception messages. Content reports are used for safety review and abuse prevention.

If a piece of data isn't necessary for the app to do its job, we don't ask for it.

Where it lives

Journal entries and saved partner details are stored in Android's private app storage. AstroGuide disables Android cloud backup and device transfer for all app data so deleted birth/journal data cannot return from a stale backup. Paid access is recovered through the signed Google-linked account instead.

The public support and deletion forms may keep only their temporary submission state in the current browser tab's session storage; the browser removes it when that tab session ends.

Birth data, calculated charts, generated readings, account links, notification registration, and purchase entitlement data are sent over HTTPS to our backend because those features cannot operate only on the device. Forecast caches normally expire after seven days; the optional offline analytics queue contains at most 100 allowlisted events and expires after seven days; AI content reports are retained up to 180 days; aggregate analytics up to 400 days; support-form queue records up to 90 days; and uncompleted deletion requests up to 45 days. Chart, account, notification, and entitlement records remain while the account is active or until deletion/opt-out requires removal. During erasure, an account identifier may remain in a cleanup job for up to 24 hours so delayed passes catch already-running requests. After that, only a one-way hashed session-revocation marker remains for the configured session lifetime plus one day (currently up to 91 days), preventing old signed tokens from recreating the account.

Analytics stores daily counters only. An account identifier is used transiently to calculate an irreversible, day-specific active-user estimate and is not stored as an analytics event row.

Encrypted server disaster-recovery backups are stored separately from the live system, are never used for analytics, and expire automatically within seven days. Data deleted from the live service may remain only inside those inaccessible encrypted backups until that retention period ends.

Third parties

Before AI processing: when you tap an action that requests a generated reading, the relevant data listed below is sent over HTTPS to AstroGuide's backend, then to OpenRouter and the selected model provider before any generated text can be returned. If you do not request an AI-generated feature, that AI request is not made.

We use the following external services:

• OpenRouter and the selected language-model provider — receive structured chart data and, depending on the requested feature, may receive display name, age or birth date/time/place, the approximate current city/town you entered, gender, partner profile and a question you typed. Every request asks the provider to use zero-data-retention routing and deny data collection. They do not receive your email, account id, journal entries, purchase token, notification token or analytics history.
• OpenStreetMap Nominatim — receives the birth-place search text needed to resolve coordinates for a chart.
• Google Play Billing — handles subscription purchases. They receive a purchase token; we receive a confirmation. They never see your chart.
• Google Sign-In — verifies your identity only if you choose to sign in.
• Firebase Cloud Messaging — processes a device notification token and message delivery data only if notifications are enabled.

Usage analytics is first-party: it is sent to AstroGuide's own backend and not to an advertising or analytics SDK.

We have not, do not, and will not sell your data to advertisers or data brokers.

Your rights

You can, at any time:

• Request a copy of the data linked to your signed-in email through support.
• Correct it.
• Delete it — see Account deletion.
• Choose whether to enable usage analytics, revoke that choice at any time in Settings, and turn notifications off in Settings or Android system settings.
• Restore eligible Google Play purchases after signing in with the same linked Google account.

If you live in a jurisdiction with stronger rights (GDPR, CCPA, LGPD, others), they apply.

Children

AstroGuide is intended only for adults aged 18 or older. If you are under 18, do not use the app. We do not knowingly collect personal data from anyone under 18; if we learn that we have, we delete it.

Contact

Data controller and developer: Aurelia Labs LLC, 30 N Gould St, Sheridan, WY 82801-6317, United States. Questions, requests, or complaints: support form.

This policy may change. When it does, we'll show the new effective date here and notify you in the app the next time you open it. Material changes will require fresh consent.