Cookieless
Privacy Policy

Cookieless Privacy Policy

Last updated: April 12, 2026

Overview

Cookieless is a Chrome extension that helps users handle cookie banners more quietly. It rejects supported banners, hides other banners visually, and provides a simple per-site pause control in the popup.

What the extension processes locally

On visited pages, Cookieless may inspect page structure, banner text, and page state in order to detect likely cookie or privacy banners. These checks run locally in the browser.

What the extension stores locally

Cookieless stores extension data on the device using chrome.storage.local.

Broken-site reporting

When the user clicks Report broken site, Cookieless can send a support report containing the current page URL and diagnostic information needed to review the issue.

Reports are sent only when the user chooses to report a site. Cookieless does not send general browsing telemetry off-device by default.

Where support reports are processed

Broken-site reports are stored in a Supabase-hosted support inbox used by the developer to review, triage, and fix site issues. Public GitHub Issues are used later for curated engineering follow-up, not as the first landing place for every customer report.

When a report is submitted, the receiving server may log standard HTTP request data, including the submitting IP address, as part of normal server-side infrastructure logging. Server-side logs are retained according to the default Supabase log retention policy. Cookieless does not store IP addresses in the bug reports table directly.

What Cookieless does not do

Support

Public support for Cookieless is handled through GitHub Issues: https://github.com/stiliyan-dev/cookieless/issues

Changes to this policy

This policy may be updated if Cookieless changes how it handles storage, reporting, optional power tools, or website interaction. Material changes should be reflected in the Chrome Web Store disclosures and on this page.