Module 12 · Security, Compliance & Ownership · 12D
Data Retention & Exit
Can we leave with our data, verifiably?
Try this
- 1Run mock final extraction
- 2Validate counts
- 3Unlock certified-deletion simulation
- Expected: Deletion step only unlocks after client validation; certificate marked SAMPLE.
Configurable retention policy
Retention schedule
| Raw pages (HTML snapshots) | days | daily, 35d | Stays in GCC region (policy) | |
| Evidence images & captures | months | daily, 35d | Stays in GCC region (policy) | |
| Transient collection files | days (max) | daily, 35d | Stays in GCC region (policy) | |
| Operational logs | months | daily, 35d | Stays in GCC region (policy) | |
| Audit events | years | WORM, 7y | Stays in GCC region (policy) | |
| Prices & mappings | contract term | contract term | daily, 35d | Stays in GCC region (policy) |
4-week handover simulation
Exit & offboarding
1 · Final extraction
Bulk + incremental export of all prices, matches, mappings, runs
2 · Client validation
Client confirms record counts and checksums BEFORE any deletion
3 · Certified deletion
Unlocked only after validation; audit log retained per policy
4 · Handover close
Knowledge transfer, runbooks, final service review
listings
4,029matches
1,368runs
1,362audit
4