Legal document
Cookie Policy
This Cookie Policy explains which cookies and similar technologies Bisux Limited ("we", "us", "our") uses on bisux.com and in the Bisux dashboard, why we use them, and how you can change your choices. Restaurant websites built with Bisux have their own cookie information.
What are cookies?
Cookies are small text files that a website stores in your browser. Similar technologies include browser storage (local storage and session storage), pixels, and information your browser sends when it loads content from another service. In this policy, "cookies" covers all of these.
Some cookies are strictly necessary for the service you ask for, such as signing in. We can use those without asking. All other cookies need your consent first.
1. Your choices
We use one optional type of cookie: advertising cookies. Accepting them allows three things, only on a few pages:
- Meta's cookies and the Meta Pixel, which measure our Facebook and Instagram ads;
- sending Meta details of your visit and, for preview requests, waitlist sign-ups and claims, a hashed version of your email address, so that Meta can match the event to a Meta account and measure and improve our ads;
- our own use of the private preview cookie to count how visitors from our ads move through our preview pages.
When we ask, you can choose Accept all, Reject all or Preferences. On some pages the same choice appears in a window in the middle of the screen. Closing the banner or window, scrolling or continuing to browse is not consent. If you reject, everything still works.
How to change or withdraw your choice
- Click Cookie settings at the bottom of our public pages that use advertising cookies, or the Cookie settings button at the top of this page. In your dashboard, Legal › Cookies brings you here.
- Turn advertising off and click Save preferences.
When you withdraw, we stop sending data to Meta, stop recording your preview journey steps and delete Meta's cookies from your browser where we can. Data already sent cannot be recalled. To ask about data already sent, see our Privacy Policy.
We remember your choice for 180 days. After that, or if you clear your cookies, we treat you as undecided. We never treat "undecided" as consent. If we change what advertising cookies are used for, we ask you again.
2. Cookies we need
The sign-in, security and requested-feature cookies below make Bisux work. They do not need optional consent when limited to what is necessary for the feature you request. Support storage is explained separately below.
Signing in
- jwt: keeps you signed in. Lasts for a short session (up to 24 hours), or up to 30 days if you choose to stay signed in.
- RememberMe: remembers that you chose to stay signed in. Up to 30 days.
- recovery_jwt: lets you finish recovering access to your account. Up to 15 minutes.
- .Bisux.ExternalAuth.v2 and .Bisux.GoogleCorrelation.v2…: used while you sign in with Google. The temporary sign-in ticket lasts up to 20 minutes; the correlation cookie lasts for the sign-in flow under the Google sign-in handler.
- .Bisux.GoogleBusinessProfile.External.v1 and .Bisux.GoogleBusinessProfile.Correlation.v1…: used while you connect your Google Business Profile. The temporary ticket lasts up to 10 minutes; the correlation cookie lasts for the connection flow under its handler.
Security
- .Bisux.Antiforgery.v2: protects forms against attacks from other websites. Ends when you close your browser.
- .AspNetCore.Session: keeps short-term information between pages. The cookie lasts for the browser session; the server-side session state expires after 60 minutes without activity.
- Cloudflare Turnstile: the security check on some forms is loaded from Cloudflare, which may store information in your browser for that check only.
Free preview and sign-up
- bisux-landing-…: gives your browser private access to your preview, using a protected access reference. We set it when you send a preview request. Lasts 7 days, or until your preview expires. If you accepted advertising cookies, we set it when you first open the page instead, and also use it to count your journey steps (section 4).
- onboarding_request: remembers the plan you picked before signing in. Lasts 7 days.
- download_token_…: shows the progress of a menu download. Lasts while the download runs.
Support chat in your dashboard
When the support chat is available in your dashboard, the chat software (Chatwoot, which we host ourselves) uses:
- cw_conversation and cw_user_…: keep your support conversation linked to your signed-in account, so you can see your earlier messages and our replies. The dashboard resets its chat binding when the account or chat session changes. These cookies maintain continuity across visits; clearing browser cookies removes them.
- bisux.chat.owner.v1 (local storage): binds the chat to the account and inbox. It has no automatic expiry and is reset when that binding changes.
- bisux.chat.open.v1 (session storage): remembers whether the chat is open in this tab, until closed or reset or the tab session ends. The chat window may also keep conversation state.
The chat can identify your account when it loads, before your first message. Its storage serves support continuity and account separation, not statistics or advertising. The exemption from optional consent applies only to storage necessary for support you request. The support chat is not loaded on public pages or restaurant websites.
Your cookie choice
- bisux_optional_consent: stores your choice, the date and a random reference that links the choice to our record of it. It does not contain your name, email or IP address. Lasts 180 days.
3. Preference cookies
These remember choices you make. They do not need optional consent when used only to remember the preference you request.
- preferred_language: your language. Lasts 1 year.
- dashboard_portal_id and dashboard_analytics_portal_id: the restaurant you last selected in your dashboard. Last 30 days.
- Browser storage: the dashboard and menu editor remember layout, open sections, scroll position and whether you dismissed the app install prompt. Layout and dismissal choices use local storage until reset or cleared; scroll and editing context use session storage until consumed, cleared or the tab session ends.
4. Advertising cookies (optional)
Used only if you accept advertising cookies, and only on our restaurant landing pages (including the review page after you send a request), our waitlist page, and one view of your dashboard after you claim your website or pay. Never on restaurant websites, checkout or payment pages, or pages whose web address contains a private access link.
- _fbp (Meta): recognises your browser so Meta can measure our ads. Typically up to 90 days, subject to Meta’s browser settings.
- _fbc (Meta): set only if you arrived by clicking one of our Meta ads. Links that click to a later result. Typically up to 90 days, subject to Meta’s browser settings.
- Meta Pixel and Conversions API: tell Meta when you view one of these pages, send a preview request or join our waitlist, claim your website or start a paid subscription. With the pixel, Meta's automatic advanced matching may read contact details you type into forms on these pages and send them to Meta in hashed form; Meta may also read page information such as titles and do part of its measurement on your device. Our server sends Meta your IP address, browser type and, for requests, waitlist sign-ups and claims, a hashed version of your email address and of our internal reference for you.
- bisux-landing-checkout (Bisux Limited): set only if you accept advertising cookies when you claim your website from one of our restaurant landing pages. It marks that claim, so that one view of your dashboard can report the claim or a later payment to Meta. It holds a protected reference to your request and account. Lasts 7 days. If you withdraw, we stop reading it and it expires by itself.
- Preview journey statistics (Bisux Limited): on our restaurant landing pages, we use the bisux-landing-… cookie (section 2) to count which steps of the preview journey you reach and which campaign brought you. This information stays with us and is not sent to Meta.
Our Privacy Policy explains what is sent to Meta and our joint responsibility with Meta.
5. Content from other services
Some pages load content from other services. Your browser then sends those services your IP address and browser information:
- Cloudflare Turnstile: the security check on some forms.
- OpenStreetMap: the map and address search (Nominatim) in the free preview and the dashboard.
- Photon (komoot): address suggestions during sign-up.
- Stripe: the payment page, which runs on Stripe's own website under Stripe's cookie policy.
- Google: the Google sign-in page, if you choose to sign in with Google, under Google's own policies.
Our fonts, code libraries, profile pictures and QR codes are served from our own servers or created in your browser, so loading them sends nothing to other services.
6. Statistics without cookies
We count visits to our website without statistics cookies, and we keep anonymous daily totals for our preview pages that contain no identifier at all. Our Privacy Policy explains how.
7. Controlling cookies in your browser
You can block or delete cookies in your browser settings. If you block the cookies we need, signing in and other features may not work. Deleting cookies resets your cookie choice.
8. Changes
If we add a new optional use of cookies, we will update this policy and ask for your choice again.
Last updated: 10 November 2026
Company details
Bisux is operated by Bisux Limited, an Irish private company limited by shares.
Legal name
BISUX LIMITED
Registered office
51 Bracken Road
Dublin
D18 CV48
Ireland
Registered in
Ireland (Companies Registration Office)
Company registration number
816985
Contact
Privacy contact
For privacy matters, Bisux Limited is the controller for Bisux account, billing, support, security, marketing and website data. For reservations and other guest processing that a restaurant directs through its website, the restaurant is normally the controller and Bisux Limited its processor. Other activities have the roles described in our Privacy Policy.