Pay Guard - Options in Privacy grayed out

Hi @billbateyiii​, 

At the moment, Trend Micro Security Apps work well with Google Chrome, Mozilla Firefox, Edge, and Safari.

However, Brave, despite being a Chromium browser, isn't supported right now. That's why the Trend Micro toolbar might not be working properly for you on Brave.

@tm_carlo​ The option I'm showing in the picture is NOT from the browser.  It's literally in the Windows app.  Why are you so fixated on the extension?  Did your developers weirdly tie those together instead of just having the Windows app set that somewhere the extension can read? If I could set that option and still got the Pay Guard modal, then it would make sense you're referencing it.  I've never developed an extension, so there could be things I don't understand, but the extension must get settings from somewhere, which I assume is a config file since I don't see a database running (but I haven't actually looked).  Is your Windows app looking for the browser extension, not supporting Brave, and therefore doesn't give me the option because it thinks it's not fully installed (please tell me you didn't do that, as that would be silly)?

Again, why is the option in the WINDOWS APP (not the browser) greyed out!?  Can I manually modify a user setting file, Windows registry, or wherever!?

Hi @billbateyiii,

This might be happening because it doesn't detect the Trend Micro Toolbar on a supported browser. To troubleshoot, could you try changing your default browser to one of the supported ones and see if the issue still persists?

Thank you in advance!

@tm_carlo​ I had to install the extension in Microsoft Edge and could then change the setting.  I returned to the Brave browser and verified it no longer pops up on various websites where it popped up every time.  Given that each browser installs extensions in different directories, this means that this is a universal setting outside of the extension that the extension reads/loads.

This is an odd choice by DEVs/Product Owner/UX.  This option should always be available to be set.  It's fine to default to "on" but needs to be always be changeable; there's no need to try and determine if the extension is installed if it's universal.  It doesn't really get you much and is going to cause more headaches like this, especially as Chromium browsers become more common.  For instance, I only use TM's extension to see link ratings and block bad sites (which it does quite well in Brave).  I mean, I could be wrong in that but then I don't see how Brave would have been affected.

I have no idea if this can be passed onto development, but it really should be considered.

Hi @billbateyiii​, 

Thank you for sharing your thoughts. We have investigated this matter with the product team and will keep you informed about any updates related to this issue.

We value your ongoing support.