claudphic.com sets no tracking cookies. No advertising, no retargeting, no analytics, no session recording, no fingerprinting. There is no consent banner because there is nothing to consent to — and adding a banner that asks permission for nothing would be theatre.
Why most sites need a banner and this one does not
The consent banner exists because most websites load a stack of third-party scripts — analytics, advertising pixels, retargeting tags, heatmaps, chat widgets, A/B testing tools — each dropping identifiers that follow you elsewhere. Law in several jurisdictions requires permission before that happens. Hence the banner.
This site loads none of that. Not out of unusual virtue, but because a company whose whole argument is that the signals people rely on have been quietly corrupted should not be quietly building a profile of the people reading about it. The consistency is the point.
What is actually stored in your browser
| What | Purpose | Duration | Type |
|---|---|---|---|
| Session cookie (only if a form is used) | Security token preventing cross-site request forgery | Until you close the browser | Strictly necessary |
| Browser cache | Stores stylesheets, scripts and images so pages load faster on return | Set by your browser | Technical, not a cookie |
That is the complete list. The session cookie carries no identifier that means anything outside a single visit, is not linked to any profile, and is not shared with anyone. Under the ePrivacy rules and comparable frameworks, strictly necessary cookies of this kind do not require consent — but you should be told they exist, which is what this page is for.
What we do not use
- No Google Analytics, or any other individual-level analytics platform.
- No advertising or retargeting pixels — no Meta Pixel, no Google Ads remarketing tag, no LinkedIn Insight tag.
- No session recording or heatmaps. Nobody replays your mouse movements.
- No chat widgets. These are among the heaviest third-party trackers on the modern web.
- No A/B testing or personalisation tools. Everyone sees the same site.
- No social media embeds. Embedded posts and share widgets track you whether or not you interact with them; our share links are plain hyperlinks that do nothing until clicked.
- No fingerprinting or cross-device linking.
- No consent-management platform, since there is no consent to manage — and these are themselves frequently trackers.
The one third-party request, disclosed
This site loads its typefaces from Google Fonts. That means your browser makes a request to fonts.googleapis.com and fonts.gstatic.com, and Google receives your IP address and user-agent as part of that ordinary HTTP request. Google states that it does not set cookies for font requests and does not use the data for ad profiling.
We disclose it because it is the only external request the site makes, and a page claiming "no third parties" while quietly making one would be exactly the kind of half-truth this company exists to argue against. We do not receive or store anything from that exchange.
If you prefer to avoid it, a content blocker that blocks third-party font loading will do so; the site will fall back to your system typefaces and remain fully readable.
What a tracking cookie would actually let us do
It is worth being concrete about what is being declined here, because "we don't use tracking cookies" is a sentence most readers skim past without picturing the alternative.
With a standard analytics cookie, we would know that a specific browser visited this page, then the independence policy, then the careers page, then returned eleven days later from a LinkedIn link and read two blog posts. With an advertising pixel, that same visitor could then be shown Claudphic advertising across unrelated websites for the following month. With a session-recording tool, we could watch a replay of the cursor moving down this page, including anything typed into a form and then deleted.
All three are ordinary, widely deployed, and entirely legal with consent. None of them are used here. What we know instead is the aggregate shape of traffic from server logs — that a page was requested a certain number of times — with no ability to connect one request to another or to any person.
The practical cost of that choice is real. We cannot tell which page persuaded someone to write to us, cannot run funnel analysis, and cannot measure whether a change to a page improved anything. Those are genuine losses, and we accept them because the alternative sits badly beside everything else this company publishes.
The consent banner problem, briefly
Consent banners were introduced to give people a choice. In practice most of them are designed to make one option effortless and the other tedious — a large "Accept all" button next to a small "Manage preferences" link leading to a screen with several hundred toggles. Studies of banner design consistently find that the friction is deliberate, and regulators in several jurisdictions have said so directly.
The version of consent that actually respects a reader is the one where the site does not do the thing in the first place. That is cheaper to build, impossible to get wrong, and requires no button at all. It is also, admittedly, easier for a company whose business model does not depend on behavioural advertising — but that is precisely the point being made rather than an excuse.
Server logs are not cookies
Our web server keeps standard request logs — IP address, timestamp, URL requested, status code, referrer and user-agent. This is how a web server works, not a tracking decision, and it is used for security, abuse prevention and diagnosing faults.
These logs are not cookies, are not used to build a profile, are not linked to any identity, and are rotated on a short cycle. Full detail is in the privacy policy.
Controlling cookies yourself
You do not need to do anything for this site, but for the rest of the web, every major browser lets you view, block and delete cookies from its privacy settings — Chrome, Firefox, Safari and Edge all provide per-site controls and a "block third-party cookies" toggle.
Blocking all cookies for claudphic.com will not break anything, because nothing here depends on them.
Our products handle this separately
This policy covers claudphic.com only.
Unfiltered Choice is a comparison publication with affiliate relationships, and affiliate links necessarily involve tracking parameters so that a referral can be attributed. That is disclosed in that site's own policies and in our revenue disclosure.
Claudphic Ads is an advertising-attribution product, and tracking is literally what it does — on behalf of its customers, for their own leads, under its own terms and data processing agreement. Neither product's behaviour is governed by this page.
If this changes
If we ever add anything that stores data in your browser beyond what is listed above, this page is updated first, the effective date changes, and — where consent is legally required — consent is requested properly rather than assumed through a pre-ticked box or an implied-by-scrolling notice.
This version is effective from 8 August 2026. Questions go through the contact page.