Cookies

01

One question, and we ask it up front

This site sets nothing before you have said yes. No advertising pixel, no A/B test, no chat widget looking over your shoulder. What we do want to know is which pages get read, and for that we use Google Analytics. That sets a cookie, so we ask permission for it.

Say no and not a single request goes to Google, and the site works exactly the same. We do not load the script beforehand and we do not park it in a holding pattern: on no, literally nothing happens. Decline sits next to accept and not underneath it, and there is no cross that quietly counts as yes.

02

What sits there if you say yes

Two cookies from Google Analytics, and nothing else. We have switched off advertising features and Google signals: we measure visits, we do not build an audience, and we link this measurement to no advertising platform at all.

03

Advertising is a second question

We advertise, and an advertising platform then wants to know whether someone who received the ad had been here before. That needs a pixel, and a pixel sets a cookie. That is a different purpose from counting how many people read a page, so we ask about it separately. Saying yes to measuring is not a yes to advertising, not even if you said it earlier.

Say no and the pixel is not loaded and no request goes to the platform at all. You get the same site, the same price and the same answers. We do not link this pixel to the page measurement and not to your catalogue.

04

What happens either way

The server sees what every server sees: an IP address, a time and which page was requested. That sits in the server log, we keep it for seven days and use it only to see whether something is broken. That needs no cookie and therefore no consent.

We also count how many people read which page, using our hosting party's built-in counter. It puts nothing on your device, reads nothing from your device and does not follow you to other sites. No visitor profile comes out of it and the measurement goes to no advertising platform. That is why it sits here and not behind the question: there is nothing to refuse that we would store on you. If you still would rather not, any common blocker stops it and the site works exactly the same.

05

One exception: the typefaces

We load Archivo and Geist Mono from Google Fonts. That means Google sees your browser’s IP address, and that is a processing we have to be straight about. No cookie is set, but the request does leave the building.

This ought to be self-hosted. Then that request stays in too. It is on the list.

06

The app sets one

Anyone logging in to the app gets exactly one cookie, and it remembers that you are logged in. Without it you would have to fetch the link from your mail on every click.

07

Why that needs no consent

A cookie strictly necessary to deliver a service the user asked for themselves is exempt from the consent requirement. Logging in is exactly that case. We use that cookie for nothing else, and there it ends.

08

Changing your mind

Your choice is not fixed. Ask me again

Choose no and the measurement stops from that moment. The cookies already sitting there you delete in your browser, under the privacy settings. Delete the app session cookie and you are logged out.

09

Changes

If we ever place anything else that is not strictly necessary, the consent question comes first and the cookie after. Not the other way round. And this page is updated before it takes effect.

Questions about this go to hi@skuply.io and are answered by somebody who builds the service themselves.