StopTheMadness for Chrome SupportMac App Icon

Home: StopTheMadness

Safari: StopTheMadness for Safari Support

Email: stopthemadness@underpassapp.com

Help Topics:

Privacy:
According to Google Chrome, StopTheMadness has permissions to "Read and change all your data on the websites you visit". However, this is just boilerplate text from Google shown for every Chrome extension that can modify webpages. StopTheMadness does not read, change, or share your personal data. The privacy policy has more details about StopTheMadness privacy.

If you've already set up Chrome to sync with your Google account, then your StopTheMadness Website Protections will also be synced. This sync process is controlled by Google Chrome. The only data from StopTheMadness that would be synced is what you see in the StopTheMadness Options.

Contextual Menus:
By default, StopTheMadness stops web sites from disabling Chrome's contextual menu. This is useful for example on YouTube, where Chrome's contextual menu allows you to easily Enter Picture in Picture. If you still need to open a web site's custom contextual menu instead of Chrome's contextual menu, just press the option key (Mac) or alt key (Windows) while you open the menu.

Website Protections:
You can selectively enable and disable StopTheMadness protection features. Your custom protections can be configured to apply to every web page or just to web sites that you specify. To change your protections, open the Extensions window in Google Chrome, click the Details button under StopTheMadness, and then click "Extension options" on the Details page.

StopTheMadness Options

There are a number of protection features that you can enable and disable. By default, most of these protections are enabled. (See the Contextual Menus section above to temporarily override contextual menus protection.) When a protection is enabled, it prevents websites from overriding Chrome's standard behavior. In most cases, you'll want the StopTheMadness protections to be enabled. However, sometimes disabling a StopTheMadness protection is necessary for website compatibility. If you uncheck "Cut, Copy, and Paste", for example, then websites are allowed to override Chrome's standard behavior for cut, copy, and paste.

When you change the protections in StopTheMadness, those changes will apply the next time you load a web site in Chrome. If you already have a web site open in Chrome, and you want the changes to apply immediately to the web site, you need to reload the page in Chrome.

How to Add Website Protections:
The Default Website Protections apply to every web page in Chrome, unless you have custom protections for a particular site. To create custom protections for a website, press the New Protections button. There are two ways to specify websites: domain or URL. Examples of domains are "apple.com" and "google.com". If you specify a domain, then subdomains of that domain are automatically covered too. For example, "google.com" also covers "www.google.com", "mail.google.com", etc. If you want a subdomain to have different protections than its domain, create a separate item for the subdomain. The longest match always wins, so if you have items for both "google.com" and "mail.google.com", then your "mail.google.com" protections will apply when you load the page "https://mail.google.com/". If you want protections to apply only to subdomains but not to the domain, put a dot at the beginning: ".google.com" applies to "https://www.google.com/", etc., but not to "https://google.com/".

You may want to apply custom protections only to certain paths of a website, in which case you need to specify the website as a full URL. For example, if you enter "https://www.google.com/maps", then the custom protections will only apply to Google Maps and not to Google Search at "https://www.google.com/". Subpaths are automatically covered too: "https://www.google.com/maps" would also cover "https://www.google.com/maps/search/apple+park". You can customize subpath protections by creating a separate item for the subpath. As with domains, the longest match among URLs always wins. And a URL setting that includes a domain will override a domain setting for the same domain, since the URL is longer. So "https://www.google.com/maps" takes precedence over "www.google.com".

Known Website Compatibility Issues:
In these cases you may want to create custom website protections and disable the specific protection.