Cookie Policy

Last updated: November 13, 2026

This policy describes the cookies and similar technologies we use. It supplements our Privacy Policy.

1. What they are

A cookie is a small file that a site saves in your browser to remember information between visits. Alongside cookies there are other technologies with the same purpose, such as local storage, which keeps data on your device until you delete it.

A clarification that is rarely made: Delimenu uses hardly any cookies of its own; most of what we store lives in your browser's local storage, which is not sent to the server with every request. The cookies that are created come from the third-party services listed below.

2. Exactly what we use

TechnologyWhat it is forCategory
Firebase sessionKeeping you signed in so that you do not have to sign in on every visit. It belongs to Google, our authentication provider.Essential
emailForSignInRemembering the email address you entered so that the sign-in link can be completed when you return. It is deleted when you sign in.Essential
pendingOAuthRequestRemembering, while you sign in, which AI agent asked you for permission to manage your menu, and returning you to that screen. It is deleted when you return and expires after ten minutes.Essential
cart_<restaurant>Saving the cart of a menu so that it is not lost on reload. It is deleted when the order is sent.Essential
cookie-consent.v1Remembering whether you accepted or rejected what this page describes, so as not to ask you again on every visit.Essential
pwa-install-promptRemembering that you already closed the prompt to install the menu as an app, so as not to show it again right away.Functional
promos-seenRemembering which promotions of a menu you already saw today, so as not to show them again on every visit that day.Functional
themeRemembering whether you prefer light or dark mode.Functional
localeRemembering the language you prefer to see Delimenu and menus in.Functional
dm-events.v1:<restaurant>Preventing a single visit to a menu from being counted several times as you browse between products. It stores only a marker, with no data about you, and is deleted when you close the tab.Essential
dm-visitor.v1Storing, for each menu you open, the date of your first and of your last visit. It lets the restaurant's statistics count your device once a day and tell a first visit from a return. It holds no identifier and is not sent to any server: only the answer “first visit” or “has been here before” leaves the device, with nothing that identifies you.Anonymous analytics
dm-view-only.v1:<restaurant>Keeping a menu without cart or order button while you browse between products, when you arrived by scanning a restaurant's view-only QR code (the one on the tables). It stores only a marker, with no data about you, and is deleted when you close the tab.Essential
dm-table.v1:<restaurant>Remembering which table you are ordering from while you browse between products and the cart, when you arrived by scanning a table's QR code, so the order names it without you typing it. It stores only the table's name or number and is cleared when you close the tab.Essential
Vercel AnalyticsCounting, in aggregate, the pages visited and where visits come from. It creates no cookies and stores nothing on your device: each visit is recognised by a code computed on the server that is discarded after 24 hours, and it is never linked to your account.Cookieless analytics
Vercel Speed InsightsMeasuring, in aggregate, how long pages take to load, to know what to improve.Analytics
Meta Pixel (_fbp)Measuring the effectiveness of our advertising. It records the pages you visit and four specific moments: when you create your account, when you create your first restaurant and the free trial begins, when you open the subscription payment and when that subscription becomes active. In the last one we also send the amount charged. Our server also tells Meta when you create your account, start the trial and subscribe (see section 3). We never send your name, your readable email or the content of your menu.Advertising, only on the production site
OpenAI Ads Pixel (__oppref)Measuring the effectiveness of our ads in ChatGPT. It records the same moments as the Meta Pixel, with the same amount in the last one, and keeps the reference of the ad you clicked. If you accept, our server also passes that reference to OpenAI, along with your email and user id irreversibly hashed (SHA-256), when you create your account, start the trial or subscribe (see section 3). We never send your name, your readable email or the content of your menu.Advertising, only on the production site

Swipe to see the whole table.

The items marked as essential cannot be disabled without breaking basic functionality: without them it is not possible to maintain the session or keep a cart.

3. Consent

Analytics and the advertising pixels are not loaded until you accept them. If you reject them, or simply do not choose, those scripts never run. What is marked as essential or functional always works, because without it there is no session and no cart.

Vercel Analytics also always works, because it uses no cookies and stores nothing on your device, as the table explains.

Our server tells OpenAI about three moments — when you create your account, when your free trial starts and when your subscription is activated, with its amount — even if you have not accepted, but then without any data that identifies you: only what happened, when and for how much. The ad reference, the browser reference and your hashed email and user id are added only if you accepted, and if you reject while signed in to your dashboard we delete them and stop sending them.

It tells Meta about the same three moments even if you have not accepted, but since Meta does not take an event with no data at all, all that goes is your Delimenu user id, irreversibly hashed (SHA-256), which on its own does not tell Meta who you are. The reference of the ad you clicked, your browser, your IP address and your hashed email are added only if you accepted, and if you reject while signed in to your dashboard we delete them and stop sending them.

Rejecting does not degrade the service: the site and the menus behave the same.

3.1 Your current decision

You can change it whenever you wish, in either direction:

If you withdraw consent, in addition to no longer loading the scripts we delete the advertising cookies that have already been created (_fbp, _fbc, __oppref and __obref).

Your choice is saved in your browser, so it is per device: if you visit from another one, we will ask you again. The same applies if you clear the site's data.

Please note that this applies to the Delimenu site and to the public menus we host.

4. Additional controls

The previous section is the main control and is sufficient on its own. These are options that depend on your browser or your account, and that apply even if you have not made a decision here:

  • From your browser: all browsers let you block or delete cookies and site data, and limit cross-site tracking. If you block the essential ones, you will not be able to sign in or use the cart.
  • Meta advertising: you can adjust the use of your data for ads from the settings of your Facebook or Instagram account.
  • Do Not Track signal: if your browser offers tracker blocking or blocking extensions, they will prevent the advertising pixels from loading.

5. Changes and contact

We will update this policy when the technologies we use change. The date of the last update appears at the beginning of the document.

If you have questions, write to us at support@delimenu.co.