Politique de confidentialité

Account email and sign-in method (Google OAuth or emailed magic link), managed by Supabase Auth.

Google sign-in requests no scopes beyond the default (email/profile) — no Calendar, Drive, or contacts access.

A venue owner’s dashboard-language preference. The email address typed on the publish flow’s “where should we send your link” field is stored but never used to send anything.

Menu content (dish names, descriptions, allergens, prices, photos), venue name and address, phone number, opening hours, and the venue’s Wi-Fi network name and password — stored in plain text, shown to guests on the menu, since that is its purpose.

Dish photos, logos, and cover images are stored in publicly readable file storage — reachable by anyone with the URL, no sign-in required, since the guest menu itself is unauthenticated. Every uploaded image is re-encoded before storage, which strips all EXIF metadata (including GPS location) as a side effect.

A menu scan records only the venue, which menu, the guest’s chosen language, and a timestamp — no IP address, browser identifier, or cookie of any kind.

Tapping “+” to shortlist a dish records only the venue, the dish, and a timestamp, the same way. The shortlist itself lives only in the browser’s session storage and is never sent to a server.

There is currently no guest-submitted review feature — displayed ratings are entered by the venue owner.

NEXT_LOCALE — the dashboard owner’s language choice. 1 year.

MENU_LANG — a guest’s chosen language for one venue’s menu. 1 year.

marketing-theme — light/dark preference for this website. 1 year.

A short-lived cookie linking an in-progress menu import to its saved draft. 7 days.

A sign-in session cookie, managed by Supabase, while signed in.

Session-only browser storage for a guest’s dish shortlist and a dismissed announcement banner — cleared when the tab closes, never sent to a server.

None of these are advertising or tracking cookies.

Supabase — database, sign-in, and file storage.

Anthropic — menu photos (resized, with metadata stripped) are sent to read a menu into text; separately, dish names/descriptions/prices are sent as text to translate a menu. Neither call sends a venue’s name, address, or owner identity.

Google — sign-in, and the Google reviews connection described below. Fonts are downloaded once at build time and served from this site, not from Google, at page-load time.

Google reviews: a venue owner can connect his venue to its Google listing. When he searches for it, the venue’s name and address are sent from our server to the Google Places API, and Google returns matching listings for him to choose from. Only the chosen listing’s place ID is stored. No rating, no review count, and no review text is requested, displayed, or stored by this site.

A connected venue’s menu shows a “Leave a review on Google” button. It is an ordinary link: nothing is sent to Google until a guest taps it, and the link carries rel=“noopener noreferrer”, so Google is not told which page the guest came from. Following it leaves this site, and from that point Google’s own Terms of Service and Privacy Policy apply to whatever the guest does there, including signing in to leave a review.

Netlify — hosting.

No analytics, advertising, or tracking service of any kind is used.

Menu content is kept until a venue owner changes or removes it — there is no automatic expiry.

A replaced photo is deleted immediately.

Scan and shortlist-tap records are currently kept indefinitely, with no automatic limit.

Deleting your account removes your sign-in only. Any venue you own keeps running exactly as it is — same content, same address, same edit link — it is simply no longer linked to an account.

There is currently no way to delete a venue and its content from within the product.

hello@menukaart.be