Let 'Em Cookie privacy

Let 'Em Cookie reads page elements locally to accept cookie banners and stores counts, preferences, first-share state and pending counter events in your browser; uninstalling removes them.

The homepage's "cookies eaten" means observed banner dismissals, not actual cookies: from version 0.3.0, counting is on for new installs, while existing installs get one choice tab and stay off unless they agree; extension Settings turns counting off and deletes unsent events, earlier versions send no automatic analytics, and no historical counts are uploaded.

Counting sends only a random retry ID per dismissal, retrying for up to 24 hours, with no visited address, hostname, cookie contents, page text, screenshot or persistent install ID; Cloudflare receives normal network data including your IP, but our code stores only daily secret-keyed IP hashes to estimate participating connections and limit spam, deletes hashes and event IDs on hourly cleanup within two days, keeps identifier-free daily aggregates and totals, disables Worker request logs, and makes only the total public.

Optional missed-banner reporting opens a GitHub draft whose URL sends GitHub the hostname, clicked selector and extension version for you to review and submit publicly; X and Substack open only when you choose to share, the homepage loads Google Fonts and the public counter without sending cookie events, and those services apply their own privacy policies.

The optional homepage demo stores a temporary choice in this site's localStorage. It uses the real library without optional trackers. Embedded sites using the library store their own choice locally and must explain their own tracking and withdrawal behavior.

We do not sell data or use it for advertising or credit decisions, we follow the Chrome Web Store User Data Policy including Limited Use, and questions can go to chrisbest@mail.instinct.com.