Privacy policy
Draft. This text is not in force yet. Legal counsel reviews it before the public launch.
Last updated: [date of publication]. Version: [version].
Your birth details are personal. This policy tells you, in plain words, what we collect, why, where it goes, how long we keep it, and how you control it.
If a word in this policy is not clear, write to us at [privacy email]. We answer in simple language.
1. Who we are
Love Nakshatra is a service of [Company name], a company registered in [Country of registration].
- Registered address: [Registered address], free zone [Free zone], licence number [Licence number]
- Website: [domain]
- Contact for privacy questions: [privacy contact name or role], [privacy email]
Under the Digital Personal Data Protection Act, 2023 (DPDP Act), we are the Data Fiduciary. That means we decide why and how your personal data is used. The DPDP Act applies to us because we offer our service to people in India, even though our company is outside India.
2. The short version
- We use your data to make your readings and run your account. We do not sell it.
- No other member sees your full birth date, time or place.
- Software calculates your chart. A rules engine picks text that people wrote. No AI writes your reading.
- We show no advertising and set no advertising or tracking cookie today.
- You can delete your account at any time in Settings. Deletion erases your data from our database at once.
3. What we collect and why
| What we collect | When | Why we need it |
|---|---|---|
| Your email address | Sign-up | To send your sign-in code, to identify your account, and to contact you about your account. |
| Your date of birth | Sign-up | To check that you are 18 or older. The birth date that you type on the landing screen is your account date of birth. If you change your birth details later, we check 18+ again, and your account date of birth does not change. |
| The time we confirmed you are an adult | Sign-up | To show that the age check took place. |
| Your birth date, birth time and birth place | Birth details screen | To calculate your chart. Without all three, we cannot make an accurate reading. |
| Your gender (woman or man) | Birth details screen | To select the reading text written for you, and later to calculate Guna Milan, which counts from the woman's and the man's Nakshatra. |
| Data we work out from your birth place | Birth details screen | The latitude, longitude and time zone of the place, and the time offset that applied on your birth date. The chart needs them. |
| Your chart | After you save your birth details | The positions we calculate (for example your Moon sign, Nakshatra, Pada and Lagna). Your readings come from it. |
| Your consent record | When you tick the consent box | The version of the notice you saw, its language and the time you agreed. The law asks us to be able to prove your consent. |
| Session record | Each time you sign in | A random session key and its expiry, so you stay signed in. It can also hold your IP address and your browser type, for security. |
| Sign-in code record | When you ask for a code | Your email and a scrambled (hashed) form of the code, for up to [5] minutes, so we can check the code you type. |
| Code send counter | When you ask for a code | A scrambled (hashed) form of your email and the time of each send, so nobody can flood your inbox or guess your code. |
| Anonymous usage events | When you use the site | Which screens are opened and which steps are completed, with a random id. These events hold no email and no birth details. |
What we do not collect: your name, phone number, photo, contacts, location from your phone, or payment card details. We do not ask about religion, caste or health.
The consent notice you see
Before we store your birth details, we show you this notice. The box is not ticked for you.
To make your reading, Love Nakshatra ([Company name]) will use: your email; your gender; your birth date, time and place; and the chart we calculate from them. We use this data only to create your readings and run your account. We do not show your full birth details to other users. Tick the box to agree. You can withdraw consent or ask us to erase your data at any time at [Settings > Privacy] or at [email]. Questions and complaints: [contact person, email]. If we do not resolve a complaint, you can complain to the Data Protection Board of India at [Board link].
4. Adults only
Love Nakshatra is only for people who have completed 18 years.
At sign-up, you enter your date of birth. If you have not completed 18 years, we stop there. We do not create an account, we do not send a code, and we do not store your email or your date of birth.
If we learn that a person under 18 has an account, we delete the account and its data.
5. How your reading is made
Your birth details go into a calculation engine (Swiss Ephemeris). It calculates the positions in your chart. A rules engine then selects text that people wrote for each result. No AI writes your reading text, and no person reads your birth details to write it.
Your reading is traditional Vedic astrology guidance. It is not a prediction or a guarantee. The Terms of Use say more.
We make no decision about you by automatic means that has a legal effect on you.
6. Who can see your data
Other members. Today, no other member can see any of your data. When matching starts (Phase 3), other members may see the profile that you choose to fill in. They will never see your full birth date, birth time or birth place. Private messages will open only after a mutual match, when both members have expressed interest.
Our team. Only the people who run the service can open the database, and only to run, fix and protect it.
Service providers (Data Processors). We use these companies to run the service. They process your data only on our instructions.
| Provider | What it does | What data it handles |
|---|---|---|
| Cloudflare, Inc. | Runs our website (Workers), our database (D1), our page cache (R2) and our logs | All the data in section 3 |
| [Email provider] | Sends your sign-in code | Your email address and the code |
| [Payment provider] | Takes payments for Premium and Soulmate Connect | Payment records. We do not see or store your card or UPI details. |
The law. We share data with a government agency or a court only when a law of India, or another law that binds us, requires it. We check that each request is lawful and in writing.
We do not sell your data. We do not share it with advertisers or data brokers.
7. Where your data is stored
Your data is stored and processed outside India.
- Website. Cloudflare runs our code in its data centre closest to you. For most members in India, that is a data centre in India.
- Database. Our database (Cloudflare D1) has one main copy in one Cloudflare region. Cloudflare picked the region when we created the database.
- Backups. Cloudflare keeps a point-in-time history of the database for 30 days (D1 Time Travel).
- Logs. Cloudflare keeps the logs of our Worker for up to 7 days.
- Company. Our company is registered in [Country of registration]. Our team may open the data from there or from [other countries].
India does not restrict transfers to these places today. If the Government of India restricts a country, we will follow the restriction.
8. How long we keep your data
| Data | How long |
|---|---|
| Your account, date of birth, birth details, chart and consent record | Until you delete your account. |
| Session records | Until the session ends or you sign out. A session ends after [7] days without use. |
| Sign-in code records | Until the code is used or expires. A daily clean-up removes expired codes and sessions. |
| Code send counter | [24 hours] |
| Anonymous usage events | 3 months. Cloudflare Workers Analytics Engine deletes them after that. |
| Worker logs | Up to 7 days. Our rules keep birth details out of every log. |
| Database backups | 30 days after the change or deletion. |
What happens when you delete your account. We erase, at once and in one step, every row that belongs to you: your account, your email, your date of birth, your birth details, your chart, your consent record, your sessions and your sign-in codes. Copies in the 30-day database history and in the 7-day logs expire on their own. We do not restore deleted data from a backup, except to recover from a failure of the whole database.
9. Your rights and how to use them
To use a right, sign in and use Settings, or write to [privacy email] from the email address of your account. We use that email address to identify you. We do not charge for a request.
| Your right | How to use it today |
|---|---|
| See your data (DPDP Act s. 11): a summary of your data, what we do with it, and who we shared it with | Your chart shows on the birth details screen. Write to us for a full summary. |
| Correct your data (s. 12) | Enter new birth details on the birth details screen. They replace the old ones and your chart. The account date of birth does not change: it is the age statement you made at sign-up. |
| Erase your data (s. 12) | Settings > Delete your account (/settings). It erases everything at once. |
| Withdraw consent (s. 6(4)) | Delete your account, or write to us. |
| Nominate a person (s. 14): someone who uses your rights if you die or cannot act | Write to us with the name and email of the person. |
| Complain (s. 13) | Write to our Grievance Officer. See the Grievance Redressal Policy. |
| Sign out | Settings > Sign out, or Sign out on all devices. |
When you withdraw consent, we stop using your birth details and erase them. We cannot make a reading without them. Withdrawal does not make our earlier use of your data unlawful.
We answer each request within [15] days.
10. Complaints and the Data Protection Board
If you have a complaint about your data, write first to our Grievance Officer:
- [Grievance Officer name]
- [grievance email]
- [Grievance Officer address]
We acknowledge your complaint within 24 hours and resolve it within 15 days. If we do not resolve it, you can complain to the Data Protection Board of India at [Board link].
11. Cookies
A cookie is a small file that a website keeps in your browser. We use only the cookies the site needs to work. You do not need to accept them, and we show no cookie banner, because we set no optional cookie today.
| Cookie | What it does | How long it lasts | Needed? |
|---|---|---|---|
better-auth.session_token (in production it can carry the prefix __Secure-) |
Keeps you signed in. It holds a signed random key, not your email or birth details. | [7] days, renewed when you use the site. | Yes |
ln_sign_up |
Remembers your email and date of birth for 10 minutes, between the sign-up screen and the code screen. It is deleted when your code is accepted. | 10 minutes | Yes |
__Host-ln_pending |
Remembers the birth details you typed for 10 minutes, until your code creates your account. It is encrypted, so nobody can read it from your browser. | 10 minutes | Yes |
ln_ref |
Remembers which member's link brought you to the site, so we can credit the member. | 30 days | — |
No advertising or tracking cookies. We do not use Google Analytics, a Meta pixel, or any other advertising or tracking cookie today. Our anonymous usage events are counted on our server and set no cookie.
[Future advertising pixel: if we add an advertising pixel (for example the Meta pixel for Instagram ads), it will not load until you say yes. The "No" choice will be as easy and as visible as "Yes". It will never load on the birth details or reading screens, and it will never receive your email or birth details. You will be able to change your choice at any time in Settings. We will update this table before the pixel goes live. counsel: confirm the consent wording.]
12. How we protect your data
- The site uses HTTPS only.
- Sign-in uses a one-time code sent to your email. We store only a scrambled (hashed) form of the code.
- We keep birth details out of logs, web addresses, error messages and usage events.
- The page cache that all visitors share never holds your personal data.
- We limit how often a code can be requested or tried.
No system is perfectly secure. If a breach of your personal data happens, we will tell you and the Data Protection Board without delay, with what happened, what it means for you and what we are doing about it.
13. Changes to this policy
We will tell you about each important change by email or on the site before it takes effect. If a change needs your consent, we will ask again. We also remind every member of this policy and our terms at least once a year.
14. Languages
This policy is in English.
15. Which law applies
Until 13 May 2027, the Information Technology Act, 2000 and its rules on personal data apply. From 13 May 2027, the Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025 apply. We already follow the 2023 Act and the 2025 Rules where we can.