Privacy Policy

01What this policy covers

This policy explains what VedicSense collects when you use the site, what it is used for, who can see it, how long it is kept, and how to reach us about it. It is published under section 43A of the Information Technology Act 2000 and the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules 2011, and is written to meet the notice requirements of the Digital Personal Data Protection Act 2023 and the rules made under it.

VedicSense is operated by Vyora Online LLP, which is the data fiduciary for everything described here. The entity details are at the end of this page.

02What you give us, and what we do with it

Every calculator works without an account, a sign-up or a payment. If you do not open an account, the only personal data you give us is what you type into a calculator:

• A name, if you choose to enter one, used only to label the chart you see.
• A date, time and place of birth, used to compute the chart, panchang, dasha or match you asked for.
• A mobile number or business name on the numerology tools, used only to compute the digit or letter total shown to you.

These details are used for that one calculation, at that moment. They are not written to a database, not linked to you, not used to build a profile, and not used for any purpose other than returning the page you asked for. Once the page is served, the values exist only in your browser.

03What the server records on its own

Like every web server, ours writes a technical log of each request: the IP address the request came from, the time, the page requested, the browser identification string and the response code. Form values you submit are not written to this log.

The log exists to keep the site running and to detect abuse. It is kept for no more than 30 days and then deleted automatically. It is not analysed for marketing and not shared with advertisers.

04Accounts and saved births

You can use every calculator without an account. If you create one, we keep your email address, the name you give, a one-way hash of your password, and the birth details you choose to save: a label, the relation, the name on the chart, the date, time and place of birth and its coordinates. Nothing is saved to an account unless you choose to save it: the Save button on a chart, or the “Save this chart” box when you create an account or sign in to download a PDF. Charts you only view are not kept.

Saved births exist so you can open them again in any tool. They are never used to profile you, never shown to anyone else, never sold, and never used for marketing. You can edit or delete any saved birth at any time, and deleting the account removes every saved birth and the account itself at once, immediately and permanently.

To look after accounts, our staff can see an account's name and email, when it was opened and last signed in to, whether the email is confirmed, and how many births and reminders it holds. They cannot see the saved births themselves: no date, time, place or name on a saved chart is shown to them. Staff may keep a short private note about a support request, send you a link to set a password, and pause an account that is misused; a paused account cannot be signed in to, and nothing in it is deleted until you or we delete the account.

If the assistant (“Ask about this chart”) is offered and you use it, your question and the answer are kept with your account for 180 days, so a follow-up question has its context; you can delete every conversation at any time from the assistant itself, and deleting the account deletes them too. Cached copies of answers last up to seven days. Our staff can read the questions people ask, with dates and numbers blanked and with no account, chart or answer beside them, to improve the answers; they can read an answer only when you marked it helpful or unhelpful, when our own checks replaced it, or when the question was refused, and the name and the birth details are never shown to them. A question that suggests someone may be in danger is not kept at all.

Signing in sets one cookie on this site that identifies your session. It carries an opaque token, not your identity, and keeps you signed in until you sign out: it lasts 400 days, the longest a browser allows, and each day you use the site that time starts again. The apps keep you signed in the same way. We send email only to confirm your address and to reset a password you asked to reset.

When an account is opened, we keep the country and city our edge network reports for the connection, and the site that sent you to us (a search engine, an AI assistant, a social network, or a tagged link), so that we know where our members come from. For this, arriving from another site stores that site's host name in a cookie, vs_src, for thirty days; it holds no identifier and is read only when an account is opened. The IP address itself is not kept with the account.

A Kundli Milan report you choose to keep (“Save this match”) is stored with your account as the two births you entered (name, date, time, place and coordinates) and the guna total, so the same report opens again from your dashboard. Saved matches are kept until you delete them, one by one from the dashboard or all at once by deleting the account. Like saved births, they are shown to no one else and never used for anything but opening the report for you.

You can take a copy of everything your account holds at any time: Settings, Download my data gives one file with your account details, saved births, reminders and saved matches. The file is made when you ask for it and is not kept on the server; it never contains your password hash or any sign-in token. How to delete the account, and what that removes, is set out in plain words at vedicsense.in/account/delete-your-account; deletion is immediate.

If you sign in from one of our apps, the app is given a device token instead of a cookie: a long random key that identifies your sign-in on that device for up to a year. We keep only a one-way hash of it, with a label for the device and when it was made and last used, never the token itself. You can revoke a device at any time from your account settings or by signing out everywhere, and a revoked token stops working at once. If you make an API key on our developers page, we keep it the same way (a one-way hash, the label you give it, its plan, when it was made and last used) and, for each day, how many calls it made to each endpoint, with their units and errors; the birth details a call carries are used for that answer and not kept.

To prevent abuse, and to keep to one account per person, the sign-up and sign-in pages set a cookie, vs_dev, holding a random device identifier, for up to two years. Each time an account is opened or signed in to, we keep with that account a keyed, irreversible fingerprint of the device identifier and of the connection address (never the address itself), with when each was first and last seen. These fingerprints are kept for 180 days and are used only to detect multiple accounts and misuse of free credits. Many people share one mobile network, so a shared connection on its own never stops anyone opening an account. Temporary email addresses cannot be used to open an account. An account opened to break the one-account rule can be banned permanently; a fingerprint of its email address is then kept, never the address itself, so that the same address cannot open a new account.

The VedicSense app is given a guest token the first time it opens, so the calculators work without an account. The guest token is a signed random key with an expiry date, kept on the phone; the server keeps no record of it and counts its calls only to hold a per-minute limit. To limit how many guest tokens one connection can take in a day, they are counted against the same keyed fingerprint of the connection address described above. If you create an account in the app, it sends a random device identifier that it made once and keeps on the phone; we use it in place of the vs_dev cookie, in the same way and for the same 180 days. The app keeps on the phone your sign-in token (in the phone's secure storage), the device identifier, your language and theme choices, the last place you chose and a copy of recent panchang days, so they open offline. It asks for your location only while it is in use, and only if you choose that over picking a city; the coordinates are sent for that answer and not kept with your account. The app contains no advertising, analytics, crash-reporting or tracking software. You can delete your account inside the app, under Account, Delete account.

Where sign-in with a mobile number is offered, you can open an account, or sign in to one, with an Indian mobile number instead of an email address, and you can add a number to an account in Settings. We then keep the number with your account, and the fact that you proved it is yours. To prove it, we send a six-digit code by SMS through an SMS provider in India acting on our behalf, which receives the number and the message, and nothing else about you. We keep the code only as a one-way hash, for at most five minutes, and delete it once it is used. To stop misuse, we count the codes sent to each number and from each connection against keyed, irreversible fingerprints of the number and of the connection address (never either value), and, for a code that adds or removes a number, against the account that asked, kept for two days. You can change the number in Settings, and deleting the account removes it.

When we switch it on, every account needs a verified mobile number to be used: an account without one is asked to add it before its saved charts, reminders and other account pages open, while the free tools stay open to everyone. New accounts are then opened with a mobile number, and an email address is optional; an address you add is written to your account only when you open the link we send to it. If the number you prove, or the address you confirm, already belongs to another account of yours that had no email address, the two accounts are joined into one: the saved births, matches, reminders and conversations of that account move to this one, and the empty account is deleted.

05VedicSense Sangam

VedicSense Sangam is a private, matrimonial circle of VedicSense members looking for a marriage alliance, for themselves or for a member of their family. It is open only to people aged 18 or over, and a profile may be made only for a person of the legal age of marriage in India. Joining asks for a consent of its own, on a separate screen, apart from what you agree to for your account and your kundli; nothing is kept for Sangam without it, and you can withdraw it at any time by leaving.

What Sangam keeps, and why:

• Who the profile is for, and which of your saved births is theirs, to read the chart that suggestions are scored on.
• Gender and date of birth, from that saved birth, to suggest members in the age band each side asks for and to confirm the legal age of marriage.
• The city and state they live in, and the city's coordinates, to suggest members in the area each side chooses.
• Mother tongue, marital status, diet and education, and religion only if you give it, to meet the practical preferences both sides set.
• Your preferences and, for a woman's profile, who may see her (an age range and the education of the men she may be shown to), to decide who is suggested to whom.
• The matching facts of the chart (the Moon's nakshatra and rashi, and whether a Mangal dosha forms) and, once suggestions are made, the list of suggestions with their scores.
• When the consent was given and, once it has been done, when the profile was verified.

Who sees what: no other member sees a name, photograph or contact detail before both sides have said yes. Before that, a member is shown a suggestion's age, city and the practical details above, the reading of the two charts, and whether the profile is verified. Our staff see a member's status (waiting, verified or paused) and counts by city, language and gender, never the profile itself. We do not ask for caste and do not keep it.

Everything kept for Sangam is kept until you leave. Leaving, from your Sangam page, erases the profile, its preferences, the chart facts and every suggestion it was part of at once; deleting your account does the same. Pausing keeps the profile but takes it out of every list. The grievance officer for Sangam is Manish Sharma, at [email protected]; a grievance is acknowledged within 24 hours and resolved within 15 days.

06Cookies, analytics and tracking

VedicSense runs no advertising network. To learn which pages and calculators are used, most pages load one analytics script from Statsy (statsy.co). It records the page address, the site that sent you, your browser, operating system, device type, screen size, language and time zone, and an approximate location (country, region and city) looked up from your IP address. Statsy states that it discards the IP address once that lookup is done and does not store it, and that it keeps these records for up to three years while our plan is active.

The script is left off every page whose address could identify you or carry your birth details: the link of a chart or of a kundali match, which holds the date, time and place of birth, and every account and sign-in page. Birth details you type into a form are sent only to our server, never to Statsy. Depending on its setting, Statsy may place one first-party cookie, statsy_vid, that recognises a returning browser for up to a year; it holds a random identifier, not your name or email.

Fonts, styles and every other script are served from vedicsense.in. The site's content security policy allows the page to contact only vedicsense.in and statsy.co, so no other domain can be reached from your browser; this is enforced by the browser, not just promised. The panchang remembers the city you chose in your browser's own storage, on your device only, so it opens there next time. Product pictures shown beside some results are served from vedicsense.in too. A link to a product on another site tells that site which calculator page the link was on; nothing about you or your birth details goes with it.

Our edge network provider may set a short-lived security cookie on some requests to tell a browser from a bot. It carries no identity and is not used by us. Apart from Statsy's, the cookies set for this site are the sign-in cookie for a visitor who chose to open an account, the referring-site cookie described above, the device cookie vs_dev that the sign-up and sign-in pages set (described under accounts), and the sign-in cookie for our own staff on the administration pages, which no visitor page ever sends.

To understand which pages and calculators are used, the server keeps an aggregate usage record for each request: the page, the calculator run, the time, the response status and speed, the country the edge network reports, whether the browser is a phone or a desktop, the referring site's host name, and a short hash that changes every day and cannot be traced back to you or your device. It holds no IP address, no browser string, no form field and no birth detail. It is used only to improve the site and is kept for 400 days.

07Who else handles the data

These providers process data on our behalf, under their own published terms:

• A cloud host in Mumbai, India, on whose server the site runs and where the request log lives.
• An edge network and security provider that sits in front of the server to cache pages and filter attacks. Requests pass through its network, which may route them outside India.
• Statsy (statsy.co), the analytics service described above, which receives page visits from the pages that load its script and runs on cloud servers that may be outside India.
• When the assistant answers a question, an AI model provider receives the chart's computed facts and your question in order to write the answer, and nothing else: not your email, your account or your IP address. At present that is OpenAI (United States), through its business API, whose terms do not allow the content to be used to train its models; we add a provider only on terms that say the same.
• When you sign in with a mobile number, MSG91, an SMS provider in India, receives the number and the message carrying the code, only to deliver it by SMS.

Statsy never receives the birth details you enter. Neither of the other providers receives them for any purpose other than carrying the request to and from our server. We do not sell, rent or trade personal data, and we do not share it with anyone else unless a court or a competent authority in India lawfully requires it.

08How it is protected

Every connection is encrypted with HTTPS and the site instructs browsers never to load it unencrypted. Access to the server is by key only. Security headers restrict what the page may load and forbid it from being embedded in other sites. These are the reasonable security practices required under rule 8 of the 2011 rules.

09Your rights

Because nothing you enter is stored, there is nothing to correct, export or erase after a page is served. You can still:

• Ask us what personal data, if any, we hold about you.
• Ask us to delete a request-log entry that identifies you, which we will do if it is still within the retention period.
• Withdraw from any processing simply by not using the site; no consent is stored, so there is nothing to revoke.
• Raise a grievance with the officer named below, and if it is not resolved, approach the Data Protection Board of India once it is constituted under the 2023 Act.

10Children

The site can be used to compute a chart for any date of birth, including a child's, and this needs no account and stores nothing. We do not knowingly collect any data from a child that is retained, and we do not track or profile anyone of any age.

11Changes

If this policy changes, the new version is published at this address with a new effective date. The current effective date is at the top of the page.

12Who we are & how to reach us