Add to Chrome

Permissions explained

Browsers show a scary-looking permission list when you install any extension. Here’s what InTab actually uses each one for.

Site access (“read and change data on all sites”)

InTab’s writer, grammar, selection popover, screenshots, video speed pill, and YouTube tools all need to run on the pages you use them on - so it requests access to all sites. In practice, features only act when you invoke them, and content scripts run in an isolated shadow DOM so they don’t interfere with the page.

Optional - asked only when you use the feature

  • Bookmarks - for the Bookmarks panel. Not requested until you open it.
  • History - for the History panel and time analytics. Same: only on first use.

Decline either and everything else still works.

The rest, briefly

  • storage / unlimitedStorage - save your settings and data locally.
  • tabs / tabGroups - the tab manager and session save/restore.
  • downloads - image optimization and saving screenshots.
  • scripting / activeTab - inject the on-page tools where you use them.
  • contextMenus - the right-click AI actions.
  • clipboardWrite - copy screenshots and results.
  • alarms - schedule breaks, prayer times, and reports.
  • offscreen - play ambient noise and the adhan in the background.
  • sidePanel - the YouTube summaries side panel.
  • cookies - detect that you’re signed in to ChatGPT/Claude/Gemini/Perplexity for the multi-model chat.
  • idle - start the screensaver and time breaks correctly.
  • readingList / favicon / declarativeNetRequest - reading-list search, site icons, and the request tweaks the AI-chat proxy needs.

What InTab deliberately does not request

InTab does not request the debugger permission, and does not add new permissions casually - new permissions force everyone to re-approve the extension, so they’re avoided.

For what happens to your data once a feature runs, see What InTab sends & keeps.