Chrome extension / Cookie Nope / Full release v2.0

No thanks. To all of them.

Cookie Nope looks for recognised cookie-consent controls and attempts to reject optional cookies automatically, while leaving essential cookies available.

Full release — v2.0 See v2.0 in action ↓
Cookie Nope / v2.0 release
CN

Rejection active

Cookie Nope is watching for recognised consent controls on this page.

Full releasev2.0
LocalPage checks happen in the browser
FreeNo features are locked behind payment
FlexibleCustom wording and Allowed websites
QuietNo ads, analytics or affiliate rewriting

Main features

Built for the banner you never asked for.

The full v2.0 release keeps automatic rejection at the centre, but adds clearer control over refusal behaviour, site exceptions, reporting and recovery.

01

Automatic rejection

Watches supported pages and attempts recognised refusal controls automatically, including late-loading consent banners.

02

Rejection preference

Choose whether Cookie Nope should prefer maximum rejection or an “essential cookies only” route where a banner offers more than one safe refusal option.

03

Per-site controls

Decline again manually, allow the current website, or remove it from Allowed websites directly from the popup.

04

Allowed websites

Pause rejection on websites you choose, with subdomain coverage, a common-sites starter pack and clear whitelisted status in the popup.

05

Clear status feedback

Confirmation messages and the optional green toolbar success icon make it obvious when Cookie Nope has successfully acted.

06

Report cookie failures

If a banner beats Cookie Nope, use the dedicated report control to help improve future matching instead of merely swearing at it.

07

Multilingual matching

Recognises consent wording across multiple languages and can inspect eligible embedded consent frames.

08

Backup & restore

Import, export and restore extension settings so your configuration is easier to move or recover.

09

Autosaved settings

Behaviour switches save immediately, with Chrome storage used for settings and Allowed websites so changes do not need a separate Save ritual.

How it works

Three steps. Mostly involving you doing nothing.

Cookie Nope watches for likely consent controls, follows the refusal preference you choose where it recognises a safe route, and leaves sites on your Allowed websites list alone.

Watch

The extension observes page content and embedded frames for recognised consent interfaces.

Match

It compares controls against refusal wording, structure and your custom settings.

Decline

It attempts the safest recognised route to reject optional cookies, without pretending every banner on Earth is identical.

Cookie Nope in action

The real thing. No suspiciously perfect mock-ups.

These current v2.x interface captures show the main popup, the expanded settings page and the distinct state used when a site is on your Allowed websites list.

Full settingsBehaviour, refusal preference, custom phrases and Allowed websites
Rejection activeCurrent-site control, reporting and quick access
Allowed websiteClear whitelist status with one-click removal or one-off decline

Privacy by design

Your browsing is not the product.

During normal automatic operation, Cookie Nope processes page content and domains locally to detect consent controls and apply your site-specific settings. It does not continuously send your browsing history or page content to IF Designs. A failure report or feedback submission is a separate action you choose to initiate.

Read the full privacy policy
Clear permission purpose.
Website access is required because cookie-consent interfaces appear across the web. The extension uses that access to inspect consent controls locally and attempt safe refusal actions.
  • No analytics or advertising profiles.
  • No sale of browsing data.
  • No remotely downloaded executable code.
  • Reports are user-initiated rather than background tracking.
  • Chrome may synchronise settings when Chrome Sync is enabled.

Questions

Useful answers, no interpretive dance.

Does Cookie Nope remove essential cookies?

It is designed to reject optional cookie choices while leaving essential cookies available. Cookie-consent systems vary, so the extension attempts recognised safe refusal actions rather than claiming perfect coverage.

Can I allow cookies on particular websites?

Yes. Add them to Allowed websites or use the per-site quick allow option where available.

Does it send my browsing history to IF Designs?

Not as part of normal automatic operation. Cookie Nope does not run background browsing analytics. If you deliberately use Feedback or Report cookie failure, information associated with that report may be sent so the issue can be investigated.

Are donations required?

No. Cookie Nope is free. Optional cryptocurrency donations support development but unlock nothing and do not change how the extension works.

Free software. Voluntary support.

Cookie Nope has no paid features. Donations simply help fund continued development.

Support IF Designs