DevTools: Console Logs & Network Requests
Birdie DevTools for outgoing screen recordings
Birdie allows you to record your screen and automatically capture essential technical details to help engineers troubleshoot and resolve issues faster.
When you record your screen with Birdie, the following data is automatically collected:
Session and Device Metadata:
URL
Timestamp
Country
Device
Browser
Operating System
Console Logs.
Network Requests.
What Happens to Sensitive Data in Network Requests?
At Birdie, we understand that network requests may contain sensitive information—such as tokens, cookies, or personal data. That’s why we’ve designed our system with privacy and security as a top priority.
Client-Side Filtering
When Birdie captures network requests during a screen recording, we proactively scan and sanitize all requests on the client side. This means any potentially sensitive data is removed before it ever reaches our servers.
Specifically:
We filter out sensitive fields from request headers.
If the request body is in JSON format, we scan and sanitize it as well.
This ensures that sensitive values are never transmitted to Birdie’s backend.
What You’ll See in Birdie
In your Birdie recording, any fields that were flagged as sensitive will masked with ***************
This indicates that we’ve scrubbed the original value for security reasons. Filtering happens before the recording is uploaded, so no unfiltered data ever leaves the device.
A Cautious Approach
We believe it's better to over-filter than under-filter. As a result, you might occasionally see information masked that isn’t truly sensitive. If you notice something that could be improved, we’d love your feedback—just reach out to us at [email protected].
Custom Keys
You can add your own custom keys to hide in your Security Settings page. Please note these keys are case-insensitive, and must be separated by commas.
Last updated