This policy explains the cookies Revasi sets when you use our booking platform or visit revasi.net. We keep this short.
1. What are cookies
Cookies are small text files stored on your device when you visit a website. They allow the site to remember information about your visit — such as your session state — so you don’t have to re-enter information on every page.
2. Cookies we use
We use essential cookies to run bookings and sign-in, and a small number of analytics cookies to understand how our site and booking pages are used. Advertising cookies are used in two places: on revasi.net, to measure Revasi’s own Google ads, and at venues that measure their Google ads, only after you allow it on that venue’s booking page. We never sell your data.
Cookie name
Purpose
Duration
Set by
sb-*-auth-token
Keeps your session active during the booking process
Session / up to 1 week
Supabase
better-auth.session_*
Keeps you signed in to your Revasi account. Set only when you sign in, and removed when you sign out.
180 days, renewed while you use it
Revasi
revasi-operator.*
Keeps restaurant staff signed in to the admin panel, and remembers a device they chose to trust for two-step verification. Set only when staff sign in.
Sign-in: 2 days without use, renewed while in use. Trusted device: 30 days
Revasi
sidebar:state
Remembers whether the admin sidebar is open or closed
7 days
Revasi
revasi_attribution
Records which link or page brought you to a booking page, so the restaurant can see which of its campaigns are working. Contains no personal details.
30 days
Revasi
revasi_ad_consent
Remembers your answer to a venue’s ad-measurement question, so you are not asked again. Holds only the venue and your answer.
180 days
Revasi
revasi_ad_click
Only after you allow ad measurement: the reference of the Google ad you clicked, so the venue can see which ad led to your booking.
90 days
Revasi
_gcl_*
Only at venues that use Google Ads, and only after you allow it: links your booking to the ad you clicked.
Up to 90 days
Google
rvm_*
On revasi.net only: links a demo request or a WhatsApp message to the Revasi ad you clicked. Not set in the EEA, the UK or Switzerland.
Up to 90 days
Google
_clck, _clsk
Measures how pages are used, so we can fix what is confusing
Session / up to 1 year
Microsoft Clarity
ph_*
Counts page views and booking steps so we can see where the booking flow loses people
Up to 1 year
PostHog
We also store up to two entries in your browser’s local storage. revasi_first_touchremembers the first page you arrived on so we can tell which of our pages lead to enquiries. If you arrived from one of Revasi’s Google ads, revasi_marketing_ad_click keeps the reference of that ad for 90 days, so a demo request can be linked to it. Neither holds contact details, and both are cleared when you clear your browser data.
3. Cookies we do not use
Retargeting cookies, or any advertising cookie other than the Google Ads measurement described below
Social media tracking cookies
Third-party profiling cookies
Cookies that sell your data
4. Ad measurement with Google Ads
On revasi.net.Revasi advertises on Google to reach venues. When you arrive from one of those ads, Google’s tag may set its rvm_*cookies. If you then request a demo, we keep the ad click reference with your request and send Google a record of it, with a scrambled (hashed) copy of your email address. A tap on one of our WhatsApp links is counted too. In the EEA, the UK and Switzerland the tag sets no cookies and we keep no ad click or email address; Google receives only signals that carry no cookie, with ad identifiers removed. Ad personalisation stays off everywhere. These cookies are separate from the ones below, and venues’ booking pages do not use them.
At venues that use Google Ads.Some venues advertise on Google and want to know which of their ads lead to bookings. On those venues’ booking pages we ask you first. Until you answer, Google’s tag loads with advertising storage switched off: it sets no cookies and sends Google only signals that carry no cookie or identifier.
If you allow it, Google’s tag may set its _gcl_* cookies, and when you book we send the venue’s own Google Ads account an ad click reference, the booking time and value, and a scrambled (hashed) copy of your email address and phone number. If you decline, nothing about the ad is stored or sent. Ad personalisation stays off either way.
5. Managing cookies
Most of what we set is essential to the booking flow and cannot be switched off without breaking it. Ad measurement at venues that use Google Ads needs your permission, which is asked on that venue’s booking page and can be cleared above. Measurement of Revasi’s own ads on revasi.net is not asked for; you can stop it by blocking or clearing cookies for revasi.net in your browser.
You can delete cookies at any time through your browser settings. Note that clearing session cookies will sign you out of your Revasi account, any active booking session, or an admin account.
6. Changes to this policy
If we introduce new cookies in the future, we will update this page and, where required by law, obtain your consent before setting them. The “Last updated” date below reflects the most recent revision.