Skip to content

Policies

Cookie Policy

Last updated 14 November 2026

1. What this covers

Cookies are small files your browser keeps for a website. This policy also covers similar storage your browser keeps on your own device — localStorage, session storage (which goes when you close the tab) and IndexedDB. Some are set by us, some by providers we use to run ResoFlow, such as Stripe and Cloudflare.

We don’t show adverts on our site or sell your data. If you choose advertising cookies, we learn which of our own adverts work, and Meta may also use what it learns for the adverts it shows you (section 3).

2. Your choices

Our cookie banner has three controls, and uses the same names:

  • Essential cookies — always on, because ResoFlow can’t work without them: keeping you signed in, taking payments, protecting against fraud and bots, and remembering your preferences.
  • Analytics cookies — help us see how our website and dashboard are used and how visitors found us. Off until you accept.
  • Advertising cookies — tell us which of our Google, Facebook and Instagram adverts work and, from our servers, when a venue that came from a Google advert first pays us. Off until you accept. The Google part needs analytics cookies on too.

If you ignore the banner or choose Essential only, no analytics or advertising cookies are set. Change your mind any time with Cookie preferences in our footer: accepting starts them at once; turning them off stops them at once (we delete the advertising cookies on our own site straight away, and a page refresh fully clears the analytics tool and the Meta pixel). If we add a new choice, the banner asks you again. You can also clear cookies in your browser’s settings, though turning off essential storage will stop ResoFlow working properly.

3. Analytics and advertising (only with your yes)

NameProviderWhat it’s forHow long
_ga, _ga_*Google Analytics 4Totals of which pages and features are used, and which links (such as our adverts) brought visitors.Up to 2 years
ph_* (local and session storage)PostHogCounts which pages and features of our website, sign-up and dashboard are used, and keeps a recording of the visit so we can see where people get stuck. The recording shows our own menus, buttons and headings; everything typed, every picture and everything from a venue’s own records stays hidden. Never on a guest’s page or a venue’s own website.Until you turn analytics cookies off (we delete them then) or clear your browser; some only until you close the tab.
_gcl_au, _gcl_aw, _gcl_gb, _gcl_gsGoogle Ads, through Google AnalyticsRemember that your visit came from one of our Google adverts (Google’s click reference), so a sign-up can be matched to it. Google may keep the same reference in local storage under a similar name.90 days
_fbpMeta (Facebook and Instagram), through the Meta pixelLets Meta recognise this browser’s visits to our website and match them to our adverts.90 days
_fbcMeta, through the Meta pixelMeta’s click reference, set only when you arrive from one of our Facebook or Instagram adverts, so a call booked or an email left can be matched to it.90 days
frMeta, on facebook.comMeta’s own advertising cookie, sent only if your browser already has it and allows it on other sites. We can’t read or delete it.90 days
resoflow.adClick (local storage)ResoFlow, for Google AdsKeeps the click reference from the Google advert you arrived from, so that if you sign up a venue — even in another tab — we can tell Google Ads that advert led to a sign-up. Only if you accept analytics and advertising cookies, only on our own website. Deleted when you turn advertising cookies off.90 days, or until your venue is created

Google ad measurement works only on our own website and sign-up pages. It reports that a new venue signed up and the type of business it chose, later (from our own servers) that the venue first paid us (never how much), and — with your yes — a one-way scrambled copy (a hash) of the email address you signed up with, which Google uses only to match the sign-up to the advert you clicked; never your name, phone number or anything about a venue’s guests, and never used to show you personalised adverts. What it sends to Google Ads is in our Privacy Policy (section 6). Google Analytics works for us; Google Ads works under Google’s own terms (see how Google uses information from sites that use its services).

The Meta pixel works only on our own website (never our sign-up pages, the dashboard or any venue’s pages) and only after you accept advertising cookies. What it sends to Meta, and how Meta uses it, is in our Privacy Policy (section 6).

Tagged links. Our Google adverts link to our site with a campaign label and Google’s click reference in the address — part of the link, not a cookie; analytics reads them only if you’ve accepted analytics, and only if you also accept advertising cookies do we keep Google’s click reference on your device, for up to 90 days (resoflow.adClick), so a sign-up finished in another tab still counts. Our marketing emails and texts contain no tracking pixel, so opening one is never recorded; their links may be tagged so the sender sees which link was clicked. Unsubscribe with the link in any marketing email or text.

Cloudflare Web Analytics — page-view counts and load times on resoflow.co.uk, used only with your Analytics yes. Cloudflare receives the page address, a rough country and the browser type, and shows us totals only. It doesn’t follow you across sites.

Sentry — error tracking that stores nothing on your device, so it needs no consent. On signed-in screens only (the dashboard, staff portal and our admin panel), it may keep a short replay around an error, with all text, form entries and media masked. Replay never starts on our public, sign-up or guest pages, though one already running may carry on if you move to one in the same tab.

4. Essential storage (always on)

All of these are part of the one always-on Essential category. Apart from the items our providers set, they are set by ResoFlow, stay on your device (or prove something to our servers), and are never used to track you. Session storage goes when you close the tab; local storage stays until it is removed as described below, or until you clear your browser.

Set by our providers

  • Stripe — cookies on the pages that take a payment (booking, tickets, gift cards, Order & Pay, payment and card links, sign-up’s payment step and billing), and on js.stripe.com, for payments and fraud checks.
  • Cloudflare — cookies and short-lived challenge tokens (including on challenges.cloudflare.com) for its Turnstile bot check on our public forms, and for Firebase App Check, which proves requests come from our app.
  • Firebase Authentication — keeps you signed in (mostly in local storage).
  • Firebase Cloud Messaging — firebase-messaging-database (IndexedDB): this device’s push token, only if alerts are turned on.

Each provider controls its own cookies under its own policies; see the list in our Data Processing Agreement.

Videos on a venue’s website load from YouTube or Vimeo only when you press play; from then their own cookies apply.

Set by ResoFlow

  • Signing in and security — keeps you signed in (on a venue’s pages, through “Keep me signed in on this device for 30 days”, ticked unless you untick it), remembers a computer you said is yours, stops the security check repeating, signs out idle or copied sign-ins and tells your other tabs why, remembers which of your venues this device has open, and proves a device is a staff device, an approved display screen or a demonstration venue we gave you (on staff portal pages this includes a cookie). Our servers keep only scrambled copies of the sign-in tokens and proofs. How long: until you close the tab or sign out, after 30 days (or 30 days unused) or when the venue removes the device; some items for up to a year, or, like a random device ID, until you clear your browser.
  • Bookings, orders and a venue’s pages — what you’ve typed into a booking, gift card or ticket form (including any allergy notes), your order basket and how you chose to order, the venue’s details so its pages open at once (on a waitlist status page, also your first name, party size, time and status), a loading screen or prompt you’ve seen or closed, and a random value (no personal information) that our servers turn into a one-way fingerprint to stop misuse of public pages, kept with a few records such as an order. How long: mostly until you close the tab; the basket 3 hours after your last change; the random value and a closed prompt until you clear your browser.
  • Staff devices and screens — how this device’s staff screens are set up and kept steady (display boards, Orders screens, the scanner, sounds, tips, dismissed alerts and the staff role being previewed) and, if alerts are on, push alerts: a small service worker that only shows alerts and never caches pages, the venues this device gets alerts for, the personal rota pages this phone gets alerts for (each page’s own link, so tapping an alert opens the right page), and the app icon’s badge number. How long: until you change them, alerts are turned off, the venue removes the device or you clear your browser; some only until you close the tab, or for 30 days.
  • Your preferences and unfinished work — light or dark look, time format and how dashboard and admin pages are laid out; tours, tips, cards and banners you’ve seen or closed; unfinished forms, so a reload doesn’t lose them; the dashboard search box’s recent searches (which can include a guest’s name — on a shared staff device they are wiped when you sign out); quick copies that keep pages fast and steady; and your cookie choices (the cc_cookie cookie, about 6 months). Mostly kept per person, so two people on one device keep their own. How long: until you change them or clear your browser; much of it only until you close the tab, and most unfinished forms until you finish or discard them, or 30 days.
  • Sign-up, setup and codes from links — a promo, referral or loyalty invite code from a link, the plan, billing period and products you picked, your answer to the UK-business question, the name and type of venue you told Rezo in our website chat (if you press Start free there), your place in the first setup screens, and a setup code we gave you, until sign-up, joining or setup uses them. How long: until you close the tab (a setup code’s place a little longer, so a reload carries on).
  • Help and support chat — keeps a chat with Rezo or our team (its reference, an access value, the email you gave and what you’ve read) and a support conversation’s messages and attachment links on screen after a refresh. How long: until you close the tab or sign out; a chat passed to our team before you’ve given an email, a few days so you can come back for our reply.

Names may change as we develop ResoFlow. To ask about a particular item, contact us (section 6).

5. Changes to this policy

We update this policy when we add, remove or change cookies or similar storage. The “Last updated” date shows the latest version.

6. Contact us

Questions about cookies: [email protected]. For the full picture, see our Privacy Policy.