The short version
- We set only the cookies this site needs to work: they keep you signed in and protect forms.
- There are no advertising, analytics or tracking cookies, so the site shows no cookie banner.
- You can block or delete cookies in your browser, but then sign-in and forms stop working.
What cookies are
A cookie is a small text file that a website stores in your browser. Cookies let a site recognize your browser from one page to the next, for example to keep you signed in. Similar technologies, such as your browser’s local storage, work in a comparable way, and this page covers them too.
The cookies we set
These are all the cookies the Service sets. The first two are set when you open any page, because forms such as sign-in and the contact form need them.
| Name | What it does | Lasts | Needed? |
|---|---|---|---|
brown_ | Keeps you signed in and holds short-lived information for the page you are on, such as a security token and form messages. | 2 hours after your last visit | Yes |
XSRF-TOKEN | Lets our forms and buttons prove that a request really comes from our own pages, which protects you from forged requests. | 2 hours after your last visit | Yes |
remember_web_… | Keeps you signed in on this device. It is set only if you tick “Remember me” when you sign in. | Up to 400 days | Only if you choose it |
Websites that run on Linx
A fulfillment center can run a website on Linx, at an address of its own. A visitor who only reads it gets no cookie at all. Cookies are set there only when someone signs in:
- The owner of the website, and a storefront that signed up on it, get a session cookie named
__Host-panel, and the form-protection cookieXSRF-TOKEN(as in the table above), on that website’s address only. They keep a person signed in to the admin there for 2 hours after the last visit. They are needed to sign in, they are never shared with another address, and “Remember me” is not offered there. - A person who has an account on the website itself (not an account of Linx) gets a cookie named
__Host-sitewhile they are signed in to that account.
What we do not use
We do not use advertising cookies, analytics or tracking cookies, social-media plug-ins or browser fingerprinting.
Every cookie in the table is needed to deliver the Service you asked for or to keep it secure, so we do not ask for your consent for them, and the site shows no cookie banner. If we ever add anything else, we will ask for your consent first and update this page.
Browser storage
The workspace remembers your color theme (light or dark) and the state of its side menu in your browser’s local storage. This stays on your device: it is not sent to us, and you can clear it in your browser at any time.
Content from other companies
Pages of the Service load typefaces from Google Fonts and Bunny Fonts and, where the personalizer needs it, an open-source graphics library from jsDelivr. These providers do not set cookies for us, but your browser contacts their servers, so they see your IP address and browser details. The Privacy Policy lists them.
Our network provider, Cloudflare, may also set a short-lived security cookie (for example one named __cf_bm or cf_clearance) when it needs to tell people from automated traffic. It is used for security only and not to follow you from site to site.
Managing cookies
Your browser lets you see, block and delete cookies; how you do it depends on the browser, so search its help for “cookies”. If you block the cookies in the table above, you will not be able to sign in and forms such as the contact form will not work. Deleting them signs you out.
Changes and contact
If the cookies we use change, we will update this page and its date. Questions: use the contact form and choose “Privacy or data request”.