Cookies

01

This site sets none

No analytics, no advertising pixel, no A/B test, no chat widget looking over your shoulder. So there is no banner asking for consent either: there is nothing to consent to.

That is a choice and not an oversight. We would rather not know how many people scroll halfway down the pricing page than put a pop-up in front of every visitor for permission to know it.

02

What does happen

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.

03

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.

04

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.

05

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.

06

Managing it yourself

Deleting or blocking cookies is possible in every browser under the privacy settings. Delete the session cookie and you are logged out. Nothing else changes, because there is nothing else.

07

Changes

If we ever do place something 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 hallo@skuply.io and are answered by somebody who builds the service themselves.