Skip to main content

If you’ve recently tried to install or update the Fluencer Fruit extension and encountered a yellow warning saying “This extension is not trusted by Enhanced Safe Browsing,” you’re not alone—and your extension is perfectly safe.

What’s Happening?

Starting in June 2025, Google Chrome introduced a new feature where your Enhanced Safe Browsing settings automatically sync across all your devices. This means if you enabled Enhanced Safe Browsing on your phone or any other device where you’re signed into Chrome, it now applies everywhere—including on computers where you might not have consciously chosen that setting.

This change has dramatically increased the number of people seeing extension trust warnings. Many users who never enabled Enhanced Safe Browsing on their work computer suddenly have it turned on because they enabled it once on another device.

Is Fluencer Fruit Safe?

Yes, absolutely. The Fluencer Fruit extension:

  • Follows all Chrome Web Store Developer Program Policies
  • Has proper privacy disclosures stating we don’t sell your data to third parties
  • Uses your data only for the core purpose of organizing your school emails
  • Has been reviewed and approved by Google for the Chrome Web Store

The warning doesn’t mean the extension is compromised, malicious, or dangerous in any way.

What Does “Not Trusted” Actually Mean?

Google’s “trust” designation is based on an opaque algorithm that evaluates developer reputation over time. It’s not about whether an extension is safe or follows the rules—even extensions with perfect compliance records, years of operation, and thousands of happy users can show this warning.

According to Google’s own documentation, approximately 25% of all Chrome Web Store extensions are flagged as “not trusted” by Enhanced Safe Browsing. This includes extensions from established developers who have been building Chrome extensions for years.

The warning system looks at factors like:

  • How long the developer account has existed
  • Developer compliance history
  • Time-based reputation signals
  • Other undisclosed criteria

Google explicitly states that new developers require “at least a few months” to build trusted status, but there’s no guaranteed timeline or clear path to achieving it.

Why Can’t Fluencer Fruit Just Fix This?

Unfortunately, there’s nothing we can do directly. According to Chrome’s Developer Relations team, the official response is: “This isn’t something that can be directly fixed by you as a developer, but should resolve itself in time for developers that follow our policies.”

We’ve maintained perfect policy compliance since day one. We can’t make technical changes or documentation updates that will remove this warning—it’s entirely controlled by Google’s automated systems based on developer reputation that builds over time.

What Should You Do?

You can safely click “Continue to install” when you see this warning. The warning is informational, not a block. Chrome is letting you know that the extension hasn’t yet earned “trusted” status based on the developer’s reputation timeline, but it’s not preventing you from using it.

Think of it like buying from a new seller on an online marketplace—they might not have hundreds of reviews yet, but that doesn’t mean they’re selling bad products.

If you prefer not to see these warnings at all, you can:

  1. Go to chrome://settings/security
  2. Under “Safe Browsing,” select “Standard protection” instead of “Enhanced protection”

Note that this will turn off Enhanced Safe Browsing for all extensions and websites, not just Fluencer Fruit.

When Will This Warning Go Away?

We’re working with Google through their support channels to resolve this, but Google doesn’t provide specific timelines or milestones. Based on other developers’ experiences, it could take anywhere from 2-6 months of continued compliance for the automated system to grant trusted status.

The important thing to understand: this is a time-based reputation system, not a safety issue. We’re following all the rules and will continue to do so. The trust designation should resolve itself as our developer account matures.

More Technical Details?

We know some of you are curious about the specifics. Here’s what we’ve learned from research:

  • The warning first appeared for many users in mid-October 2025, likely due to the combination of Chrome 138’s sync feature (rolled out in June 2025) reaching more users
  • Google’s trust algorithm evaluates extensions individually, not developer accounts holistically
  • Having proper privacy policies, large user bases, or years of experience doesn’t guarantee automatic trust
  • Even OpenAI’s official ChatGPT extension has reportedly triggered this warning for some users

The warning appears exclusively for users who have Enhanced Safe Browsing enabled. If you don’t have that setting turned on, you won’t see any warnings at all.

Bottom Line

The “not trusted by Enhanced Safe Browsing” warning is frustrating for both you and us, but it doesn’t reflect any actual security concerns with Fluencer Fruit. It’s a side effect of Google’s developer reputation system combined with a new sync feature that’s showing these warnings to many more users than before.

Your email data is safe. Fluencer Fruit is safe. You can confidently click “Continue to install.”

We’re committed to maintaining the highest standards of privacy and security. If you have any concerns or questions, please don’t hesitate to reach out to us at [your support email].

Last updated: October 30, 2025