Documentation
Data classes and retention
What REAP collects, what it does not, how long it keeps it, and how it is deleted.
Data classes
| Class | Examples | Collected | Notes |
|---|---|---|---|
| Device configuration | Running/startup configs and history | Yes | Handling of secrets in configurations masking rules |
| Command output | show commands, diagnostics | Yes | Evidence |
| Topology | Devices, links, paths, VLANs, adjacencies | Yes | |
| Telemetry | Syslog, SNMP, gNMI (opens in a new tab) metrics | Yes | Retention configurable |
| Flow records | NetFlow or IPFIX exports: source, destination, ports, protocol, bytes, packets, timestamps | Where you configure exporters | Flow metadata only; what REAP does with the flows is to be confirmed by REAP engineering; retention per the table below |
| Ticket metadata | Numbers, titles, states, assignment, timestamps, work notes REAP writes | Yes | Free-text fields in scope only as agreed |
| Documents | Runbooks, designs, conventions | Yes (agreed spaces) | Citations only; originals stay in your systems |
| Traffic payloads | Continuous packet capture, payload inspection | No | By design |
| On-demand packet captures | A capture on a switch port, requested by an engineer during an investigation | Only when requested | Kept with that investigation; retention per the table below |
| Clinical or cardholder data | No | By design; not present in the classes above | |
| Personal data | Names of engineers in tickets and logs; console users | Incidental | Covered by the DPA |
Retention
| Class | Default retention | Configurable |
|---|---|---|
| Telemetry (metrics, logs) | e.g., 90 days | Yes |
| Flow records | e.g., 30 days | Yes |
| Configuration history | e.g., 13 months | Yes |
| Investigations and audit trail | e.g., 13 months | Yes |
| Evaluation data | Deleted at the end of the evaluation within the period in the statement of work | — |
Deletion
- On request at the end of an evaluation, and on termination, within the contractual period; a deletion confirmation is provided.
- Backups age out per the backup retention period.
Engineering to confirm
- Default retention periods per class, including flow records and on-demand packet captures
- What REAP does with flow records where they are configured (enrichment, path evidence, baselines)
- Secret-masking rules at ingestion
- Backup retention and deletion confirmation format
Last reviewed: October 7, 2026 (draft) · Owner: solutions engineering · Corrections: security@reapnet.ai