Cookie Policy

This page lists every cookie this site can set, who sets it, what it does and how long it stays on your device. It exists because a generic sentence about "using cookies to improve your experience" tells you nothing you could act on. We publish the actual names, including our own Google Analytics property identifier, so you can open your browser's storage inspector and verify that what you receive matches what we describe.

This site is an editorial resource covering Popunder Ads, not an advertising network. We do not operate an ad server, we do not build advertising profiles from your visit, and we do not sell audience data. What follows applies to visits to this website only, and stops the moment you click through to a third-party platform, where that platform's own policies take over.

What Cookies Are and Why a Site Sets Them

A cookie is a small text file that a website asks your browser to store on your device. On your next request, the browser sends it back, which is how a stateless protocol like HTTP manages to remember anything at all. The file itself is inert text: it cannot execute, cannot carry a virus, and cannot read other files on your machine.

Cookies split two ways. By origin, they are first-party (set by the domain in your address bar) or third-party (set by another domain whose code runs on the page, such as an analytics provider). By lifetime, they are session cookies, deleted when you close the browser, or persistent cookies, which carry an explicit expiry date and survive restarts until that date passes or you clear them.

Similar technologies do the same job by other means. Local storage and session storage hold key-value data in the browser without being sent on every request. Pixels, sometimes called web beacons, are one-pixel images or script calls whose only purpose is to signal that a page loaded. Where we use those, we list them alongside cookies below, because the practical effect on your privacy is the same and separating them would be a technicality that serves us rather than you.

Cookie Categories on This Site

Strictly necessary

This site sets none. It is served as static files with no login, no shopping basket, no contact form and no server-side session, so there is no state for a first-party cookie to carry. If your hosting provider or a content delivery network in front of the site adds its own security cookie, that cookie belongs to the provider and is listed on their documentation rather than here.

Analytics

These count visits and measure which pages are read to the end. We use them to decide what to write next and to find pages that load slowly on real devices rather than on our own machines. The reporting we see is aggregated: page paths, referrers, device categories, country. Google Analytics 4 does not record raw IP addresses at rest; addresses are used in transit for coarse location and then discarded. These cookies are written when the page loads, and the section below explains how to stop that from your browser.

Affiliate attribution

When you click a commercial link on this site, the destination platform may set a cookie on its own domain recording that the visit came from us. That is how the commercial arrangement described in our terms is measured. We do not read that cookie, cannot read it, and receive only aggregate counts from the partner. It contains a partner identifier and a timestamp, not your name or email.

What Is Not Used Here

No retargeting pixels, no social media tracking widgets, no cross-site advertising identifiers, no fingerprinting scripts that combine screen resolution, fonts and canvas rendering into a device hash. Google Analytics is the only third-party script on the site; there is no tag manager container, no A/B testing tool and no session recorder. If you audit this site and find something in those categories, it is a mistake on our side and we want to hear about it through the contact page.

Our GA4 property is G-VV5DF4J2V4, so the second cookie carries that identifier in its name and both are straightforward to confirm in your browser inspector. Lifetimes on third-party cookies are set by the third party rather than by us and can change without notice on their side. The affiliate window depends on the partner programme and is the figure that determines how long a click stays attributable.

How to Control Cookies Yourself

There is no cookie banner on this site, so control sits with your browser rather than with a dialogue we put in front of you. That is a deliberate choice about clutter, and it means the instructions below are the real mechanism rather than a fallback.

Browser settings give you a blunter but more reliable instrument. In Chrome, open Settings, then Privacy and security, then Third-party cookies, where you can block third-party cookies entirely or add a per-site exception. Firefox groups the same controls under Settings, Privacy and Security, Cookies and Site Data, and its Enhanced Tracking Protection blocks known trackers by default on the Strict setting. Safari blocks cross-site tracking by default on both macOS and iOS; the toggle sits under Settings, Safari, Prevent Cross-Site Tracking. Edge places the same options under Settings, Cookies and site permissions.

Blocking cookies costs you nothing here. Every page is static HTML and renders identically whether cookies are allowed, blocked or cleared mid-visit; nothing on the site depends on them to display, navigate or read. The only thing that changes is whether our visit count includes you.

Google publishes a browser add-on that opts your device out of Google Analytics measurement across every site that uses it, which is a more durable choice than a per-site refusal. It installs as a browser extension and needs no account.

Legal Basis and Retention Periods

Analytics measurement runs on legitimate interest under Article 6(1)(f) of the UK General Data Protection Regulation: the interest is understanding which pages are read so we know what to write next, weighed against a low privacy impact, since the data we see is aggregated and we never combine it with anything that identifies you. Affiliate attribution cookies are set by the destination platform under its own lawful basis once you choose to click through, not by us.

Server access logs, which record IP address, request path, user agent and timestamp, are retained by our host for 90 days and then deleted. Aggregated analytics reporting is retained for 14 months, the interval that lets us compare a month against the same month a year earlier. Email sent to any of our published addresses is kept for 12 months from the last reply and then deleted, unless the exchange concerns a factual correction, in which case we keep it for as long as the corrected page is published so the record of why a change was made survives with it.

You can ask what we hold about you, ask for it to be corrected or deleted, or object to processing based on legitimate interest, which for analytics you can also exercise unilaterally with the browser controls above. Those rights come from Articles 15 to 21. Write to us through the contact page; we acknowledge within 72 hours and answer within 30 days. If our answer does not satisfy you, you can complain to the data protection authority where you live, which in the United Kingdom is the Information Commissioner's Office.

Changes to This Page

We revise this page whenever a cookie is added, removed or changes lifetime, and whenever a provider changes what its cookie does. The date at the top is the date of the last substantive edit rather than an automatic timestamp: if nothing changed, the date does not move. This page is the record, so the table above is meant to be checked against your own browser rather than taken on trust.

Questions about anything on this page, including a request for the raw list of cookies set on your specific visit, go to the contact page. Our approach to what we publish and why is set out in the editorial policy.