Permissions Explained

Takt requests only the permissions it needs. Here's what each one does and why.

Required permissions #

These are granted at install time and are necessary for core functionality:

Permission Why
activeTab Read the current tab when you trigger a popup action (e.g. hibernate this tab, create a rule from it)
tabs Read tab URLs and titles to match against your rules
tabGroups Create and manage Chrome tab groups
storage Save your rules, settings, and profiles
contextMenus Right-click "Create rule from this tab" menu item
scripting Inject the duplicate-prevention toast notification
notifications Alert you when tab groups exceed memory budgets
alarms Periodic budget checks and scheduled profile switching

Optional permissions #

These are requested at runtime only when you enable features that need them:

Permission Why Triggered by
<all_urls> Measure per-tab memory and monitor network requests in the resource dashboard. Also enables in-page prompts in Manual automation mode. Opening the resource dashboard or enabling Manual mode
webRequest Count network requests and detect background activity per tab in the resource dashboard. Opening the resource dashboard
webNavigation Detect navigation for duplicate tab prevention Enabling duplicate prevention
system.memory Show total system memory in the resource dashboard Opening the resource dashboard
identity Obtain an OAuth token to read and write Takt's private sync file in your Google Drive App Data folder. No other Drive files are accessed. Enabling Google Drive Sync
bookmarks Create a "Takt Bookmarks" folder and save a group's tabs as bookmarks. No existing bookmarks are read or modified. Using "Save group as bookmarks"
history Search your browsing history in Quick Switch (Alt+Shift+Space) and surface frequently-visited domains in rule suggestions. History data is never stored beyond the session or transmitted externally. Enabling browsing history search

How to manage permissions #

Open the Options page and go to Settings. The permissions panel lets you:

Revoking a permission disables the feature that depends on it. The feature re-enables automatically when the permission is granted again.

What Takt never accesses #

For the full privacy story, see the Privacy Policy.