Read and Change All Your Data on All Websites, Explained
Chrome shows this warning for any extension that can run on every site. Here's what it allows, which extensions need it, and how to vet or limit one.
Key takeaways
- The warning means the extension can see and modify the content of any website you open in Chrome, including what you type into pages. It describes what the extension could do, not what it does.
- Ad blockers, password managers, grammar checkers, translators and text-to-speech readers really do need it. A calculator, a timer or a tool for one website does not.
- Before installing, check the publisher, the Privacy practices tab, the last update date, whether the permission fits the job, and the most recent low-star reviews.
- You can limit any extension to run only when you click it, or only on sites you choose, under Details → Site access on chrome://extensions.
- Extensions update themselves, so keep your list short and remove anything you no longer use.
You find an extension that does exactly what you need. Maybe it fixes your grammar, blocks the autoplay videos on a news site, or reads articles out loud. You click Add to Chrome, and a box appears: “Read and change all your data on all websites.”
That sentence sounds like you’re handing over the keys to everything. Sometimes that’s close to true. Usually it’s just how Chrome describes a tool that has to work on whatever page you happen to be on. This guide explains what the permission really covers, which extensions need it, how to check one before you install it, and how to rein in one you already have.
The short answer
The warning means the extension is allowed to run on every website you open. On those pages it can see the content, including text you type into forms, and it can change what the page shows. Chrome uses the same words for every extension with this access, so the warning alone doesn’t tell you whether an extension is careful or careless.
What matters is three things: whether the job actually needs every website, whether you trust the publisher, and whether the extension acts only when you ask it to. You can also cut the access down yourself in about ten seconds (see how to limit site access below).
What the permission actually covers
Extensions ask for two kinds of access. API permissions give access to browser features, like managing downloads or showing notifications. Host permissions say which websites the extension can run on. When an extension asks for every site, Chrome sums it up as “read and change all your data on all websites”.
“Read” means the extension can see what’s on the page: the article text, the comments, the email open in your webmail, and what you type into fields before you submit them. “Change” means it can add or alter things on the page. Examples include hiding an ad, inserting a button, underlining a misspelled word, or painting a highlight over the sentence being read aloud.
The permission is about web pages. It doesn’t by itself give an extension the files on your computer. But web pages are where a lot of your life is: banking, email, work tools. That’s why the warning deserves a few minutes of thought rather than a reflex click.
Why Chrome words it so broadly
Chrome can’t know in advance what an extension’s code will choose to do on each page. So the warning describes the capability, not the behavior. A reader that only touches the paragraph you select gets the same warning as a tool that quietly logs every page you visit.
Developers have narrower options when the job allows it. Google’s developer documentation points to activeTab, which gives an extension temporary access to the current tab only after you click it, and to optional permissions that you approve later. An extension that only needs the page in front of you, at the moment you click, can often avoid the scary warning entirely. One that has to work in the background, on any page, can’t.
Other warnings you might see next to it
| Warning in Chrome | What usually triggers it |
|---|---|
| Read and change your data on a number of websites | The extension lists specific sites instead of all of them |
| Read your browsing history | Access to tab details such as page addresses and titles |
| Manage your downloads | The extension can save files, for example an exported audio file |
| Modify data you copy and paste | A Copy button inside the extension |
The wording comes from Google’s permission warnings list. A warning is a prompt to ask “does this make sense for what I’m installing?”, not proof of bad intent.
Which extensions really need it
Some tools can’t do their job any other way:
- Ad and tracker blockers. They have to inspect and filter every page before you see it.
- Password managers. They fill login forms on whatever site you’re on.
- Grammar and writing checkers. They read the text you type, wherever you type it.
- Translators. They read and replace the page’s text.
- Text-to-speech readers. They read the passage you pick and often highlight words on the page as they speak. Our comparison of text-to-speech Chrome extensions shows that nearly every reader in the category asks for this access.
- Accessibility and reading tools. Examples include dark modes, dyslexia-friendly fonts and line-focus overlays. They restyle every page. Our roundup of Chrome extensions for dyslexia covers several of them.
And some shouldn’t need it at all: a calculator, a timer, a new-tab wallpaper, a screenshot tool you only use on demand, or a tool built for one website. An extension for one shopping site, for example, should only ask for that site. When the permission is much bigger than the job, that’s your cue to look harder or walk away.
A 7-point check before you install any extension
None of these takes more than a minute, and together they catch most bad bets.
1. Who publishes it? Look at the publisher name on the listing, then visit its website. Is there a real product, a privacy policy and a support contact? Google gives an Established Publisher badge to developers with a verified identity and a good track record, and a Featured badge to extensions its team has reviewed. Developers can’t pay for either. A brand-new publisher without badges isn’t automatically suspect (every product starts somewhere), but the rest of this list matters more.
2. Read the Privacy practices section. Every Chrome Web Store listing has one. The developer declares what kinds of data the extension handles (website content, browsing history, personal information and so on) and certifies how it uses them. These are self-reported, but they’re bound by store policy: Google’s rules say the disclosures must be accurate and up to date, and extensions whose disclosures contradict their behavior can be removed. If a listing says “no data collected” and the extension obviously sends your pages to a server, that’s a mismatch worth noticing.
3. Check when it was last updated. The listing shows an “Updated” date. An extension that hasn’t been touched in years may still work, but nobody is fixing its bugs or keeping up with Chrome’s changes.
4. Does the permission fit the purpose? Hold the warning up against the description. A reader, blocker or translator asking for all sites makes sense. A recipe saver asking to manage your downloads and read your history doesn’t.
5. Read the recent low-star reviews. Five-star reviews tell you little. One- to three-star reviews from the last few months are where people report surprise ads, redirected searches, a sudden paywall or a change after an update. Also notice whether the developer replies.
6. Is the code open? Some extensions publish their source code. The popular Read Aloud extension, for example, is open source. Open code isn’t a guarantee, because few people audit it, but it does mean anyone can inspect it.
7. Watch what happens after you click. A careful extension tells you what it will collect before it collects anything and asks you to agree. It acts when you trigger it, and lets you delete what it stored. If it starts sending data the moment it’s installed, without saying so, remove it.
Extensions can change after you install them
Extensions update automatically, which is mostly good: bugs get fixed without you doing anything. The flip side is that the extension you vetted last year isn’t necessarily the one running today. Extensions get sold to new owners, and developer accounts get hacked.
A real example: in December 2024, the security company Cyberhaven said an attacker had phished an employee’s Chrome Web Store account and published a malicious version of its extension. The bad update was live for roughly a day before the company pulled it, and it reached the people whose Chrome updated the extension automatically, which is nearly everyone.
Two habits help:
- Keep your list short. Every extension you don’t use is risk with no benefit. Review
chrome://extensionsevery few months and remove the leftovers. - Pay attention to Chrome’s warnings. Since Chrome 117, the extensions page flags installed extensions that the developer has unpublished or Google has taken down for a policy violation. It also flags extensions marked as malware, and Chrome disables those automatically. If Chrome tells you an extension is no longer in the store, take that seriously.
How to limit an extension’s site access
You don’t have to choose between “all websites” and “uninstall”. Chrome lets you narrow any extension:
- Type
chrome://extensionsin the address bar and press Enter. Or click the puzzle-piece Extensions icon and choose Manage extensions. - Find the extension and click Details.
- Under Site access, change “Allow this extension to read and change all your data on websites you visit” to one of these:
- On click. Google’s help page now also words this as On select. The extension can only touch the current tab after you click its icon, and only until you close that tab.
- On specific sites. Add the sites where it should always run, and nothing else.
- On all sites. The default for extensions that ask for it.
In many versions of Chrome you can also right-click the extension’s toolbar icon and change the same setting for the site you’re on.
What you give up: anything the extension did on its own. An ad blocker set to “on click” won’t block ads until you click it on each page. A password manager won’t offer to fill forms automatically. A reader may not restore its player when you come back to a page. For tools you use occasionally, that trade is often worth it. For tools that only make sense running everywhere, it isn’t.
How to remove an extension
- Right-click its icon in the toolbar and choose Remove from Chrome, or
- Open
chrome://extensions, find it, and click Remove.
Removing the extension stops it running in your browser. It doesn’t delete what the company may already have stored on its servers. If you made an account, check the publisher’s privacy policy for how to delete your data or the account itself.
A worked example: what Frateca for Chrome does with this permission
We make a text-to-speech extension, Frateca for Chrome, and it shows this same warning when you install it. So here is our own answer to the checklist above, as plainly as we can put it.
Why it asks for all websites. You can use it on any article, on any site, so Chrome has to let it run wherever you are. It uses that access for three things: to read the passage you selected, to draw the word-by-word highlighting on that page, and to bring the player back when you reopen a saved page or restart the browser.
When it acts. Only when you choose one of its two actions: Listen to selected text or Save full page to Frateca. Before you can use either, the extension shows a short notice about what it sends and asks you to click Agree and continue. Pages you never act on are never sent.
What leaves your browser. The text you selected, or the page you saved, plus that page’s address and title. These go to Frateca’s servers, where the audio is generated. The address is what lets Open page take you back to the source later.
What it declares on the store. Its Privacy practices section lists personal information, authentication information, web history, user activity and website content. Personal and authentication information cover your account and sign-in session. “Web history” means the address and title of pages you choose, not a log of everything you visit. User activity is your library and playback state, and website content is the text you send.
What it isn’t used for. Your data isn’t sold and isn’t used for advertising. Saved items stay in your library until you delete them, and you can delete single items or your whole account. Details are in the privacy policy.
If you set it to “On click”. The right-click actions are things you trigger yourself on the tab you’re reading. What may stop working is the automatic part: restoring the highlight and player when you reopen a saved page with Open page, or after a browser restart. We haven’t tested every combination of these settings. If something you rely on stops working, switch the site access back. For other playback problems, see Chrome read aloud not working.
If you’d like the step-by-step tour of the extension itself, the Frateca Chrome extension guide covers it. For the wider question of where your text goes with any reading tool, including apps and built-in readers, see is text-to-speech private?
The bottom line
“Read and change all your data on all websites” is a description of reach, not a verdict. Plenty of the most useful extensions need it, and some of the worst ones have it too. Match the permission to the job, check who’s behind it and what they declare, and keep an eye on reviews after updates. And remember that you’re allowed to turn the dial down. An extension you use twice a week rarely needs to run on every site, every minute.
Stop reading. Start listening.
Frateca turns PDFs, articles, textbooks and web pages into natural audio you can play anywhere: on your commute, at the gym, or while you cook. Free plan included, no card required.
iOS · Android · Web · Chrome extension · Free plan, no credit card required