Cookie Policy

A cookie is a small text record a website asks your browser to keep and send back on later visits. Browsers also offer local storage and session storage, which a page can read but which are never sent with a request. This policy lists all three where Cliux uses them, because "cookie" alone would leave things out.

The sign-in and sign-up pages and the console load Clerk, the sign-in service, which keeps __client_uat and one item of its own settings in local storage even before you sign in, so it can tell whether you are. The rest of the Cliux site does not load Clerk; its header only reads __client_uat, when Clerk has set it, to show "Dashboard" instead of "Sign in". Everything else is written only when you do something that needs it: answering the cookie notice keeps your answer as cliux.cookieChoice, a first message sent to the help chat without being signed in sets __Host-cliux_help, a chat handed to the support team keeps one item in local storage, and working in more than one workspace in the console sets __Host-cliux_workspace, so you sign in to the last one you opened. Signing in sets the other sign-in cookie below, opening a plan's payment form on the console's billing pages loads Stripe's payment script, which sets two cookies of its own, a password-protected preview link sets one more, and the editor and a few console tools keep the items below while you use them.

Clerk may also set short-lived helpers whose names start with __clerk_ while a sign-in is in progress. We do not count page views on this site. For one visit in ten we also measure how fast the page loaded: its timings, its path, how it was opened (for example by a link, a reload or the back button) and the kind of device and connection, sent once, with no cookie, no identifier and nothing stored on your device. We ask before measuring: the notice puts Reject all beside Accept all, nothing is measured until you choose, and refusing is a real refusal, not a dismissed notice. You can change your answer at any time from Cookie settings in the footer.

The first time you visit the Cliux site or console, a notice at the bottom of the page says what is stored. Cookie settings, in the footer of the Cliux site, on your profile in the console, and below, shows the same list and every choice there is to make. One choice exists: measuring how fast the marketing pages load, for one visit in ten. It is off until you allow it, the notice asks with Reject all beside Accept all, and nothing optional loads until you choose. Your answer is kept for 12 months, then asked again, and you can change it at any time.

Our own code on a published site stores something in your browser only for a feature of the page (a cart, a sign-in, a like, a welcome screen shown once per visit) or after you accept the site's consent banner; what the site's owner adds is described below. The site's own visit counting stores nothing in your browser: unless you have accepted the banner, our server tells a visit apart by a hash of your IP address and browser, made with the date and with a secret that is never written down and is replaced whenever the server restarts, so the hash is new every day. The hash is kept with the visit for the site owner's analytics and your IP address is not; once the secret has been replaced, the hash can no longer be linked to your IP address or to another day's visits. What a site may store:

If the site's owner has added a Google Analytics or Meta Pixel id, those services set their own cookies. While the site's consent banner is on, they load only after you accept it; declining is a real refusal and the answer is kept in the item above. The banner is on for every site to begin with, but its owner can switch it off in the site's settings, and then those services load, and set their cookies, without asking you. What a site owner collects through their own forms and store is described in that site's notice, not here.

A video (YouTube or Vimeo), a map (Google Maps) or a music player (Spotify, SoundCloud or Apple Music) on a published page is not loaded with the page. It shows a box saying whose content it is, and loads only when you press its button; from then on that company receives your visit under its own policy. A site's fonts are served by the site itself, so loading them does not contact Google.

Clerk sets the sign-in cookies named above under its own policy, and its sign-in service runs behind Cloudflare, which sets short-lived bot-protection cookies (such as __cf_bm) on Clerk's own address, not on ours. Stripe's payment script, which loads when you open a plan's payment form on the console's billing pages, sets the two Stripe cookies named above to prevent fraud; that form is Stripe's, shown inside the billing page. Some other payments in the console open Stripe's own checkout page instead, which runs under Stripe's policy. No advertising network and no cross-site tracker is loaded by the platform. On a published page, the videos, maps and music players described above load only when you ask for them; anything else the site's owner places on a page from another company's address, such as an embedded website, a pasted code snippet, or a photo or video file hosted elsewhere, loads with the page, and that company receives your visit under its own policy.

Your browser can block, delete or warn about cookies and site data. Blocking the sign-in cookies means you cannot stay signed in to the console; blocking the chat cookie means a live-chat conversation does not follow you between pages; blocking __Host-cliux_help means the help chat forgets your conversation when you move to another page; blocking the site's storage means the cookie notice returns on every visit, because your answer to it cannot be kept. Nothing else on this list is needed for a page to work.

Questions about this policy go to [email protected], or through the contact form. When the list above changes, the date at the top changes.