Skip to content
AIKundliJyotish

Privacy · live customer boundary

Personal by nature. Private by design.

The live customer boundary includes authenticated accounts, canonical birth profiles and saved reading requests in one protected customer journey.

What AIKundli stores

Your protected email identity, session records, confirmed canonical birth profile and the reading requests you choose to save.

Where the boundary sits

Customer records remain in a private database schema behind authenticated server-side gateways, with no direct public, anonymous or signed-in browser table privileges.

Qualified processing only

Saved birth details are not silently sent to an unapproved calculation, language-model or payment provider. If qualified evidence is unavailable, AIKundli does not fabricate a personal result.

When an AI helps write your reading

Your chart is calculated entirely inside AIKundli, and every judgement in your reading — the answer, the timing, the remedies — is made by our own engine.

To put that reading into plain language, AIKundli may send an external AI provider (Anthropic or OpenRouter, depending on the server configuration) your question and the findings the engine has already produced: the verdict, the planet ruling the relevant house, the house numbers, the periods identified, and any remedies judged eligible.

This narration path excludes your name, birth date, birth time, birth place and CV. Your question may itself contain personal information, so avoid including names, contact details or other sensitive information. The provider receives the question and computed findings. A separate broader synthesis path must remain disabled unless specifically authorised and disclosed; it can include birth details and CV text.

The AI is not permitted to decide anything. It may only re-word what the engine already concluded. If it adds a date, a remedy or a promise the engine did not produce, its work is discarded automatically and you read the engine's own words instead. If the provider is unavailable, your reading is produced exactly as it would be otherwise.

Retention and deletion

Profile and reading records remain while the account is active. Verified deletion removes the live account and its linked customer records under the controlled deletion lifecycle.

Security controls

PIN access, same-origin mutation controls and bounded request bodies protect the journey. Every reading creation has a server-side abuse budget.