There are a few things you can do if you need to keep PolicyPak running on the machine (in general) but disable Browser Router's interaction with the machine.
That being said, here's the order we recommend in getting to the bottom of the issue.

1. What happens if you 100% uninstall the PolicyPak CSE…. Does the problem go away? If NO, then this is unlikely to be a PolicyPak problem.
2. Can you reproduce using the LATEST CSE available in the Portal. Does the problem go away?

3. Check to see if this flag is set in ANY routes. A check here could “bleed” from one route into another website. This setting is not supported, and as such you might have to remove it from all routes.

   

4. After steps 1, 2 and 3… if you can REPRODUCE using latest CSE... then and only then.. send us log files (user and computer) via Sharefile (do not attach.) https://kb.policypak.com/kb/article/261-what-must-i-send-to-policypak-support-in-order-to-get-the-fastest-support/

5. AFTER you install the latest CSE, you might want to attempt to disable the in-Browser Extensions for the affected browser, but keep Browser Router operating. Here's how to do that (see screenshot below.)

   

6. AFTER you install the latest CSE and the in-browser Extension, and are STILL able to reproduce the issue, you could kill JUST the affected component like Browser Router. Use these instructions: https://kb.policypak.com/kb/article/240-what-if-i-want-to-unlicense-one-component-like-pppreferences/ (KB shows killing PPPreferences, but in this case you would kill PolicyPak Browser Router.)
7. Is the web app something we could have access to, and reproduce the experience on our end? If yes, that would get you a test / repro / fix about 100x faster.