First-draft policy
This document is a working first draft prepared so PIKL can run an early-access programme with reasonable transparency. A solicitor will review and finalise the binding version. If you spot anything that looks wrong, contact us and we will get the right person to look at it.
01. What this notice covers
This notice explains how PIKL uses cookies and similar storage technologies — like browser localStorage entries — on the website at pikl.app and in the apps that link to this notice. It sits alongside our privacy notice; the privacy notice covers personal data more broadly.
Where this notice talks about “cookies”, we usually mean cookies and similar technologies together. For consent purposes, the rules under the UK Privacy and Electronic Communications Regulations (PECR) and UK GDPR apply to both.
02. How we group cookies
We split cookies into two categories. The PIKL cookie banner asks for consent for the second category before any cookie in it is set.
| Category | What they do | Consent |
|---|---|---|
| Strictly necessary | Sign-in tokens, security tokens, basic UI state, and the cookie banner's own preferences. | Always on. Required to deliver the Service. |
| Analytics | Aggregated usage data we use to improve the platform. Vercel Analytics and Mapbox usage telemetry. | Off until you opt in. |
No advertising trackers
03. Strictly necessary cookies and storage
These keep PIKL working. We do not need consent for them under PECR. You can block them in your browser, but the site will not work properly if you do.
| Name | Provider | Purpose | Lifetime |
|---|---|---|---|
| sb-* (e.g. sb-access-token) | Supabase | Keeps you signed in across pages and reloads. HttpOnly, set server-side. | Up to 7 days; refreshed each time you use the site. |
| sidebar_state | PIKL | Remembers whether the player sidebar is collapsed or expanded. | 1 year. |
| pikl.cookie-consent.v1 | PIKL | Stores your cookie preferences so we don't ask again. localStorage entry. | Persistent until you clear it. |
| __cf_bm | Cloudflare (via service providers) | Bot-management cookie set by Cloudflare-fronted services we rely on. Only appears once you reach those services. | 30 minutes. |
| stripe-mid (only on payment pages) | Stripe | Payment-fraud prevention when you pay through PIKL. | Up to 1 year. |
04. Analytics cookies and storage
We only set these once you click “Accept all” or turn analytics on in the cookie preferences. They help us see which pages and search journeys help players, and which are getting in the way.
| Name | Provider | Purpose | Lifetime |
|---|---|---|---|
| _vercel_va, va | Vercel Analytics | Privacy-friendly page-view counts. We do not receive any personally identifying data from Vercel Analytics. | Session. |
| mapbox.eventData.uuid: / mapbox.eventData.uuidTimestamp: | Mapbox | Mapbox sets these when the map loads to attribute usage to PIKL for billing and to detect abuse. localStorage entries. | Persistent. |
| algolia-client-js-* | Algolia | Anonymous client identifier so search analytics work and to protect against abuse. localStorage entry. | Persistent. |
When you switch analytics off, we stop loading the Vercel Analytics script. Mapbox and Algolia entries are set by their SDKs; the easiest way to remove existing values is to clear site data for pikl.app in your browser. Going forward, when consent is off, our map and search calls run with usage telemetry minimised.
05. Third-party services that may set cookies
Some PIKL features rely on third-party services. When you use a feature that loads one, that service may set its own cookies. The ones to be aware of:
| Service | When it loads | Their privacy policy |
|---|---|---|
| Stripe | When you make or take a payment. | stripe.com/privacy |
| Stream | When you open a chat or activity feed inside PIKL. | getstream.io/privacy |
| Mapbox | When the discover map or any embedded map loads. | mapbox.com/legal/privacy |
| DUPR | When you link a DUPR account to your PIKL profile. | mydupr.com/privacy |
These services act as separate controllers for the data they collect through their own cookies. Their privacy policies cover how they use that data.
07. Changes to this notice
When we add a new cookie or technology, this notice will change. The “Last updated” date at the top reflects the latest version. Where a new category requires consent, we will reset stored preferences and ask again through the banner.
08. Contact
For questions about cookies or how we use them, email privacy@pikl.app.
Contact
DRFT Solutions Ltd, the company behind PIKL, is registered in England and Wales. For questions about these terms, write to legal@pikl.app. For privacy and data-protection questions, write to privacy@pikl.app.