Cookie Policy
This site runs one measurement tool and nothing else. Google Analytics 4 is installed, it sets two cookies, and this page names both of them with their provider, purpose and lifetime. Everything else a content site normally loads — advertising pixels, retargeting tags, heatmaps, session recorders, social embeds, external fonts — is absent. Below you will find the cookie table, the legal position on consent, what changes when you follow an outbound link, and how to check the whole thing in your own browser in about thirty seconds. Effective from 5 August 2026.
The cookies this site sets
Two cookies are written, both by Google Analytics 4 through the gtag.js library loaded from googletagmanager.com. Neither carries your name, your email or anything you have typed, because there is nowhere on this site to type anything.
| Cookie | Provider | Purpose | Lifetime |
|---|---|---|---|
| _ga | Google LLC | Assigns a random identifier so repeat visits from one browser count as a single visitor and not several | 2 years |
| _ga_MHSPZL4755 | Google LLC | Holds session state for this property: when a session began, how many pages it covered, whether it is still running | 2 years |
What those two produce is aggregate reporting: how many people reach the comparison table, which sections hold attention, whether a page renders badly on a particular device. They do not tell us who you are, and they are not used to build an advertising profile.
What is not running on this site
Beyond the two cookies above, nothing else stores anything. There is no Tag Manager container, no Meta pixel, no heatmap tool, no session recorder and no A/B testing script. Advertising and retargeting pixels are absent, so nothing served from this domain follows you around the web.
Local storage and session storage go unused. Fonts come from the operating system, which means no request reaches Google Fonts or any comparable host and no IP address of yours arrives at a third party through font delivery. Social embeds, comment widgets, chat bubbles and video players are all absent, and those are the usual sources of silent third-party cookies on a content site.
Consent, and how to refuse
Under the Privacy and Electronic Communications Regulations, consent is required before storing information on a device unless the storage is strictly necessary to deliver the service the user asked for. Analytics cookies are not strictly necessary, so the two above sit inside that requirement, and the corresponding lawful basis under UK GDPR is consent under Article 6(1)(a).
Refusing them costs you nothing here. Blocking analytics and third-party cookies in your browser, using a private window, or installing Google's own opt-out add-on each prevent the measurement from running, and no page, table or control on this site depends on either cookie. Consent can be withdrawn at any point by clearing the two cookies from your browser; the processing that follows from them is described in the privacy policy.
What happens when you follow a sign-up link
Buttons on this site pointing to an advertising platform carry tracking parameters inside the address itself — a source, a medium, a campaign and a position identifier. Those live in the URL you can read in the address bar. They are not a cookie, this site does not write them to your device, and they contain no identifier for you: they describe where the referral came from, not who followed it.
Once you arrive on the destination platform you are on their infrastructure under their policies, and that platform will set its own cookies, including cookies used to attribute a registration to a referring source. Those are theirs, governed by their cookie policy, and this site has no control over them and receives no data about your session there. The commercial arrangement behind those buttons is disclosed in full in the editorial policy.
Hosting-level technology
Serving a page requires a web server, and a web server writes a log line for each request containing the fields listed in the privacy policy. That is server-side record-keeping rather than device storage, and no cookie is involved in it. A hosting provider may additionally apply strictly technical measures for security and delivery; where such a measure involves any device storage it would be strictly necessary within the meaning of the regulations, and it does not identify individual readers or build profiles.
How to verify this yourself
Open your browser's developer tools before loading a page here and look at the Application or Storage panel. The cookie list for this domain will hold exactly two entries, _ga and _ga_MHSPZL4755, and nothing else. Then open the Network panel and reload: you will see requests to this domain for the page, the stylesheet and the images, one request to googletagmanager.com for the analytics library, and no calls to a tag manager container, a font host or an ad server. Any privacy extension you run will report the same two cookies and the same single third-party host.
Verifying a claim instead of trusting it is the same principle the rest of this site is built on, and it is set out for editorial figures in how we check figures. A cookie policy is simply the one page where the reader can run the check in their own browser instead of opening someone else's documentation.
Do Not Track and Global Privacy Control
Some browsers send a Do Not Track header or a Global Privacy Control signal with each request. Neither is acted on at the server here, and no configuration on this site reads them. What does honour them is the browser itself and any privacy extension you have installed, both of which commonly block the analytics library outright, in which case no cookie is written and no measurement reaches Google.
Nothing is sold or shared with data brokers in either case, and no advertising profile is built from the two cookies above. The signals appear in server logs because they travel as HTTP headers, and no record is kept of which visitors send them.
Controlling cookies in general
Every major browser lets you block cookies, delete them, restrict third-party cookies specifically, or browse in a private window that discards them at the end of the session. Because no feature here depends on either cookie, blocking them entirely will not break a page, a table, the table of contents or any other element. That is worth testing on any site handling sensitive subject matter, since a site that stops working when storage is blocked is telling you something about what it was storing.
Changes
Everything described here applies across Adult Ad Networks and every supporting page, since all of them are served from the same static build carrying the same single script. Who runs the site is on the about page, who writes it is on the author page, and the conditions of use are in the terms and conditions.
If a further cookie or any comparable storage mechanism is introduced, this page will be updated before it goes live, and the table above will name the cookie, its provider, its purpose, its lifetime and whether it is strictly necessary. The effective date will change with it. No advertising or retargeting cookie will be added to this site. Questions go to [email protected] or through the contact page.