Privacy

Accounts are optional. Everything works without signing in, with all data kept on your device. An invite-only Google sign-in exists for syncing saved profiles and account defaults across devices.

If you sign in (currently invite-only), your saved profiles and preferences sync to the server so they follow you across devices. Profiles store only a label plus the derived bird — or nakshatra and paksha. Account defaults may store language, theme, default bird, and a default location you chose. Raw birth date, time, and event-specific coordinates are never stored on the server, signed in or not.

Birth details and precise location you enter are used only to compute the result you asked for. They are never stored on the server, never written to logs, never sent to analytics, and never included in a shareable link.

If you use "Use my location," your coordinates are read by your browser after you explicitly grant permission and resolved to a timezone on your device. To show a readable place name instead of a generic label, those coordinates are also sent to OpenStreetMap's Nominatim service to look up a name — this only happens after your click, and only for that lookup; if it fails, a generic label is shown instead. Searching for a place by name sends only the text you typed to a different geocoding service (Open-Meteo), never your device's location.

If you enable period alerts, our server stores this device's push address, your bird (or nakshatra and paksha), a location rounded to roughly 1 km, and your alert settings — never your birth date, time or exact coordinates. Disabling alerts deletes all of it immediately.

What's stored in your browser

Only non-sensitive preferences are saved locally on your device: your chosen language, light/dark theme, last-selected bird, a short list of recent locations, and the last successfully calculated schedule (so it can be shown while offline). None of this is birth date, birth time, or precise coordinates tied to a real event.