Privacy policy

Account information. If you sign in, it's with Google. We receive your name, email address, and profile photo from Google and store them as part of your account. We don't set a password, and we don't ask for anything beyond what Google already shares for a basic sign-in.

Saved places. If you heart a restaurant, we store which restaurant, in which of your lists, tied to your account. Only you can see your saved places.

Contributions. If you add a restaurant or a dish note, we store what you typed. If you choose to include your name or contact info in a submission, that text is public — it's shown on the restaurant's page as attribution, the same way a comment would be. Contributions are not currently linked to your account, whether or not you're signed in.

Usage analytics. We use an analytics tool to understand how the site is used — which pages get visited, which searches and filters get used, and when something breaks. This includes standard web analytics (pages viewed, general location from IP, device/browser type) and session recordings of how you interact with the page, to help us fix confusing or broken UI. Anything you type into a form field is masked in these recordings by default — we don't capture the text of your dish notes or contribution forms this way. If you're signed in, this activity is linked to your account ID (not your email) so we can tell returning visitors apart from new ones.

• We don't sell or rent your information to anyone.
• We don't run ads or ad-tracking on this site.
• We don't share your email or saved places with other users.
• We don't use your Google account for anything beyond signing you in — we can't post as you, read your Gmail, or access anything outside the basic profile Google shares at sign-in.

Running JainEats means a few specialized services handle data on our behalf, each only for what's needed to keep the site working:

• Sign-in.Google, since that's who you sign in with.
• Database and authentication. A managed backend provider.
• Website hosting. A cloud hosting provider.
• Usage analytics. The analytics tool described above.

None of these are given more than they need to provide their piece of the site, and none are permitted to use your data for their own purposes.

We use a session cookie to keep you signed in, and our analytics tool stores a small identifier (cookie or local storage) to recognize repeat visits for analytics. Neither is used for advertising, and neither follows you to other websites.

Your saved places are private — only visible to you. Anything you contribute to the directory itself (a restaurant, a dish note, an order tip) is public by design, because the whole point of JainEats is a shared, crowd-sourced directory. If you submitted a contribution and want it corrected or removed, contact us and we'll take a look.

You can permanently delete your account at any time from your account page. This immediately and permanently deletes your account and every place you've saved, and disconnects JainEats from your Google Account. It can't be undone.

Restaurants and dish notes you've contributed to the directory stay in place — they're shared directory content, not personal data tied to your account, and removing your account shouldn't erase a restaurant's dish history for everyone else. If you'd like a specific contribution removed too, email us and we'll handle it directly.

If what we collect or how we use it changes meaningfully, we'll update this page and its "last updated" date. JainEats is a small, actively developed project — check back occasionally.

Questions, corrections, or a deletion request beyond what the account page covers — reach us at hello@jainfoodmap.com.