Privacy Policy

1. The short version

JyotishGen computes your birth chart entirely in your web browser using JavaScript. The date, time, and place of birth you enter are never transmitted to any server — there is no backend that receives, logs, or stores this information. If you close the tab, the chart is gone unless you've saved or printed it yourself. The same is true of the palmistry tab: a palm photo is read inside your browser and never sent anywhere. We do count how many visits and page views the site gets each day, and how many charts, matches, readings and calendar views happen, as an anonymous total with only an approximate city name attached to it — section 3 sets out exactly what that involves.

2. Palm photos

The palmistry tab reads a photograph of your palm. That photograph is never uploaded. It is decoded into an in-memory canvas inside the tab, measured there, and discarded — it is not written to local storage, session storage, or IndexedDB, and no copy of it is sent anywhere. There is no server that could receive it.

• The reading is produced from measurements only — the length, curve and position of the creases relative to the width of your own palm. Once those numbers exist, the image itself is no longer needed and the buffers holding it are released.
• The diagram shown with your reading is drawn from the traced outline and lines, not from the photograph. It contains no pixels of the original image, which is why you can discard the photo and keep the reading.
• A Discard the photo now button releases the image immediately. Remove photo clears it along with the file selection.
• Everything left in memory is wiped when the tab is closed, reloaded, or navigated away from.
• If you use your phone's camera from the upload button, the photo is handed to the page by the operating system. Whether your phone also saves its own copy to your camera roll is a setting on your device, not something this site controls.

As with the kundali calculator, the practical consequence is that we hold nothing: there is no palm image for us to lose, hand over, or be asked to delete.

On your device: saved charts, reminders and offline use

Some features keep information in your own browser so they can work the next time you visit. None of it is sent to us or to anyone else, and there is still no account and no server-side copy.

• Saved charts. If you press “Save on this device”, the name, date, time and place of birth you entered are kept in your browser’s local storage, so My Day, Rashifal, Muhurat and the tithi birthday page can open with them. Nothing is saved unless you ask. You can remove one chart or all of them on the My Day page, or by clearing this site’s data in your browser.
• Preferences and progress. Your language, chosen city, quiz scores, nakshatra-series progress and samagri checklists are kept the same way.
• Reminders. If you turn reminders on, the upcoming dates are worked out on your device and kept in your browser’s storage, so the app can show a notification the day before. Notifications are shown by your own browser; we do not run a push server and receive nothing.
• Offline use. A service worker keeps copies of pages and files you have opened, so the site loads faster and works offline. It never stores what you type, and it never caches the visit counter.
• Share pictures. When you share a chart or a Milan score as a picture, the image is drawn in your browser and handed straight to your phone’s share sheet or downloaded. Your birth date is only on it if you tick the box.

3. What we do store

The only data saved on your device is a few preferences — your choice of English or Hindi; on the Vikram Samvat calendar, Panchang, nakshatra and Disha Shool pages, the city you picked (or, if you tap “Use my location”, the coordinates your browser gives the page); on the calendar page, the month-name style (Amanta or Purnimanta); and, in the baby-name bank, the names you save with the heart — kept in your browser's local storage so they are remembered the next time you visit. These are never sent to us. A location, if you choose to share it, is used only inside your browser to work out sunrise, and the city list you search is a static file loaded into your browser. You can clear it at any time by clearing your browser's site data for jyotishgen.com.

On our side, we keep a count of how many people visit and how often the tools are used, and nothing else. When any page loads, it sends the word view with the page’s name (for example diwali-date), the language you are reading in (English, Hindi or Marathi) and, for the first page of a visit only, a broad source group: search engine, social or chat app, another website, typed directly, or the installed app. When a tool finishes a result (a kundali, a match, a palm reading, the calendar, a life timeline, a transit reading, My Day, a muhurat search or a tithi birthday), it sends that tool’s name; using share, reminders or the “did this happen” buttons sends that feature’s name. These only increment daily totals. A “visit” is the first page view in a browser session. To be exact about what that means:

• The database holds counters only: per day, a count for each tool (in half-hour slots, so totals can be shown in Indian or UTC days), and running counts for each approximate city (for example “Pune, IN”), each page, each language and each source group. There is no row that represents you, or your visit, or your device.
• The approximate city is worked out from your IP address at the moment of the request, using a free offline database (IP geolocation by DB-IP) that sits on our own server, or a label supplied by our network provider if one is in use. The address is used in memory for that lookup and then discarded; only the resulting city and country label is counted. We never store the IP address or any finer location such as a street, postcode or coordinates.
• No birth details and no image data are involved. The message that gets sent has room for a few short words and a true/false flag; it could not carry them.
• No cookie, no session identifier, no advertising ID, no referring address, no user agent, and no IP address is stored. The source group is worked out in your browser; the address you came from never leaves it.
• Your IP address is used in memory, for a few seconds, to stop one machine from inflating the count. It is hashed with a salt that changes daily and the hash is deleted within two hours, so it cannot be used to recognise a returning visitor.
• A flag in your browser's session storage lets us tell a visit apart from a repeat use in the same sitting. It is cleared when you close the tab and is never sent anywhere.

The purpose is the ordinary one: to know whether anyone is using this, and roughly where from. It cannot tell us who you are, where you live beyond the city, or what you asked it.

4. Advertising and cookies

This site displays ads served by Google AdSense. Google and its advertising partners use cookies and similar technologies to serve ads based on your prior visits to this and other websites, and to measure ad performance. Google may also collect and use non-personally-identifiable information, and in some regions personally-identifiable information, in accordance with its own privacy policy.

• You can opt out of personalized advertising by visiting Google Ads Settings.
• You can also opt out of a third-party vendor's use of cookies for personalized advertising by visiting www.aboutads.info.
• Third-party vendors, including Google, may use cookies to serve ads based on your prior visits to this website or other websites.

Consent in the EEA, UK and Switzerland. Where the law requires it, a consent message from Google is shown to visitors in these regions so you can accept or decline cookies used for ad personalisation. You can change that choice later through the privacy settings link Google provides. How Google uses data from sites that use its services is explained at policies.google.com/technologies/partner-sites.

If this site uses Google Analytics or a similar analytics service to understand traffic patterns, that service uses its own cookies and collects information such as pages visited, approximate location (derived from IP address), device type, and referring site. This information is aggregated and is not linked to the birth-chart data you enter, which — as above — never reaches a server in the first place.

5. Children's privacy

This site is not directed at children and does not knowingly collect personal information from children. Because no birth data is transmitted or stored server-side regardless of who enters it — including when a parent generates a chart for a child — there is no server-side children's data to describe. If you believe a child has provided personal information through a channel this policy hasn't accounted for, contact us and it will be addressed.

6. Your rights and choices

Since no personal data is stored on our servers, there is generally nothing for us to access, export, or delete on your behalf — the data was never sent to us. For anything related to advertising cookies specifically, use the opt-out links in section 4. If you have questions about this policy or believe it doesn't cover a specific situation, see the Contact page.

7. External links

This site may link to external resources (for example, timezone or daylight-saving references). We aren't responsible for the privacy practices of external sites — check their own policies before sharing information with them.

8. Changes to this policy

This policy may be updated from time to time, for instance if new advertising or analytics services are added. Material changes will update the "Last updated" date at the top of this page.

9. Contact

Questions about this policy can go to the address on the Contact page.