Privacy
Last updated 30 August 2026. This draft describes how Jevan works today. A lawyer has not reviewed it yet.
Who this covers
Jevan is a USA restaurant product on jevan.ai. This policy covers guests who scan a table QR, diners who sign in, and kitchen staff who publish menus.
We means Jevan. You means the person using jevan.ai. Questions go to dikshab0304@gmail.com.
Information we collect
Guests can read a menu with no account. We do not need a name for that.
If you name a palate in this browser, we may store the city that shaped your flavour, the cultural cuisines you grew up with, and allergens you listed.
If you sign in with Google or with an email and password, we receive the account you choose. That account holds identity, saved taste, recommendations across restaurants, and loyalty. We do not use phone OTP or SMS login.
Kitchens supply dishes, ingredients, and listed allergens. After a confirmed real order we may store enough of that ticket to award loyalty points and, later, to fill a forecast.
Servers may also see the usual request data a site needs to run: IP address, browser, and the page you opened.
How we collect it
You type palate answers. You may sign in with Google on a full-page redirect, or with an email and password on this site. Kitchens publish menus. A diner may send a kitchen ticket from the table QR. Payment stays with the house. Kitchen owners invite staff by email.
Cookies are set by the server. They are HttpOnly, Secure in production, and SameSite=Lax. The site does not write identity cookies from JavaScript.
How we use it
City, cuisine, and listed allergens rank the table. We may filter dishes and show ingredients. We never call a dish safe.
A signed-in diner keeps the same taste at other Jevan kitchens. Points stay with the kitchen that earned them. Kitchen staff sign in to manage menus, table QR codes, and staff invites.
We store data in the United States so the product can run. A hosted model reads a restaurant’s own menu text to label each dish with one cuisine, and writes sentences about a kitchen’s own saved sales for its owner. It never sees your answers, your account, or your order, and it does not decide the order of dishes on your table menu. That ranking runs on this page against the answers you saved. We do not use a hosted model to forecast covers.
Legal basis
Jevan is built for the United States. If you live in California, you can ask us what we hold, ask us to delete it, and ask us not to sell it. We do not sell personal information.
We process palate and account data to provide the service you asked for. We process kitchen menus under the restaurant’s instructions.
Where it lives
Data is stored in the United States. If you use Jevan from another country, your data still sits on those US systems.
How long we keep it
A palate cookie may last about seven days on this browser. An unclaimed loyalty cookie may last about seven days. It never spends points.
A signed-in account stays until you ask us to close it. Confirmed order history stays so a kitchen can later see a forecast. We do not invent forecast rows.
Your rights
Email dikshab0304@gmail.com to see, correct, or delete what we hold on you. Ask us to export your saved taste. We will answer as soon as we can.
You can refuse the palate cookie by not answering those questions, and you can read a menu without signing in.
Security
Production cookies are Secure. Traffic uses HTTPS. Access to kitchen tools needs a signed-in staff account. Invite tokens are hashed in the database, expire, and work once. No system is perfectly safe. Tell us at dikshab0304@gmail.com if you see a problem.
Children
Jevan is not directed at children under 13. We do not knowingly collect their data.
Changes
If this policy changes in a material way, we will post the new date on this page. Keep using jevan.ai after that date and you accept the new policy.
The terms sit next to this policy.
