Permissions Explained
Raft requests only the permissions it needs. Here's exactly what each one does.
tabs
Lets Raft see your open tabs — URLs, titles, and states (pinned, audio playing).
Why: Core to saving sessions, suspending inactive tabs, and applying protection rules.
We never send your tab data anywhere. Everything stays local.
tabGroups
Lets Raft read and restore Chrome's tab groups.
Why: To preserve group names, colors, and collapsed state when saving and restoring sessions.
storage
Lets Raft save data to your browser's local storage.
Why: Sessions, settings, and tab activity data persist between browser restarts.
This storage is entirely local to your browser.
alarms
Lets Raft set background timers.
Why: Auto-suspension checks and auto-save run on a schedule, even when the popup is closed.
No tracking or heartbeats to external servers. Purely local timers.
contextMenus
Adds "Suspend this tab" and "Suspend other tabs" to Chrome's right-click menu.
Why: Quick access to suspension without opening the popup.
identity
Lets Raft use Chrome's built-in OAuth to connect to Google Drive.
Why: Optional cloud sync (Pro feature). Uses Chrome's secure identity system — Raft never sees your Google password.
We only access a private app-data folder. We cannot see your Drive files, email, or contacts.
googleapis.com host permissions
Lets Raft communicate with Google's OAuth and Drive APIs.
Why: To complete sign-in and upload/download encrypted sessions.
All session data is encrypted before upload. These APIs are not used for tracking.
Permissions We Don't Request
history — We don't need your browsing history. Only open tabs matter.
bookmarks — Sessions are managed separately from bookmarks.
webRequest — We don't inspect or modify web traffic.
<all_urls> — We don't inject scripts into pages. We only need tab metadata.
Questions? Open an issue or email privacy@raftapp.io.