# DevTools: Console Logs & Network Requests

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.**

<div><figure><img src="/files/AANhmxEpslcjYJpnUaEM" alt="" width="375"><figcaption><p>Capture Console Logs</p></figcaption></figure> <figure><img src="/files/c1dkTeF8ONXCXaQbCXM0" alt="" width="375"><figcaption><p>Capture Network Requests</p></figcaption></figure></div>

<details>

<summary>What Happens to Sensitive Data in Network Requests?</summary>

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 such as Bearer and JWT tokens, api keys, credit card numbers, etc. 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 `***************`

<figure><img src="/files/zLQkAk4QloEMboGBmn8Z" alt=""><figcaption><p>Example of Sensitive Data Masked in Network Headers</p></figcaption></figure>

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 <security@birdie.so>.

#### Custom Keys

You can add your own custom keys to hide [in your Security Settings page](https://app.birdie.so/settings/security). \
Please note these keys are case-insensitive, and must be separated by commas.&#x20;

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.birdie.so/birdie-docs/record-my-screen/devtools-console-logs-and-network-requests.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.