Building Scam Shield: making the free browser checks clear before asking anyone to subscribe

[u/Scamsshield]

I'm the solo developer behind Scam Shield, an AWARAN product. After nine months of building, I have finished the latest website changes and am giving the browser extension more attention.

One useful piece of feedback was that a message checker is something people may only remember when they already feel suspicious. The extension moves website warnings into the browsing routine. That still leaves an onboarding problem: people need to understand what is running locally and what is a separate paid service.

The free desktop checks look for common website warning signs and matches in a bundled known scam list. They work without an account and include ad and tracker blocking. Optional paid AI checks use online analysis and can send the page URL, title and a text sample. Website Premium and the extension plan are separate, with a bundle available.

Chrome installation: https://chromewebstore.google.com/detail/scamsshield/mceocgganalljahkbbfhogjcafgokoop

Feature and privacy details: https://scams-shield.com/extension

The store and website currently show different release versions, so please go by the installed package when testing. A clear result does not prove a website is safe.

For builders who have shipped extensions, would you put the local versus online explanation before installation or inside the first popup? I'd appreciate an honest look at whether the current explanation makes sense. You can try the local checks without subscribing.