"This extension is not trusted by Enhanced Safe Browsing" – How to build user trust?

[Sneh Agrawal]

Hi devs,

I recently published a Chrome extension using a new developer account, but users see a warning:

"This extension is not trusted by Enhanced Safe Browsing."

This is hurting installs and makes social promotion almost useless — users drop off instantly.

How long does it take for a new extension/account to gain trust?

Is there any way to speed it up or improve credibility faster?

Facing this early-stage trust issue is really frustrating. Any tips or experience would be appreciated!

[Oliver Dunk]

Hi Sneh,

This is based on both your extension's age as well as other factors. We don't share the specific criteria which unfortunately means I can't say for sure when this will go away.

It does usually go away relatively quickly for new items, and so if you are patient this should resolve itself. There isn't a way to speed up the process I'm afraid.

For clarity, this doesn't show for all Chrome users. It only shows for users with enhanced safe browsing enabled which is more typical in large enterprises.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/67a30e3b-628c-4e1d-8d11-ad773762c535n%40chromium.org.

[Sneh Agrawal]

Hello, I'm building a Chrome extension where the core logic is critical and proprietary. I understand that Chrome Web Store doesn't allow heavy obfuscation or encrypted code for safety reasons. But is there any recommended or allowed method to protect the core logic from being easily copied, while still following all extension guidelines?

[Oliver Dunk]

Hi Sneh,

We support minification as it would be implemented by most bundlers. That makes your code harder to understand and therefore copy.

Unfortunately, we don't have anything beyond that.

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

[Alesandro Ortiz]

Hi Sneh,

If possible, you can implement most of the proprietary logic server-side and implement only what is minimally required on the client-side.

This is the approach used by many websites and extensions if they don't want to expose proprietary logic that would otherwise be possible to run client-side.

Regards,

Alesandro