> For the complete documentation index, see [llms.txt](https://intelfactor.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://intelfactor.gitbook.io/docs/intelfactor-ai/architecture-and-data/evidence-and-retention-policy.md).

# Evidence & retention policy

What we store, where it lives, and typical retention patterns.

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](/docs/intelfactor-ai/architecture-and-data/evidence-packaging.md)
* [Data flow](/docs/intelfactor-ai/architecture-and-data/data-flow.md)
* [Security model](/docs/intelfactor-ai/operations-and-security/security-model.md)