This policy explains the cookies and similar technologies used on the Octopus Menu website, on restaurants’ menus served by Octopus Menu, and in the restaurant dashboard. On a restaurant’s menu, the restaurant is responsible for diners’ personal data; see the diner privacy notice.
Cookies we set
| Name | Where | Purpose | Duration | Category |
|---|---|---|---|---|
| __octopus_consent | Our website, sign-up pages and restaurants’ menus | Remembers your cookie choice. | 6 months | Strictly necessary |
| __octopus_lang | Our website | Remembers the language you picked from the website’s language menu, so the next pages open in it. Set only when you pick a language; never set from your location or browser settings. | 1 year | Functional |
| __octopus_public_session | Restaurants’ menus | Remembers which table’s QR code you scanned, so feedback can say where you sat. Signed. | 4 hours | Strictly necessary |
| __octopus_recognition_<restaurant id> | Restaurants’ menus | A random identifier that lets the menu welcome you back on a return visit to the same restaurant. It holds no name or contact details and is not stored on our servers. You can reset it from the welcome message. | 30 days | Functional |
| __octopus_loyalty_<restaurant id> | Restaurants’ menus | Keeps the loyalty card you joined on your phone. Set when you join or open your card link; removed by “Not you? Use a different card” or “Delete my card”. Signed, and holds no name or email. | Up to 400 days | Strictly necessary |
| sb-<project>-auth-token | Restaurant dashboard and our staff console | Keeps a signed-in user signed in. | 7 days | Strictly necessary |
| om-pkce | Restaurant dashboard | Secures signing in with Google or Apple, where offered. | 10 minutes | Strictly necessary |
| __Host-octopus_imp | Restaurant dashboard | Used only when our support staff access an account to help its owner; records the support session. | 8 hours | Strictly necessary |
| analytics_retention_dismissed | Restaurant dashboard | Remembers that you closed the analytics-history notice. | Until the browser closes | Functional |
Analytics
If you accept analytics cookies, we count visits to our own marketing and sign-up pages with our self-hosted analytics, and a restaurant’s menu records page views, QR scans and language changes for that restaurant’s menu statistics. If you decline, neither is recorded. We do not set Google Analytics cookies of our own.
A restaurant’s own tags
A restaurant can add its own analytics and advertising tags to its menu: Google Analytics, Google Tag Manager or the Meta Pixel. On that restaurant’s menu, accepting analytics cookies also allows those tags to load. They can set their own cookies (for example _ga or _fbp) and send data about your visit to Google or Meta, which may use it for advertising. The restaurant chooses these tags and is responsible for them. If you decline analytics cookies, they do not load.
Other technologies
- Browser storage. Restaurants’ menus keep a few small items in your browser’s own storage: a random visit identifier (cleared when you close the tab), whether you closed an age notice (cleared when you close the tab), and whether you already used the review button today.
- Fonts. Menu templates and the dashboard load typefaces from Google Fonts, so your browser sends your IP address and browser details to Google when those pages load. Google Fonts does not set cookies.
- Payments. Paying for a plan takes place on a Stripe checkout page, where Stripe sets its own cookies under its own policy.
Changing your choice
You can change your choice at any time with the “Cookie settings” link at the bottom of our website and of every restaurant menu. You can also block or delete cookies in your browser settings; blocking strictly necessary cookies may stop parts of the site working, such as signing in or keeping your loyalty card.
Contact
Questions about cookies: privacy@octopusmenu.com.