Cookies

Last updated 6 September 2026.

1. No tracking cookies by default

Allfound sets no tracking cookie and no advertising cookie of its own, on any page, ever. A page you open here is plain HTML built ahead of time; it does not phone home to render. The one cookie we set ourselves is described in section 2, and it identifies nothing and nobody.

2. Local storage and IndexedDB: functional, no consent required

The checklist keeps your progress in your browser's IndexedDB, under an anonymous account id the device made up. That is what makes ticking work without a connection and without a login. It is strictly functional storage — the site cannot work without it — so it needs no consent under the ePrivacy rules, and nothing in it is sent to anyone unless you turn on sync, which sends your progress to our own Worker and nowhere else.

One first-party cookie, af_pro, is set by the checklist when your account is Pro and removed the moment it is not. It holds the value 1 and nothing else: no id, no name, no history. Its only job is to tell our other pages not to load the advertising and consent scripts described below, because a Pro account never sees an ad. It lasts a year, is sent only to this site (SameSite=Lax), and is functional in the same sense: it exists to keep something from running, not to track you.

3. Consent for ads on the free tier

Free-tier pages — an item, a category, a launch page, the tracker's list screen — may carry one advertisement, below the content, served by Google AdSense. Before any advertising script is requested, Google's consent manager ("Privacy & messaging", the CMP) is loaded and asks for your decision under the IAB Transparency & Consent Framework. Only after it reports a decision — whatever the decision — is the AdSense script requested. If you decline, the unit shows a non-personalised ad or nothing; the page never asks again on its own. The consent manager stores your choice in its own cookies and local storage on this site, as its documentation describes; we do not read them. With no advertising client configured — the state at launch — none of this loads at all.

Google, as the provider of the consent manager and the ads, receives the requests your browser makes for its scripts and, after consent, for the ads. What Google does with them is covered by Google's privacy policy and by your decision in the consent manager. Allfound sends Google no account id, no progress and no email address.

4. Analytics without cookies, and error reports without you

Every page loads Cloudflare Web Analytics, a small script from Cloudflare that counts page views and page timings. It sets no cookie, stores nothing in your browser, and does not fingerprint the device; Cloudflare aggregates the counts and we see totals, top pages and referrers. This is why it needs no consent banner.

If the checklist itself hits an error, it sends a short report to our own Worker: the error message, a trimmed stack trace, the page's path, the build's version and your browser's user-agent string. Our Worker forwards that to Sentry, our error-monitoring processor, without your IP address; the report never contains an account id, a progress item, an email address or anything you typed. At most three reports leave a page, and a repeated error is sent once.

5. How to change or withdraw consent

Open the consent manager's own controls on any page that carries an ad — the "Privacy" link Google places in the ad unit, or the choice dialog when it appears again — and change or withdraw your decision there; the choice applies at once. Clearing this site's data in your browser removes the consent manager's storage too. Turning Pro removes ads and the consent manager from every page for that account. Your progress is never affected by any of this.

6. Changes to this notice

When something on this list changes — a new script, a different provider, a cookie we did not have — this page changes with it and the date at the top moves. Questions go to .