Anyone who adds or updates their Birdie extension, new users and existing alike, are going to be caught off guard by permission modal that looks like this:
We understand that permissions requests can catch you off guard, so here’s a clear explanation of why Birdie asks for these permissions, how they’re used, and why you can trust us 👇
Permissions Requested by Birdie
1. Access the page debugger backend
This allows Birdie to capture technical details, such as console logs and network activity, which are essential for helping you troubleshoot issues effectively.
2. Read and change all your data on all websites
We know this permission sounds alarming, but it’s actually a common and necessary requirement for screen recording tools. Here’s why Birdie needs it:
Content Scripts: Like many Chrome extensions, Birdie uses "content scripts" to run code in the pages you visit. This is necessary to integrate Birdie’s recording controls and UI seamlessly into your browser experience.
Full Web Coverage: To allow you to record on any website, our code must be able to operate on all pages. Chrome describes this broadly as "read and change all your data on all websites," but in reality, Birdie only interacts with pages when you actively start a recording.
This permission is standard for video recording extensions, and while the Chrome messaging can seem intimidating, it’s intentionally written to encourage security awareness.
3. Capture the content of your screen
This is essential for Birdie to record your screen and provide the video content you need to troubleshoot and resolve issues.
Your Privacy Matters
At Birdie, your privacy and security are our top priorities. Without your trust, we couldn’t exist.