Cookie policy

01The short version

02What cookies are

A cookie is a small text file a website asks your browser to store, so it can recognise your device on a later visit. Similar technologies — local storage, session storage, tracking pixels, device fingerprinting — do comparable things by other means, and European law treats them broadly alike: storing information on your device, or reading information already there, generally needs your consent first.

There are narrow exceptions. Consent isn’t needed where the storage or access is purely to transmit a communication, or where it’s strictly necessary to provide a service you explicitly asked for. Dutch law adds a further exception, in Article 11.7a(3) of the Telecommunications Act, for measuring how a site is used where the privacy impact is minimal. Where we rely on an exception, we say so and explain why.

03Cookies we set

None. As of the date at the top of this page, poks.app sets no cookies of any kind — not functional, not analytical, not advertising.

If that changes, this table gets filled in — every cookie named, with its purpose and lifespan — before the cookie goes live.

04Other device storage

We don’t use local storage or session storage either, and we don’t fingerprint your device. The small amount of JavaScript on the page handles visual behaviour only — scrolling, animation, video playback — and stores nothing about you.

Your browser will cache the page’s images, video and fonts so the site loads faster next time. Caching is your browser’s own doing, it’s necessary to deliver the page you asked for, we can’t read it, and you can clear it from your browser settings whenever you like.

05How we measure visits

We don’t. There’s no analytics on this site at all — no Google Analytics, no cookieless alternative, no heatmaps, no session recording, nothing counting your visit.

The only record that you visited is the ordinary server log our infrastructure provider generates in order to serve the page, described in the privacy policy. We don’t read those logs to study visitor behaviour and we don’t build reports from them.

06Third parties your browser contacts

No cookies doesn’t mean nothing leaves your browser. Loading any web page means requesting files, and a request reveals your IP address to whoever serves it. Here’s every server this page talks to — one of them ours, one of them genuinely a third party:

The videos and images on the site are served from our own server, not from YouTube, Vimeo or any other embedded player — so watching them tells nobody but us.

We plan to serve the fonts from our own server too, so that Google receives nothing at all. Until that’s done, this table is the accurate picture, and you can block third-party requests with your browser or an extension if you’d rather not wait for us.

07The waitlist form

Joining the waitlist sets no cookie. When you submit the form, your first name and email address are sent to our database, which runs on Supabase in Stockholm, Sweden, and are used for one thing: emailing you a link to join the beta when it opens. Nothing about you is stored until you actually submit the form. Full detail, including how to have it deleted, is in the privacy policy.

08How to control cookies

There’s nothing here to switch off, but your browser gives you the controls regardless — every major browser lets you block or delete cookies, block third-party requests, and clear stored site data. Look under Settings → Privacy in Chrome, Safari, Firefox or Edge.

Blocking third-party requests on this site may mean the page loads in a fallback typeface. Nothing else breaks.

09If this changes

We’d only add cookies for a reason, and if we ever add any that aren’t strictly necessary, this is the commitment:

• Consent comes first. Nothing non-essential loads before you agree — not on page load, not on scroll, not on a click somewhere else.
• Refusing is as easy as accepting. Equally visible buttons. No pre-ticked boxes, no dark patterns, no cookie wall.
• You choose per purpose. Analytics and marketing are separate decisions, not one bundle.
• No nagging. If you say no, we don’t ask again for at least six months. That’s our own commitment, not a rule we’re obliged to follow.
• Withdrawal is one click, from a link that stays available on every page.
• This page gets updated first, with every cookie named and its lifespan listed, before anything goes live.

10The rules we’re following

• Regulation (EU) 2016/679 — the General Data Protection Regulation
• The Dutch Uitvoeringswet AVG (UAVG), which implements the GDPR in the Netherlands
• Article 11.7a of the Dutch Telecommunicatiewet — the Dutch cookie rule
• Directive 2002/58/EC — the ePrivacy Directive, as amended

The EU is currently negotiating changes to how cookie consent works. Nothing there is settled law yet, and if it lands we’ll update this page — the commitments in section 9 are written to meet or exceed what’s under discussion.

11Contact

Related: privacy policy.