Permissions Explained
When you install Brie, your browser asks you to approve certain permissions. Here's what each one does and why Brie needs it.
| Permission | Why Brie needs it |
|---|---|
| Read and change all your data on all websites | Required to capture screenshots, inject the annotation editor, and record sessions on any page you visit. Brie only activates when you trigger a capture (or when Rewind is enabled). |
Web request access (webRequest) | Captures network request/response data to include in bug reports. |
Web navigation (webNavigation) | Tracks page navigations to associate captures with the correct URL. |
Tab access (tabs, activeTab) | Reads the current tab's URL and title for slice metadata. Required for tab-level video recording. |
Storage (storage) | Stores your authentication tokens, settings, and temporary capture data locally in the browser. |
Context menus (contextMenus) | Adds "Brie - Bug Capture" to the right-click menu with Area, Fullscreen, and Window options. |
Identity (identity) | Handles the OAuth sign-in flow. |
What Brie does NOT do
- Brie does not run on pages until you trigger a capture (or enable Rewind).
- Brie does not collect or transmit browsing history.
- Brie does not inject ads or trackers.
- Brie does not modify page content (except to display the annotation editor and recording toolbar during capture).
Pro tip: You can review exactly what data Brie has captured at any time by opening a slice and checking its Console, Network, and Info tabs.