Cookie Policy
Last updated: July 26, 2026
This page explains the cookies wrdlcheat uses, why they exist, and how to control them. Short version: right now there are none. The longer version explains what changes when Google AdSense activates.
What a cookie is
A cookie is a small text file a website asks your browser to store. The next time you visit, the browser sends the file back to the site, which lets the site remember things about you between visits — preferences, login state, advertising context, that sort of thing.
Cookies fall into a few categories, and EU law (and a growing set of US state laws) requires sites to disclose which ones they use and to ask permission before setting non-essential ones.
What wrdlcheat sets today
wrdlcheat’s own code sets no cookies at all — no session cookies, no preference cookies, nothing in localStorage or sessionStorage. Every visitor gets the same server-rendered HTML; the site has nothing to remember about you between visits. But two third parties do set cookies on a page load, and pretending otherwise would make this page useless:
- Google. The AdSense loader script runs on every page even though no ads are being served yet, and it lets Google set a probe cookie named
test_cookieondoubleclick.net, which checks whether your browser accepts cookies. The fuller advertising cookie set described below applies only once ads are actually approved and running. - Cloudflare. Sets a security cookie (typically
cf_clearance) for bot mitigation. Cloudflare Web Analytics also runs on the site, but it is cookieless — it counts page views without storing anything on your device.
Cloudflare’s cookies are governed by Cloudflare’s privacy policy, not by wrdlcheat.
What changes when AdSense activates
wrdlcheat is intended to be supported by Google AdSense. The loader is installed but the site is not an approved publisher, so no ads are served today. If approval comes through, the cookie picture looks like this:
| Category | Purpose | Who sets it |
|---|---|---|
| Essential | Site delivery and security — bot detection, rate limiting, request routing. | Cloudflare |
| Analytics | Cloudflare Web Analytics runs on the site and is cookieless — it counts aggregate page views without storing anything on your device or identifying you. No Google Analytics, and if that ever changes this row will say so. | Cloudflare |
| Advertising | Ad serving, frequency capping (so you don’t see the same ad twenty times), and personalization where permitted. Cookies named __gads, __gpi, and others may appear once AdSense activates. |
The consent banner
When AdSense activates, visitors in regions that require it (the EU, the UK, certain US states, and others) will see Google’s Funding Choices consent banner on first visit. The banner lets you accept or reject personalized advertising, and your choice is remembered via a cookie set by Google. Visitors outside those regions will not see the banner; ad serving falls back to non-personalized mode for anyone who opts out.
How to control cookies
Every modern browser lets you view, block, or delete cookies per-site through its settings. The exact path varies — search “cookie settings” in your browser’s help docs for the right page. You can also use browser-level tracking protection (built into Safari, Firefox, and several Chromium-based browsers) to block third-party cookies across the whole web.
For Google ad cookies specifically, the Google Ads Settings page lets you opt out of personalized advertising across all sites using Google ad services, not just this one.
Related policies
Cookies are one slice of the broader data picture — the privacy policy covers what data the site handles end-to-end, and the terms of service cover the rules of using the site itself. For questions about any of this, the contact page has the address.