Cookie policy
Effective REPLACE_WITH_EFFECTIVE_DATE. Last updated REPLACE_WITH_EFFECTIVE_DATE.
The short version
This site sets no cookies at all. There is no consent banner because there is nothing to consent to, and no settings panel because there is nothing to switch off.
The one thing we store in your browser
When you first arrive, a short animation plays: a bullet crosses the screen and draws the line under the navigation. It is meant to be seen once, not replayed every time you click through to another page.
So the site writes a single entry called sb-intro-seen to
session storage, which records that the animation has played.
That is the whole content — a flag. It holds no identifier, nothing about
you, and nothing that could be joined to anything else.
Session storage is not a cookie. It is never sent to our server, it cannot be read by any other site, and the browser discards it the moment you close the tab. If your browser blocks it, the site notices and carries on; you simply see the intro again.
What other companies see
The site loads three JavaScript libraries from two public content delivery networks, cdnjs (operated by Cloudflare) and jsDelivr. Requesting a file from them discloses your IP address and user agent, as any web request does. We do not set cookies through them and receive nothing back. Their own policies govern what they do with that request.
Why there is nothing to configure
Cookie settings panels exist to let you turn off analytics and advertising trackers. This site runs neither, so a panel would be a control with nothing behind it. The privacy policy sets out what little we do collect.
If this changes
Adding analytics or an advertising pixel would change this page and, most likely, require a real consent mechanism before it went live. We would update this page first, not afterwards.
Contact
REPLACE_WITH_LEGAL_ENTITY, REPLACE_WITH_BUSINESS_ADDRESS. REPLACE_WITH_PRIVACY_EMAIL.