> ## Documentation Index
> Fetch the complete documentation index at: https://docs.polymorfa.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Recorded findings

> Read retained BanSafe findings, their observation times, evidence, and acknowledgement state.

Recorded findings are retained observations from the earlier conduct evaluator.
The present Health estimator does not open, resolve, or refresh them. They are
not inputs, explanations, or point contributions to the current Health
estimate.

Read records with `GET /platform/bansafe/findings` or on one number with
`GET /platform/bansafe/health/{session}`. Both need `sessions:read`.

## Read the observation time

Use `lastSeenAt` before acting on a finding. It is the last time the earlier
evaluator observed that condition, not a statement that the condition is true
now. `firstSeenAt`, `occurrences`, and `reopenedCount` describe the retained
record's lifecycle.

Each record carries:

| Field        | Meaning                                                               |
| ------------ | --------------------------------------------------------------------- |
| `key`        | Stable identifier for the recorded check.                             |
| `title`      | Customer-readable name.                                               |
| `summary`    | Sentence built from the retained evidence.                            |
| `fix`        | Suggested change associated with that recorded check.                 |
| `severity`   | Severity recorded at the last update.                                 |
| `status`     | Retained lifecycle state: `open`, `acknowledged`, or `resolved`.      |
| `evidence`   | Bounded numeric evidence; no message content or recipient identifier. |
| `lastSeenAt` | Last observation time for this record.                                |

Console labels the section **Recorded findings** and does not add these rows to
Health band tiles or the Health column.

## Acknowledging a finding

A team owner, admin, or developer can acknowledge a record in Console, or call
`POST /platform/bansafe/findings/{findingId}/acknowledge` with a signed-in Console
session. Organization keys and project tokens receive
`403 bansafe_ack_requires_dashboard_identity`.

The body accepts an optional `note` of up to 500 characters and optional
`snoozeDays` from 1 to 30.

<Warning>
  Acknowledging records that you have seen this. It does not change Health and it
  does not lift a restriction. Health changes after new evidence; restrictions
  change when their recovery conditions are met.
</Warning>

Acknowledgement records the person and time. It does not refresh the evidence,
change the current estimate, or assert that the old condition still exists. The
request is idempotent: acknowledging an already acknowledged record preserves
the original acknowledgement details.

## Privacy

Finding evidence contains bounded counts, ratios, and timing summaries. It does
not contain message text, media, message identifiers, recipient identifiers, or
chat history.

## Related

* [BanSafe Health](/guides/bansafe/overview)
* [Safety in Console](/console/safety)
* [Safety actions and restrictions](/guides/bansafe/enforcement)