Retention and Cleanup
Audience
Developers, QA and support engineers, data reviewers, implementation partners, solution architects, privacy reviewers and security reviewers.
Reference Content
Summary
No source-backed lifecycle retention schedule or cleanup job was found for onboarding, exit, audit/timeline, outbox, processed-event or notification delivery records.
Data classes requiring policy
| Class | Examples | Policy question |
|---|---|---|
| Candidate/onboarding | Candidate, offer, onboarding, compatibility payloads | Hiring purpose and deletion/anonymization trigger |
| Employee/workforce | Profile, employment, bank/document children | Employment and statutory retention |
| Exit | Request, reason, decisions, audit | Legal hold and dispute period |
| Audit/timeline | Context-local evidence | Immutability, redaction and archival |
| Messaging | Outbox, processed events, attempts, email queue | Replay window and bounded growth |
| Projections | Payroll/leave/attendance employee profiles | Deactivation and upstream erasure propagation |
Lifecycle
Current status
Retention duration, cleanup cadence, archive location, deletion authority, legal hold, data-subject request propagation and proof of deletion all Require confirmation.
Safety
Until policy exists, operators should not manually remove lifecycle or messaging records. Cleanup must preserve referential, audit and replay requirements and must be tested against every owning context.
Requires confirmation
Unless explicitly confirmed above, production migration governance, rollback, reconciliation, retention, privacy, performance, concurrency and operational ownership require confirmation.
Source References
microservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.csmicroservices/src/notification-service/Infrastructure/NotificationDbContext.cs
Related Articles
See Also
Keywords
- Onboarding database
- Offboarding database
- Lifecycle persistence
Revision Information
- Status: Draft
- Last reviewed: 2026-07-20
- Review cycle: Quarterly