✓Cookies

Cookies, just the essentials.

What we set, what it is for, and how to turn the optional ones off. No advertising trackers and no data brokers.

Last updated ยท 24 October 2026
Plain English. We use cookies to keep you logged in, remember your preferences, and (anonymously) understand which pages are useful so we can improve them. We don't use cookies to track you around the web for advertising.

A small text file your browser stores when you visit a website. It can hold a login token, a setting, or an identifier so the site knows it's you on the next page. Modern sites also use similar mechanisms (localStorage, sessionStorage) that we group under "cookies" here for simplicity.

Cookies we set

Strictly necessary

Always on. The site does not work without these and the law does not require consent for them.

  • blinki-cookie-consent - the choice you made in the cookie banner, so we do not ask again. Kept for 365 days.
  • __session - only on a password-protected staging link to a website that is not yet published, so the page knows you have the password. Kept for 12 hours.
  • Signing in to the dashboard does not set a cookie: Firebase Authentication keeps your sign-in in your browser's own storage, for the session or until you sign out.
  • Dashboard pages load Stripe, our payment provider, so that a card can be taken. Stripe sets __stripe_mid (one year) and __stripe_sid (30 minutes) for fraud prevention. These are Stripe's cookies, under Stripe's privacy policy.

Analytics

None. We do not run an analytics tool on blinki.co.uk or the dashboard.

Websites published on Blinki

A website published on Blinki carries a small counter of ours so its owner can see visits, pages read and taps on their phone number, email address and map link in their dashboard. It sets no cookies and involves no third party. A visitor is told apart on our server by a one-way hash of their internet address and browser made with a secret we hold, and the address itself is never stored. The only thing kept in the visitor's browser is two session-only markers (_bk, _bkp) that vanish when the tab closes.

If the website has its own cookie banner, the counter can be held back until the visitor accepts statistics. Put this in the page before our script:

<script>window.BLINKI_TRACK = false;</script>

and call window.blinkiTrack() when the visitor accepts (on load if they already have). Until then nothing is stored or sent. Anything the website owner adds themselves, such as a Google tag or a Meta pixel through their site settings, is theirs and sets its own cookies.

Cookies we don't set

No Facebook Pixel. No Google Ads remarketing. No third-party advertising cookies. We don't sell, share or buy advertising data.

Controlling cookies

You can clear cookies in your browser at any time, or block them entirely. Most browsers also have a "delete on close" mode. Note that if you block strictly-necessary cookies, the platform's login won't work.

To change or withdraw your choices, use the button below - it is the same panel you saw when you first arrived. Turning a category off reloads the page so anything already running stops.

blinki-cookie-consent cookie.

Changes

We update this page whenever we add or remove a cookie. The "last updated" date at the top tells you when. For broader privacy questions, see the privacy notice.

Contact

Questions about cookies: privacy@blinki.co.uk.

Changed your mind about cookies?

You can change what you allow at any time, and nothing on this site needs the optional ones to work.