Skip to content
InPolicy InPolicy Docs

Turn it off for a site

Some sites don’t play nicely with the extension. Others — internal tools, SaaS you don’t want the extension to touch — you’d rather just exclude. You can disable the extension per-site from the popup.

Why you might want to

Section titled “Why you might want to”
  • Custom editors that break under observation. Some rich-text editors (older CMSes, certain in-house tools) re-render aggressively enough that the extension’s underlines flicker or the editor slows down noticeably.
  • Sites that are irrelevant to policy checking. If your team has no policies that would ever apply to what you’re doing on a given site, there’s no reason to scan there.
  • Sites with strict content security policies. Most CSP-protected sites work fine because the extension bypasses page CSP, but a handful have extra defenses that cause rendering issues.

How to disable for the current site

Section titled “How to disable for the current site”
  1. Navigate to the site you want to exclude.
  2. Click the InPolicy icon in your Chrome toolbar.
  3. In the popup, toggle Disable on this site (or similar, depending on the extension version).
  4. The popup confirms the change. Reload the page — underlines and cards will not appear.

The exclusion is stored against your account, not just your browser. If you sign in from a different Chrome profile or computer, the exclusion still applies.

How to re-enable

Section titled “How to re-enable”

Same path: navigate back to the site, open the popup, toggle Disable on this site off.

How admins can exclude sites fleet-wide

Section titled “How admins can exclude sites fleet-wide”

Admins can maintain a tenant-wide exclusion list. This is useful for:

  • Internal apps where detection is unnecessary.
  • Payment processors or other sensitive sites where an extension observing the DOM is a compliance concern.
  • Legacy systems that break under the observer.

The exclusion list is managed via the admin API; a dedicated UI is planned. For now, contact your admin if you need a tenant-wide exclusion added.

What “disabled” means

Section titled “What “disabled” means”

When disabled for a site:

  • The extension’s content script still loads, but it does not scan text or draw underlines.
  • Sign-in state is unaffected.
  • Other sites continue to work normally.

The exclusion is lightweight — toggling takes effect on the next page load with no reinstall.

What disabling does not do

Section titled “What disabling does not do”
  • It does not uninstall the extension. To uninstall, see Install the extension.
  • It does not sign you out.
  • It does not affect the Mac app, which runs independently of the browser.
Section titled “Related”