Privacy
What Jevan keeps about you, who else sees it, and how long it stays.
Updated 1 November 2026. A draft a lawyer has not reviewed yet.
What Jevan keeps
- Your taste answers, in a cookie on your phone
- Dishes you save to a shortlist
- A count of menu opens by table and day
- Your meal rating and note, if you leave one
What Jevan never keeps
- Your name
- Your card
- Your location
- Your answers sent to an AI model
Taste and shortlist cookies end after four hours.
Read the full clauseWho this covers
This policy covers four groups of people on jevan.ai: guests who scan a table QR code, diners who make an account, restaurant owners and staff who use the kitchen dashboard, and people who join the waitlist or write to us.
“We” means Jevan. “You” means the person using the site. Send questions to hello@jevan.ai.
What we collect
Guests at a table
You can read a table menu without an account or a name. If you answer the taste questions, a cookie on your phone keeps your answers for four hours: the city that shaped your taste, the cuisines you grew up with, your dietary style, the kind of plate you want and any allergens you list. Dishes you save stay in a second four-hour cookie.
When you open a menu, we count the open against the kitchen, the table and the day, with no cookie. When the menu suggests dishes, we record which ones it suggested, which ones you saved and the answers that ranked them, under a random key your phone makes for that visit. That record holds no name, account, device or allergen.
If you rate your meal in Jevan, we keep the table, the stars, your note and the time. If the restaurant links its Google listing, the rating button opens Google Maps instead, and Google’s privacy policy covers what you post there.
Diners with an account
If you sign in with Google or with an email and password, we receive the name and email address on that account. An email address must be verified before it can sign in. The account keeps your taste answers and shortlist, so they follow you to other restaurants on Jevan.
Restaurants and their register
A restaurant that connects its register lets Jevan read its menu, its orders and their payment totals, tips, the server on each order, the party size when the register records one, staff names and clock-ins. Jevan only reads from the register and never writes to it. We drop guest names, card details and the register’s raw messages, and we do not process cards.
Owners also enter the restaurant’s name and address, suppliers, costs, stock counts, schedules and pay rates. Menu and invoice photos are read on the owner’s device and are never uploaded or stored.
If an owner connects a Google Business Profile, we keep Google’s sign-in token, sealed for that kitchen, and the location’s reviews: each reviewer’s display name, the review, Google’s saved reply and any draft reply.
Kitchen staff
Owners invite staff by email. For each person we keep a name, email, access level, pay rate, shifts, availability, time-off requests and clock-ins. When a phone clocks in, the browser shares its position once. Jevan checks that it is within 150 meters of the kitchen and does not keep it. A staff account sees its own shifts, never anyone’s pay or anyone else’s hours.
Waitlist and messages
Joining the waitlist sends your email, ZIP code and the restaurant you name to Resend, our email provider. Our database does not keep it. Jevan’s founders may copy signups to a private Google Sheet. If you write to us, we keep your message and your address.
Like any website, our servers see your IP address, your browser and the page you ask for.
How we use it
Taste answers rank the dishes on the table menu. The ranking runs against your saved answers, without a hosted AI model. It may hide dishes or show ingredients. It never calls a dish safe for an allergy.
A restaurant’s saved orders build that restaurant’s own forecasts, prep lists, supplier order drafts, cost and labor reports, and the emails its owner turns on. Staff records run schedules, clock-ins, tips and payroll exports for the owner. Suggestion records and meal ratings show us how well the ranking works, and may rank that restaurant’s dishes for its later guests; they never train a model for another restaurant.
We send sign-in, invitation and alert emails. Waitlist contacts may get Jevan news and can unsubscribe at any time.
We use guest and account data to give you the service you asked for. We use a restaurant’s menu, orders, stock and staff records on the restaurant’s instructions, which include building its forecasts and improving its recommendations.
AI models
Ask Jevan, the dashboard assistant, sends a question and the kitchen records it needs to a hosted model through the OpenCode Go gateway. When it drafts a reply to a Google review, it sends the kitchen’s name, the stars, the review’s words and the dishes the review names, never the reviewer’s name. If our rules cannot read a line on an invoice or stock sheet, that line’s text may go to the same model. After the nightly save, Ask Jevan also prepares a few answers and review reply drafts ahead, only for restaurants that agreed to AI and whose owner opened the dashboard in the past week. Jevan keeps a prepared answer for a day, and a record of each AI run’s length, model calls and tokens for 30 days, never its question or answer.
A model Jevan runs itself labels each dish from the menu text. Forecasts come from Jevan’s own statistics, fitted to each restaurant’s own history, not a hosted model. Whoever connects a restaurant’s register agrees, for the restaurant, to this use of AI on its records.
Ask Jevan and the dashboard never train a model. No guest answer, order or register record goes to a hosted model for training, and Jevan never trains a model on what it reads from a register. Jevan’s dish model learns from dishes Jevan writes and labels itself and, only where a restaurant’s manager turns it on in Settings, from dishes typed into Jevan or read from a menu photo, in a form that names no guest and no kitchen, on systems Jevan controls.
Where it lives
Jevan stores data in the United States. If you use Jevan from another country, your data still sits on those US systems.
How long we keep it
- Taste and shortlist cookies4 hours
- Team invitation links7 days
- A kitchen’s Google reviewsUntil it disconnects
- Suggestion recordsUntil the kitchen leaves Jevan
- Accounts and kitchen historyUntil you ask us to delete them
Disconnecting the register keeps a restaurant’s saved history so its reports still work; email us to delete it. Disconnecting Google deletes the token link and every saved review. A clock-in position is never kept.
Your rights
Email hello@jevan.ai to see, correct, export or delete what we hold about you. We answer as soon as we can, and within the time the law sets. If you live in California, you can also ask what we hold, ask us to delete it, and ask us not to sell it.
The suggestion record holds nothing that identifies you, so we cannot find yours to show or delete it. You can skip the taste questions and read any menu without signing in.
Security
Traffic uses HTTPS. The kitchen dashboard needs a signed-in staff account. Register and Google tokens are encrypted for each kitchen. Invitation tokens are stored hashed, expire after seven days and work once. No system is perfectly safe; if you see a problem, tell us at hello@jevan.ai.
Children
Jevan is not meant for children under 13, and we do not knowingly collect their data.
Changes
If this policy changes in a way that matters, we post it here with a new date. If you keep using jevan.ai after that date, you accept the new policy. The terms sit next to this policy.