Public summary

Retention and deletion summary

Retention windows, purge behavior, and privacy/deletion workflow expectations across normal operations and request-based deletion.

Focused summaryReview-ready languageFormal follow-up available

Request retention follow-up

Back to trust center Open trust packet

Why this matters

Organizations helping people through job transitions need to know their users’ information is not hanging around forever. This summary explains the normal cleanup cycle, scheduled minimization, and the faster deletion path when someone asks for it.

Retention and deletion summary · Current public summary

Current summary

The main points a reviewer should actually take away

These points are written to be shareable and review-friendly. They give the reviewer a direct answer in plain language before the conversation turns into a longer procurement or questionnaire exchange.

Blacklight uses normal retention windows and scheduled cleanup rather than keeping full personal information indefinitely by default.

Some records are minimized or redacted on schedule even when no one files a deletion request, while deletion requests move the specific request into a faster removal workflow.

In practice, that means operational records are kept only for the period needed to deliver the service, support the request, and satisfy limited legal or security obligations before they are minimized or removed.

Next review path

Open the next document only if the review actually needs more

Start with this summary. Then move into the packet, appendix, or formal follow-up only when the reviewer needs a broader or more formal response.

Retention and deletion summary

The main points a reviewer should actually take away

Open the next document only if the review actually needs more

Use the packet when the team needs one concise review document.

Use the appendix when the reviewer needs deeper operational detail.

Use the contact flow when the public materials are no longer enough.