What a browser extension can actually see
That "read and change all your data" warning sounds scary. Here's what it really means, a two-minute check before you install anything, and the one setting that puts you in charge.
You find a handy extension, click "Add to Chrome", and a box pops up: this extension can read and change all your data on all websites. Most people click Add anyway. Some people close the tab in a hurry. Neither is really the right move, because that warning tells you what an extension could do, not what it does.
Here's how to tell the difference.
Extensions are small programs that live in your browser
An extension is a bit of software that runs inside your browser, like Chrome. To be useful, a lot of them need to look at the page you're on. A translator has to read the text to translate it. A password manager has to find the login box. A reader mode has to see the article to tidy it up.
That's why the broad warning is so common. If a tool is meant to work on any site, the browser has no way to grant it "only the good bits". It's access to the page or no access at all.
What the warnings actually mean
Chrome groups permissions into plain-ish sentences. The ones you'll see most:
| What Chrome says | What it means in practice |
|---|---|
| Read and change all your data on all websites | It can see and edit any page you open. Needed by tools that work on any site. |
| Read and change your data on a few named sites | Same, but only on the sites listed. |
| Read your browsing history | It can see the list of pages you've visited, even ones you closed. |
| Manage your downloads | It can save files to your computer and see what you downloaded. |
| Modify data you copy and paste | It can put things on your clipboard. "Read data you copy and paste" is the one that lets it see what you copied. |
None of these are bad on their own. The question is always: does this permission match what the tool is for? A tool that turns pages into files needs the page and your downloads. A calculator that wants your browsing history is a red flag.
The two-minute check before you install
You don't need to be technical to do this. Before clicking Add:
- Open the store listing's "Privacy practices" section. In the Chrome Web Store, every extension has to say what kinds of data it collects and certify how it uses them. "Does not collect or use your data" is a good sign. A long list of data types for a simple tool is worth a second look.
- Read the privacy policy, at least the top. A good one says, in plain words, what the extension reads, when it reads it, what leaves your browser and who it's shared with. If it's vague ("we may collect information to improve our services") or there isn't one, be careful.
- Match the permissions to the job. Ask: would I expect this tool to need that? If the answer is no, skip it.
- Look at who made it. A website, a support page and recent updates suggest someone is looking after it. An unknown name, no website and no updates in years means nobody will fix it if something goes wrong.
- Notice when it wants an account. Signing in is normal for features tied to a paid plan or syncing. It shouldn't be needed just to use a simple tool.
The setting most people never touch
Here's the part that changes things: you can limit any extension after you install it. Chrome has a "Site access" setting with three choices, and it applies even to extensions that asked for every site.
Asleep until you press its button. Then it can read only the tab you pressed it on. The tightest setting.
Runs by itself only on the sites you list. Everywhere else it waits for a click.
Can read and change every site you open, without asking. Fine for tools you trust and use everywhere.
To change it:
- Click the puzzle-piece icon in the toolbar.
- Click the three dots next to the extension.
- Choose This can read and change site data, then pick When you click the extension, On [this site], or On all sites.
You can also do it from chrome://extensions: open Details on the extension and look for Site access.
A good rule of thumb: tools you use everywhere and trust can stay on all sites. Everything else can sleep until you click it. Some features may stop working with less access (anything that runs in the background, for example), so if a tool you've limited seems broken, this is the first place to look.
A note on "Load unpacked"
Some extensions, especially new ones or ones still in testing, are shared as a zip you load yourself with Developer mode and Load unpacked. That's a normal way to try software early, but it skips the store's review and the browser won't update it for you. Only do it with files from a source you trust, like the maker's own website, and remove copies you no longer use.
Tidy up every few months
Open chrome://extensions and look at the list. Anything you don't recognise or haven't used in months? Remove it. Fewer extensions means fewer things with access to your pages, and a slightly faster browser too.
The short version
- The big warning describes what an extension could do. The privacy policy and the store's "Privacy practices" tell you what it does.
- Permissions should match the job.
- You're in charge: Site access can put any extension on a short leash.
Sources: Google's help page on installing and managing extensions, and the Chrome Web Store's privacy fields and program policies for developers.
The shortcut
We hold our own extension to the same checklist. Page to Markdown turns pages, threads, AI chats and video captions into clean Markdown files. It asks for access to all sites because you might use it on any page, but it only reads a page when you click its button, use a shortcut or pick it from the right-click menu, and what you export never leaves your browser. Its privacy policy says plainly what it accesses and that your exports never come to us, and it's on the Chrome Web Store, so you can run the same two-minute check on it yourself.