> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/product-guides-and-integrations/product-guides/luciq-pii-masking/sensitive-data-findings.md).

# Sensitive Data Findings

Review sensitive data Luciq detected in your crash reports, jump to the log entry it came from, and ignore or reopen findings from your app settings.

Sensitive Data Findings detects leaks that happen in your app and are reported to Luciq. Today it covers Crash Reporting: Luciq scans the console logs and network logs attached to your crash reports for sensitive data, such as API keys, tokens, and credentials. Each kind of match is grouped into a single **finding**, so you can see what leaked, where, and how often, without opening reports one by one.

* Find secrets that your app writes to console logs or sends in network requests.
* See how many reports and app versions a finding affects.
* Jump straight to the log entry that contains the value.
* Ignore findings you've reviewed and confirmed are safe.

{% hint style="info" %}
Sensitive Data Findings currently covers Crash Reporting only, and detects leaks in console logs and network logs. It's available per app token, and the page isn't shown for apps where it isn't enabled. Findings cover the last 90 days.
{% endhint %}

### View your findings

Go to **Settings** > **App settings** > **Data privacy** > **Sensitive data findings**.

The page has two tabs, each with a count:

* **Unresolved**: Findings you haven't ignored.
* **Ignored**: Findings you've ignored.

If nothing was detected, the **Unresolved** tab shows **All clear**.

<figure><img src="https://2991836969-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCha1KrkvNKPdcC0aGvuB%2Fuploads%2Fgit-blob-7a2e53071ddc3230fb7014aca7003a7013a6b532%2Fsensitive-data-findings-list.png?alt=media" alt="The Sensitive data findings page in app settings, showing the Unresolved tab with a table of findings."><figcaption></figcaption></figure>

Each finding is one row in the table:

* **Finding**: The kind of data detected, labeled with where it was found, either **Console log** or **Network log**.
* **Severity**: **High**, **Medium**, or **Low**.
* **Reports**: The number of crash reports the finding appears in.
* **App version**: The app version, or the number of versions when the finding appears in more than one.
* **First seen** and **Last seen**: How long ago the finding was first and last detected, such as `4h`, `2d`, or `2mo`.

Findings are grouped by the kind of data detected and the log it appears in. You can sort the table by **Severity**, **Reports**, **First seen**, or **Last seen**.

### Investigate a finding

Select a row to open its details. Use the arrows at the top to move between findings.

<figure><img src="https://2991836969-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCha1KrkvNKPdcC0aGvuB%2Fuploads%2Fgit-blob-dd006da3e28825135cae658d0d89d981d7ec6406%2Fsensitive-data-findings-details.png?alt=media" alt="The details panel for a JSON Web Token finding, showing sample reports with the value redacted and advice for your engineer."><figcaption></figcaption></figure>

The details show:

* **Detected in N reports**: A sample of the reports the finding appears in. Each one shows the surrounding log text with the sensitive value replaced by `[REDACTED]`, the crash number, how long ago it happened, and the app version. Select **Show all** to see the rest.
* **What your engineer needs to do**: Advice for fixing the leak. For console logs, remove the value from your logging or redact it before it's logged. For network logs, stop sending the value in requests the SDK logs, or mask its header or query key. See [Network Log Masking](https://docs.luciq.ai/product-guides-and-integrations/product-guides/luciq-pii-masking/network-log-masking.md).

Select a crash to open its occurrence. When Luciq knows which log entry holds the value, the occurrence opens on the logs, filtered to that log type, scrolled to the entry and highlighted.

<figure><img src="https://2991836969-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCha1KrkvNKPdcC0aGvuB%2Fuploads%2Fgit-blob-a459b7ad05d82b02d8a1ba4ab54f9add02d4fdee%2Fsensitive-data-findings-log-entry.png?alt=media" alt="The Logs section of a crash occurrence, with the console log entry that contains the sensitive value highlighted."><figcaption></figcaption></figure>

### Ignore a finding

If you've reviewed a finding and it's safe, select **Ignore** on its row or in its details. The finding moves to the **Ignored** tab.

{% hint style="warning" %}
Ignore applies to the whole kind of data, not just the row you selected. It hides that kind of data in both console and network logs, and Luciq stops recording new matches for it while it's ignored.
{% endhint %}

To undo it, open the **Ignored** tab and select **Reopen**. The finding returns to **Unresolved** with its history intact.

The **Ignored** tab only shows findings you ignore from this page. Ignore rules scoped to a specific endpoint, text, or pattern, created elsewhere, don't appear on it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.luciq.ai/product-guides-and-integrations/product-guides/luciq-pii-masking/sensitive-data-findings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
