Cookie Calm privacy policy

Effective September 21, 2026.

Cookie Calm handles cookie consent and supported website interruptions in Chrome. Dave Goldblatt maintains the project. Contact: dave@davegoldblatt.com.

Information processed on your device

The extension examines website addresses, page text, element attributes, and control states to identify banners and promotional prompts and decide whether to act.

This processing can include personal information that appears in page text. Text stays in transient memory and is not retained by the extension.

The extension uses page signals to avoid some suspicious clicks. It inspects field types and names, but does not read password or payment-field values.

It reads button labels and consent switch states. It observes interaction events to preserve forms, chats, and media that you use. No typed characters or field values are recorded.

The extension processes the current tab address to apply site-specific pauses and to coordinate embedded frames. It does not use Chrome's browsing-history API.

For supported Sourcepoint consent flows, it temporarily reads the site's named local consent receipt to check the saved opt-out. The raw value stays in transient memory and expires within eight seconds. The extension does not copy or transmit it.

Information stored on your device

Local Chrome extension storage contains your selected mode, enabled state, and hostnames where you paused automation.

Session storage contains temporary tab status: hostname, rule name, action outcome, promotion category and count, and a generic guard reason.

It also contains up to 12 recent provider results and an opaque action ID. Results contain fixed outcome and reason codes. They exclude page text, full addresses, form values, and consent receipt values.

Tab status clears on navigation, tab closure, settings changes, or browser-session termination. Preferences remain until you change them or remove the extension.

The extension does not store page text, browsing-history records, passwords, or payment-field values. It does not use Chrome storage sync.

Transmission and sharing

The extension has no analytics, telemetry, advertising service, account system, remote AI, or reporting endpoint. Its rules are bundled with the extension.

It does not send page text, addresses, or settings to the maintainer or third-party services.

Automatic clicks use the website's normal consent, close, decline, or minimize controls. Those controls can send requests to the website or its providers.

When a supported optional prompt's decline fails, the extension can apply a reversible local stylesheet to hide it and release its CSS scroll obstruction. This does not record a consent choice or send a request.

The website's own privacy policy governs those requests and any cookies that it sets. Acceptance mode can permit optional cookies and tracking.

If you open a project link, your browser makes a normal request to that external website.

Chrome and the Chrome Web Store perform their own installation, update, and store operations under Google's policies.

Support messages

If you send an email or file a GitHub issue, the maintainer receives the information you choose to provide.

Support information is used to answer your request or investigate the reported problem. GitHub issues are public.

You can request deletion of a support email through the contact address. GitHub controls issue retention and account information on its service.

Your choices

You can pause automation globally or for an exact hostname. Pausing stops new actions and restores elements hidden by Cookie Calm. It does not undo choices saved by website controls.

You can remove Cookie Calm through Chrome's extensions page. Removal deletes its local extension settings and temporary status.

The website retains its own cookies and saved choices. You can manage them through the website or Chrome's site settings.

Limited use

Cookie Calm uses locally processed data only for its disclosed consent and interruption-handling features. It does not sell data or use it for advertising or credit decisions.

Its handling of user data follows the Chrome Web Store User Data Policy, including the Limited Use requirements.

Changes

Policy changes appear in this file with a new effective date. The source code and release history are public in the project repository.