RedHub AI
How the roll-up gate works
How the Retention Purge Scheduler gate works
This tool grades every record class's purge-due date against a pinned evaluation date, then rolls the register up to whether anything is overdue. It reads 5 classes and rolls them into one verdict — the worst, never the average — then a gate that can only make it worse.
The 5 classes
A record class under a litigation or regulatory hold is suppressed from the purge schedule no matter how far past its retention date — deleting held data is spoliation, so the hold always beats the calendar. Every other class rolls up worst-first: one class past its purge-due date puts the whole register in PURGE BACKLOG.
Why: Two of the five classes are safely within their window and one is under legal hold — but two are past their purge-due date. Chat transcripts are 6 days past (still in the 30-day grace) and lead exports are 107 days past. One class past its date puts the register in PURGE BACKLOG. The most overdue class of all — disputed-account PII at 530 days — stays off the schedule entirely because it's under hold; deleting it would be spoliation.
No single class is the crisis — the clustering is. The roll-up takes the worst, the gate escalates when trouble compounds, and it names the one thing to fix first. Schedules purges from retention periods you supply as policy — it sets no retention periods, deletes nothing, and never schedules a legal-hold class. What to keep and for how long, and what's under hold, are legal questions; confirm them with counsel. It schedules records, not people. Not legal advice.