Privacy

Why Your Browser Extension Should Never See Your Passwords: A Guide to Extension Privacy

Why extensions need broad permissions at all

A grammar-checking or text-expander extension needs to work on any website you type on — that's the whole point. To do that, it has to request access to run on all sites ("host permissions"), which sounds alarming out of context but is genuinely necessary for the feature to work at all. The question isn't whether an extension requests broad access — most useful ones do — it's what it actually does with that access.

What a well-behaved extension does with page access

Red flags worth checking for

How to actually check before installing

  1. Read the requested permissions listed on the extension's store page — not just the star rating.
  2. Open the linked privacy policy and check whether it specifically explains what happens to your typed text, not just generic legal boilerplate.
  3. Check whether the developer is identifiable (a real company or named developer, not an anonymous listing).

What "local-only" storage actually means

Some extensions store your settings and data only in your browser's local storage, meaning it never leaves your device unless the extension explicitly sends it somewhere for a specific feature (like sending text to an AI API you've configured). This is a meaningfully different privacy model than an extension that syncs everything to its own servers by default — worth checking for specifically if privacy matters to you.

Spellro stores your API key and shortcuts locally in your browser only, and sends text directly to your own AI provider — never through Spellro's servers, because there aren't any. Read the full privacy policy.

Add to Chrome