Ask for less

Chrome Extension Permissions Explained: The Warnings Users See, the Data Rules Behind Them, and a Privacy Policy That Matches the Code

A font changer asks to read and change all your data on all websites. Some users click Add anyway. The careful ones close the tab, and they are exactly the customers a business extension needs. The permission prompt is the one part of an extension every user reads.

November 17, 2026 · 9 min read

acmeroofing.com · extension permission plan
Each feature mapped to the least access that serves it
What a fictional CRM extension asks for, and when
Sample
storage: settings and a one-hour cacheNo warning line
contextMenus: right-click "Save to CRM"No warning line
activeTab: read the open page on clickNo install warning
Host access: api.acmeroofing.com onlyIts own server
tabs, history, every websiteNot requested
Asked later, only if the feature is usednotifications, optional
Illustrative: a sample permission plan for a fictional roofing company's CRM extension

The short answer

A Chrome extension declares its permissions in the manifest. Some show no warning; others, such as tabs or broad host access, show a warning the user must accept, and adding one in an update disables the extension until the user agrees. Google's policies call for the narrowest permissions possible, a privacy policy when the extension handles user data, and prominent disclosure with consent before collection.

On this page
  1. The five manifest fields where access gets granted
  2. Install warnings, quoted exactly as Chrome shows them
  3. activeTab and optional permissions: asking at the moment of use
  4. GatorCrawl asks for two permissions and one site
  5. The update that switches your own extension off
  6. User data, Limited Use and a privacy policy that matches the code
  7. Writing the permission plan before the first line of code

The five manifest fields where access gets granted

Permissions are not one list. Chrome's guide to declaring permissions names five places in the manifest that grant access, and a careless build can widen its reach in any of them. The same page gives the reason to care in one line: "Permissions help to limit damage if your extension is compromised by malware." A narrow extension that gets hijacked can do little. A broad one can do whatever the user can.

  • permissions: named browser features such as storage, tabs or context menus, granted at install.
  • optional_permissions: the same kinds of features, but "Granted by the user at runtime, instead of at install time."
  • host_permissions: match patterns for the websites the extension may touch; Chrome notes that changes "may trigger a warning."
  • optional_host_permissions: website access requested later, only when a feature needs it.
  • content_scripts.matches: the pages where the extension's scripts run, which also counts as access to those sites.

Chrome's permission warnings page adds the distinction users actually feel: "Some permissions are less intrusive and don't display a warning. Other permissions trigger a warning that users have to allow." The job of a permission plan is to stay in the first group wherever the product allows it. Staff tools pushed out by an administrator follow the same rules, as our page on internal team extensions explains.

Install warnings, quoted exactly as Chrome shows them

These lines come from Chrome's permissions list, as of November 2026. The third column is our reading of what a cautious buyer hears.

Warning text from Chrome's permissions reference, as of November 2026
PermissionWarning Chrome showsWhat a careful user hears
tabs"Read your browsing history."This tool can see where I go
history"Read your browsing history."The same words, with a longer memory
bookmarks"Read and change your bookmarks."Why does a CRM tool need my bookmarks
notifications"Display notifications."It will interrupt me; fine if it is useful
proxy, pageCapture and others"Read and change all your data on all websites."Everything, everywhere, including my bank
storage, contextMenus, sidePanelNo warning line in the listNothing to explain at install
activeTabNo warning during installationIt acts only when I click it

One quirk is worth knowing. The same warnings page says some warnings disappear when paired with broader ones: "the "tabs" warning won't show if the extension also requests "<all_urls>"." A shorter prompt can therefore hide a bigger ask. We also do not quote the exact wording Chrome uses for access to a single named site, because the pages we read print only the all-sites version. If someone tells you the single-site text from memory, ask for the source. Our review of off-the-shelf SEO extensions applies the same reading to tools you can install today.

activeTab and optional permissions: asking at the moment of use

Chrome's activeTab documentation describes a permission that grants temporary access to the current tab "when the user invokes the extension," for example by clicking its toolbar icon, a context menu item or a keyboard shortcut. Access lasts while the user stays on that page and ends when they leave or close the tab. It shows no install warning, and it does not reach restricted pages such as chrome:// pages.

The security argument is on the same page. Without activeTab, an extension that acts on whatever page the user is reading "would need to request full, persistent access to every website." With it, an attacker who compromised the extension "would need to wait for the user to invoke the extension" before getting in. That is a real reduction, bought with no cost to the user.

Optional permissions work the same way for everything else. Chrome's permissions API reference recommends requesting declared optional permissions at run time "so users understand why the permissions are needed." It also promises an easier upgrade path: Chrome won't disable the extension when an update adds optional rather than required permissions.

Bright blue duotone of a hand holding out a single old key, framed by solid circles, half-moons and triangles
A good permission plan hands over one key at a time, when the user asks.

GatorCrawl asks for two permissions and one site

We built the GatorCrawl Keywords extension to show keyword numbers on Google search results. Its manifest requests exactly two named permissions, storage and contextMenus, neither of which carries a warning line in Chrome's list. Its host permission covers its own web app at keywords.gatorcrawlseo.com. Its content script matches one pattern, Google's search results pages, and runs nowhere else. The full build story explains each piece.

What the manifest requests

  • storage, for an hour of cached results in session storage
  • contextMenus, for the right-click "Look up keyword volume" item
  • Host access to keywords.gatorcrawlseo.com, its own API
  • A content script on Google search result pages only
  • An optional host permission, requested only for a custom app address in builds where that field is shown

What it never asks for

  • tabs or history
  • Access to every website
  • Bookmarks, downloads or cookies
  • Analytics or tracking, per its service worker's header comment: "No analytics, no tracking, no browsing history."
  • A popup; clicking the icon simply opens the options page

The optional host permission is the detail we are proudest of. The options page asks for it only when someone enters a custom web app address, and that field is hidden in store builds. A user who installs from the store never sees the request. The extension still works everywhere it needs to, because the only place it needs to is one search page and one server.

The update that switches your own extension off

Here is the trap that catches teams a year after launch. Chrome's permission warnings page says that when an update adds a new permission that triggers a warning, "the extension will be disabled until the user accepts the new permission." The Web Store's update guide says users will be prompted to accept or disable it. Picture a sales team arriving Monday to find their capture tool grayed out, each person deciding alone whether a new warning looks safe.

User data, Limited Use and a privacy policy that matches the code

Permissions decide what an extension can touch. The Chrome Web Store's data policies decide what it may do with what it touches. Four rules carry most of the weight, all as published in November 2026.

Post a privacy policy

Google's privacy policy requirement: "If your Product handles any user data, then you must post an accurate and up to date privacy policy," linked in the designated dashboard field.

Disclose before install

The disclosure rules require an extension that handles user data to prominently say what it collects and how it is used, and to obtain the user's affirmative and informed consent.

Collect only for the stated purpose

The Limited Use policy allows only data "necessary for the extension's disclosed single purpose" and prohibits using or selling it for personalized advertisements.

Send it securely

Google's troubleshooting page lists Purple Copper for an extension that "is not transmitting user data securely." Every call to your server goes over an encrypted connection.

GatorCrawl's listing shows what an honest disclosure looks like. Its privacy section says the extension handles "Personally identifiable information", "Authentication information" and "Website content", and that data is "Not being sold to third parties, outside of the approved use cases." Website content belongs on that list, since the extension reads the query and related searches from the Google page. Declaring it is the point. A disclosure that understates what the code sends is worse than none, because it is a written claim that turns out false.

Writing the permission plan before the first line of code

Every extension we build starts with a one-page permission plan, and the plan, the store disclosures and the privacy wording are part of the build price: from $1,500, depending on complexity, with a fixed written estimate before work starts. Our pricing guide breaks down what moves that number. The steps are plain.

  1. 1

    List the features, one line each

    What the user does, on which page, and what the extension shows or sends in response.

  2. 2

    Map each feature to the least access that serves it

    Prefer activeTab for anything triggered by a click, optional permissions for anything occasional, and a short host list over a wildcard. Google's use of permissions policy asks for "the narrowest permissions necessary."

  3. 3

    Write the justification as the store will show it

    One sentence per permission that a reviewer and a buyer can both check against the feature list.

  4. 4

    Draw the data map

    What leaves the browser, where it goes, how long it is kept. Keep sensitive values in memory-only session storage where possible, which Chrome's storage reference recommends for sensitive user data.

  5. 5

    Write the privacy policy from the data map

    Not from a template. The policy and the code have to say the same thing.

The store review guide covers what happens when a reviewer disagrees, and the security guide covers what permissions cannot protect against. Our build service explains the offer, and the section overview shows the kinds of extensions we make, from CRM capture tools to AI sidebars. If the extension sends data to your own systems, the connection goes live the same day through our API integration work. DataCram has been building for the web since 1999 (about us); call (210) 346-0848 or send a note.

Questions owners ask about custom browser extensions

Chrome shows that warning for broad host access and for several permissions, such as proxy and pageCapture, as listed in its permissions reference as of November 2026. It usually means the manifest uses a wildcard like <all_urls> where a short list of sites, activeTab or an optional permission would do. Narrowing it often removes the warning and shortens review.

Chrome's permissions list shows no warning line for storage, contextMenus or sidePanel, as of November 2026. Storage still holds whatever the extension saves, so it belongs in the privacy policy if it keeps user data. Chrome's storage reference suggests the in-memory session area for sensitive values.

Google's rule is that any product that handles any user data must post an accurate, up to date privacy policy and link it in the developer dashboard. An extension that signs users in or sends page content to a server handles user data. In practice nearly every business extension needs one, and it should describe what the code actually does.

Limited Use is a Chrome Web Store policy that lets an extension collect, use or transmit only the user data necessary for its disclosed single purpose. It prohibits transferring, using or selling that data for personalized advertisements. Google also gives a sample statement developers can use about adhering to the Chrome Web Store User Data Policy.

Yes, if it is declared as an optional permission. Chrome's permissions reference says Chrome won't disable an extension when an upgrade adds optional rather than required permissions. A new required permission that triggers a warning disables the extension until each user accepts it, so plan future access as optional from the first release.

When the user invokes the extension, activeTab grants temporary access to the current tab: reading its URL, title and favicon, and running scripts or inserting CSS there if the scripting permission is also declared. Access ends when the user leaves the page or closes the tab, and it does not cover restricted pages such as chrome:// pages.

Keep reading

Free · No obligation

Get a permission plan before the build

Describe what the extension needs to do and on which sites. We reply with the permissions we would request, the warnings users would see, and what the build would cost.

Which of these sounds like you? (pick any)

Rather talk now? Call (210) 346-0848.

CallGet a quote