Your information deserves care.

Aggregate page-view measurement

When activated, our own server records public page-load totals by UTC day. This is not a count of unique people; refreshes and some automated traffic may count. No historical total is invented. No advertising tracker, fingerprint, analytics cookie, IP address or browser user agent is stored in these metric tables. Random per-page event IDs are hashed only to prevent duplicate counting and expire after two days. Private account and owner pages are excluded.

Browsing and service visitors

We do not use advertising trackers. Website service entry records your supplied name, email, mobile number, consent and a random visitor ID on Hostinger. These contact details are unverified; they do not establish ownership or grant access to an existing account. The secure browser session lasts up to seven days. Signing out or losing this session does not provide automatic recovery by typing an email or phone number. Existing password accounts remain separate.

Google sign-in

If you choose Google sign-in, we receive your verified email address, display name and a Google account identifier to create or recognise your account. Google authenticates you; we do not receive your Google password or request access to your Gmail messages. Account identity is stored on Hostinger. Sign-in uses secure cookies and encrypted, single-use verification records that expire after ten minutes. Google confirms your email, not your supplied mobile number. Existing accounts are not automatically merged by matching contact details. Customer Google sign-in does not grant private owner access.

Public chatbot

Website and Telegram messages are processed by an isolated Hermes agent using the owner’s local model. Telegram service records your Telegram sender ID and supplied display name. Website and Telegram have separate service visitor identities until you explicitly link them. We retain recent questions and answers for conversation context and clear completed queue records after one day when the worker runs. Account, consent, usage and separate operational or local Hermes records may remain for support and accounting. Telegram has its own retention policy. Payments remain inactive; WhatsApp and Instagram access is limited to the configured service.

WhatsApp and Instagram service usage

Public WhatsApp and Instagram service chats use separate local conversation records. For private owner monitoring, a random channel-specific ID, activity timestamps, incoming-message and reply counts, delivery outcomes and measured engine processing time are copied to our Hostinger database. This monitoring copy contains no chat text, social password or owner-bot conversation. Older retained replies are shown as partial history without invented timing. These channel IDs do not automatically link to a website account. Instagram messages pass through Meta and our hosted encrypted relay before local processing. Deleting local conversation history does not automatically delete operational usage counters; contact us for a data request. Opening or following a social profile does not sign you into the website.

Verified membership and linked channels

When the verified-account service is activated, you can join using a website account with a verified email or verified phone and explicitly pair a supported messaging channel. Email verification alone does not prove ownership of a WhatsApp number. Pairing requires a short-lived link, proof from the channel and a one-time code confirmed in your signed-in website session. Your membership and reply allowance are shared; conversation context stays separate by account, channel and selected Kundali. Linked-channel messages and replies pass through our Hostinger account queue for local-model processing and follow the one-day chat retention period. Pending pairing records expire after five minutes. Channel identity mappings remain until you unlink or delete the account. Unlinking blocks new replies and removes the mapping; messages already accepted by a messaging provider cannot be recalled. Daily usage records contain bounded authorization metadata and are removed after one day. An account identifier can be cleared on account deletion while anonymous daily usage remains until that cleanup, so deletion cannot refill the service-wide allowance. An anonymous occupied service slot can remain after account deletion so deletion cannot automatically expand the initial cohort. Saved Kundalis and notes continue under the separate policy below. Instagram also retains its existing transport send cap; provider restrictions can limit availability before the shared AI allowance is exhausted.

Saved Kundalis and notes

When the personal console is enabled, saved Kundali profiles, confirmed birth details and notes or reading summaries you explicitly save stay in your account until you delete them. Each profile has its own content. You can delete individual saved reflections, delete saved profiles, or clear your own Kundali details. Generated chat replies are not automatically saved as notes. Chat context remains limited to four recent exchanges within one day. Calculated chart caches and calculation jobs expire within one day and can be regenerated from saved birth details. Expired transient content is cleaned by the console web lifecycle when its schema is configured, as well as the relevant worker. Deleting console content does not delete separate account, safety or operational records; backup and messaging-provider copies follow their own policies.

Safety records

Blocked-message records retain an account ID, reason, strike count, timestamp and one-way message/event hashes, rather than the blocked text. Warning and termination records persist across sessions and restarts for enforcement and support review. Public chat cannot erase these records or restore terminated access. Legacy anonymous service identities are unverified. When verified-account membership is enabled, access requires a verified email or phone and explicit channel pairing; customer verification does not grant owner or administrative access.

Your choices

General guidance does not require birth details. General chat does not calculate a chart from an unsupported claim. The saved-Kundali console uses the dedicated offline calculator after confirmed birth details, and AI interpretation uses verified chart facts. Do not send passwords, OTPs, tokens, payment details or identity documents. AI answers can be inaccurate. Email-link delivery and mobile verification remain separate setup steps. A Google-authenticated email is marked verified; supplied service contact details remain unverified. Customer sessions do not grant inventory or private administration access. Contact Connect@astrobaaba.com for account help or deletion requests.