Cookie Policy
This page lays out every cookie and adjacent browser-storage technology that runs on Kwiff, explains the role of each one, the period it persists on your device, and the steps for removing or restricting them. Broader questions around personal-data processing are addressed independently on the Privacy Policy page; the document you are reading is the technical counterpart. A general account of the project sits on the About page, and the flagship operator review can be found on the Kwiff Casino homepage.
1. A short explainer on what cookies actually are
A cookie is essentially a tiny text record that a site requests your browser to keep on the device. On any subsequent visit, the browser returns that record, which lets the site spot the returning session, hold on to a preference, or tally traffic. They have no ability to execute code on your hardware, no access to other files, and cannot pinpoint you as an individual without supplementary data already attached. Much of what gets loosely labelled "cookies" nowadays sits in adjacent storage layers — localStorage, sessionStorage and IndexedDB among them — and behaves in broadly the same fashion; for readability, the term "cookie" throughout this page is shorthand for the entire family.
2. Cookie types currently in use on this site
Kwiff Casino deploys three distinct cookie categories. On the first visit these are surfaced through the consent banner, and the selection can be revised at any moment via the link in the site footer.
| Category | Purpose | Consent required |
|---|---|---|
| Strictly necessary | Make the site work: load the page, remember your cookie-banner choice, route traffic, prevent abuse. | No (legal basis: legitimate interest) |
| Analytics | Anonymous, aggregated traffic measurement: which pages are read, where readers come from, which links are clicked. | Yes |
| Affiliate tracking | Recognise that a click through to an operator came from Kwiff so the partnership can be credited. | Yes |
Kwiff deliberately steers clear of any advertising or remarketing cookies. No display ads are served on the site, no programmatic ad networks are integrated, and readers are not pixel-tracked across third-party properties. The commercial model that keeps the site running is set out in full on the Affiliate Disclosure page.
3. Individual cookies, providers, and retention periods
What follows is the complete catalogue of cookies that can land on your device during a Kwiff visit. Third-party cookies originate from external services Kwiff integrates with; ultimate control over their behaviour stays with those providers, and direct links to their respective policies are supplied below.
| Name | Set by | Category | Purpose | Lifetime |
|---|---|---|---|---|
kwiffcasino_consent | Kwiff | Strictly necessary | Stores your cookie-banner choice so the banner does not reappear on every page load. | 12 months |
kwiffcasino_session | Kwiff | Strictly necessary | Anonymous session identifier used to load assets and rate-limit abusive traffic. | Until browser closes |
_ga, _ga_* | Google Analytics 4 | Analytics | Aggregated traffic statistics: pages per session, traffic sources, average time on page. IP addresses are anonymised before storage. | 14 months |
kwiffcasino_aff | Kwiff | Affiliate tracking | Records that a click on an outbound operator link originated from Kwiff so the partnership is credited. | 30 days |
External policies for reference: Google Analytics is covered by Google Privacy and Terms. Casino partner sites begin issuing their own cookies the moment a visitor clicks through; those are governed exclusively by each operator's privacy policy and fall outside Kwiff's control.
4. Adjusting cookie behaviour from the browser side
Every current browser exposes controls for blocking incoming cookies, purging existing ones, or refusing third-party cookies wholesale. Official documentation links:
An alternative is opening Kwiff in your browser's private or incognito window — that mode prevents cookies from carrying over between sessions.
5. The effect of turning off non-essential cookies
The site keeps functioning without disruption. Every page remains readable, every internal link still works, and click-throughs to operator destinations still complete. Three minor knock-on effects are worth knowing about: your visit will be absent from the traffic statistics; clicking an affiliate link with tracking opted out blocks the partnership credit — the operator still treats you, the user, identically; the only thing missing is the commission record back to Kwiff; and the consent banner resurfaces after a cookie wipe because the choice itself lives inside a cookie. The full set of editorial standards that govern each page (including how affiliate links are flagged) is laid out on the Editorial Policy page, while the player-safety commitments are detailed on the Responsible Gambling page.
6. GPC support and the Do Not Track header
Kwiff respects the Global Privacy Control (GPC) signal: where a browser transmits GPC, every non-essential cookie is suppressed automatically and the consent banner stays hidden. The legacy Do Not Track header lacks a recognised enforcement framework, so the site does not act on it.
7. Revisions to the cookie policy over time
Whenever the cookie inventory on Kwiff shifts, this page is rewritten and the "Last updated" stamp at the top of the document is bumped. Substantive changes — a new category, a fresh third-party integration — trigger a one-off consent banner refresh so returning visitors are re-asked. Routine housekeeping (wording tweaks, link maintenance) does not prompt a re-consent flow.
8. Raising a query or formal complaint
Queries on individual cookies running on Kwiff are most efficiently raised via the Contact page. The Information Commissioner's Office (ICO), reachable at ico.org.uk, is the body that processes complaints against UK sites under the UK GDPR and Data Protection Act 2018.