# Evidence & retention policy

Evidence storage is designed for auditability and traceability.

```mermaid
flowchart TB
  EVT[All events: metadata JSON] --> DB[(Edge event DB: indefinite)]

  FAIL[FAIL/REVIEW events] --> FRAMES[Defect frames + boxes]
  FRAMES --> EDGEFS[(Edge storage: typical 90 days)]
  EDGEFS -->|archive/sync| OBJ[(Site object storage: long-term)]

  RCA[RCA triples] --> PG[(Site Postgres: indefinite)]
  DB -->|sync| PG

  RAW[Optional raw video ring buffer] --> RING[(Edge storage: typical 7 days overwrite)]
```

### Notes

* Retention periods vary by deployment.
* Evidence references remain stable, even if media is archived.
* Sensitive data handling follows the security controls in place.

### Next steps

* [Evidence packaging](/doc/intelfactor-ai/architecture-and-data/evidence-packaging.md)
* [Data flow](/doc/intelfactor-ai/architecture-and-data/data-flow.md)
* [Security model](/doc/intelfactor-ai/operations-and-security/security-model.md)


---

# 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://intelfactor.gitbook.io/doc/intelfactor-ai/architecture-and-data/evidence-and-retention-policy.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.