Privacy

Using the site without an account

Most of this site needs no account. Panchang, choghadiya, the dosham pages, the matching tools and the reference tables all work without signing in. When you enter birth details on those pages they are sent to our server, the chart is computed, and the answer is returned to you. Nothing about that request is written to our database. There is no account to attach it to and no record kept of it.

If you sign in

Signing in with Google gives us three things from your Google account: the identifier Google uses for you, your email address, and your display name. We ask for no other permission — the sign-in requests only "openid email profile", which is the minimum Google offers. We never receive your Google password, and we do not read your mail, contacts or calendar.

Once you have an account you can save charts — your own and those of family members you add. Each saved chart holds the label you gave it, the relationship if you set one, and the birth details themselves.

How it is stored

Every piece of personal information in the database is encrypted before it is written: your name, your email address, your phone number if you give one, and the birth details of every saved chart. The encryption is AES-256-GCM, which detects tampering as well as hiding content, and the keys live in the server's environment rather than anywhere in our code.

Your email address is also stored a second time as a keyed hash, so that signing in can find your account without decrypting every row. The hash uses a server-held key, which means a stolen copy of the database cannot be reversed by anyone who does not also hold that key.

Sessions store a hash of the session token rather than the token, the first part of your IP address rather than the whole of it, and a hash of your browser's user-agent string. That is enough to end a session that is being misused and not enough to follow you around.

How long it is kept

Each purpose has its own horizon, counted from your last activity. Withdrawing consent for a purpose stops it and removes what was held for it. Withdrawing consent for the account itself closes the account, because nothing would remain that we would be permitted to do.

Your rights

You can see what is held, correct it, and have it erased. Erasure is real deletion rather than a flag that hides a row. If you have an unspent balance when you erase your account, it is paid back rather than kept — the code has a specific path for that, because an account that costs money to close is an account nobody closes.

What we do not collect

There is no analytics script on this site, no advertising network, no social media pixel and no third-party tag of any kind. We do not sell or share personal information with anyone. We set no cookies except the ones that keep you signed in and carry a sign-in attempt from one page to the next.

Switched off in this deployment

Some parts of the product exist in the code but are switched off in this deployment, and while they are off they collect nothing at all. Payments are not enabled, so no payment information is taken or held. The AI question feature is not enabled. Nothing is sent to you by email or push notification, because no sender is configured — the consent switches for those exist, and today they govern something that does not run. This paragraph will change when that changes.

Contact

For anything on this page, including a request to see or erase what is held, write to thdofficialid@gmail.com.