English

Retention review — disposing of closed cases, standalone risks and retired privacy subjects whose retention period has expired, and the purge and manual-delete workflow

Last updated: November 10, 2026 by Steve

Retention Review

Under the System and compliance group in Reports, the Retention review panel is where administrators dispose of closed cases whose retention period has expired — the deletion step that keeps you compliant with your records schedule. Its entry in the Reports menu carries a live count ("N closed case(s); M eligible for purge"), so you can see at a glance whether there is disposition work waiting without opening the panel.

Retention review

Pin It as a Tile

Retention review can be pinned to My Day or the Reports home like any other section, and it renders a purpose-built tile rather than generic request statistics. At the smallest size it shows the two numbers that decide whether you need to act — requests to purge and closed requests. Larger sizes add the rest of the picture: all cases to purge across the five registers, the number of documents that would be destroyed, anything held back by an open linked case, and how long the oldest item has been waiting — plus bar charts breaking eligible and closed cases down by case type.

The tile is stamped As of today rather than with the dashboard's report period, because retention eligibility is a point-in-time state: a request that expired two years ago is eligible now, whatever period the dashboard is showing.

Five Registers, One Panel

Retention covers five registers through one engine: requests, assessments, incidents, complaints, and standalone privacy risks. Retired privacy subjects are listed as Privacy subjects rows too (see below). The eligible list shows a Case type column alongside each record's number, type, close date, retention expiry date, and document count — so a single review session disposes of everything that has aged out, whatever kind of case it is.

You Set the Clock Per Type, Not Globally

Each request type, assessment type, incident type, and complaint type carries its own Retention period (months) and, where more than one date makes sense, a Retention start point — Closed date or Response sent date for requests and complaints — configured in Settings (request types under Requests; assessment, incident and complaint types under the privacy configuration panels). Standalone risks take their period from their risk category's Retention period (months), counted from the risk's Closed date.

Leaving the period blank means keep indefinitely, and that is the default: a tenant that never configures retention never purges anything. Nothing ages out until you decide it should.

What Can and Can't Age Out

Some records are excluded by construction, not by policy — the engine won't offer them:

  • An assessment is eligible only once Closed. An assessment sitting In Effect is the standing privacy record for its program, so it is never listed.
  • An Accepted risk is never eligible. Acceptance is a live posture with a sign-off and an expiry, not a finished record.
  • A risk attached to a case has no independent clock — it is deleted with its case, never on its own.

Cross-case dependencies also block disposition. An expired record that another open case still depends on — an open complaint contesting the request, an open request that a complaint contests, or a live attached risk — is listed with its block reason and refused server-side. Purging it would orphan the other side's evidence trail.

Preservation holds. A case on a preservation hold is listed as A preservation hold is placed on the case and is never purged, even if the row is ticked, until every hold on it is released. See Preservation holds.

Two tabs: Purge and Disposition. Purge is the list described here. Disposition disposes of a closed case's files before the case itself is purged, where a storage policy offers it. See Retention and disposition and Storage and archiving.

Only records whose retention expiry date has already passed appear; records with a future expiry (or none) are not shown. If nothing is eligible, the panel tells you so.

The Purge Workflow

  1. Tick the cases to dispose of. You can multi-select across case types; the running total of documents that will be destroyed is tracked as you go.
  2. Click Purge selected. A confirmation dialog states exactly how many cases and documents will be permanently deleted, behind a severe-warning banner.
  3. Confirm. Eligibility is re-checked at the moment of purge — not just when the list was drawn — so a case that was reopened between listing and confirming cannot slip through. The purge runs and a result banner reports how many succeeded and how many failed, listing the first errors if any.

Purging permanently removes the case record and all its children, including:

  • Its dependent records (assignments and tasks, allegations, measures, sections)
  • Uploaded documents, blobs, and blob storage
  • Attestations
  • Audit history
  • Converted PDFs and annotations
  • Export packages
  • The Ask AccessPoint conversations about the case

This Action Is Irreversible

Retention purge is permanent and cannot be undone — the case record, its children, its documents, and blob storage are removed. Every purge is recorded in the Purge log shown below the eligible list (case type, record, who removed it, when, and the document count), with two further columns: Removed by (Retention purge or Manual delete) and Reason (the optional free text typed into a manual delete's confirmation; blank for a retention purge). The purge log is the only surviving evidence that the record ever existed, and it is never itself purged — a defensible audit trail of your disposition actions.

Because retention purge destroys data, it should be reserved for administrators following your organisation's approved records schedule.

Deleting Records by Hand

Every register has two ways out and no third: retention disposes of a record once it is closed and its period has run, and a manual delete removes a record that should never have existed — a duplicate intake, a test case, a risk logged against the wrong program — while it is still early in its life. Nothing else destroys a case record.

Register Eligible for retention once Manual delete allowed while Permission for a manual delete
Request Closed and the period has run from the start point Draft only request.delete
Assessment Closed and the period has run — an assessment In effect never ages out Active or In review — never once In effect or Closed assessment.delete
Incident Closed and the period has run The Active stage only incident.manage
Complaint Closed and the period has run from the start point The Active stage only complaint.manage
Standalone risk Closed and the period has run — an Accepted risk is never eligible Open only risk.manage
Risk anchored to an assessment or incident Never on its own: it is deleted with its case No delete of its own — it goes with its case —

A manual delete sits in the row's ⋯ menu on each dashboard and in the ⋯ menu of the record's detail panel, and only while the record is in the state the table allows. Every delete asks for confirmation, with an optional reason, and then removes the record permanently — its children, its documents and their stored files go with it, exactly as a retention purge would. A case on a preservation hold can be neither deleted nor purged until every hold on it is released. The purge log is the only surviving evidence that a record existed, whichever way it left. A manual delete is logged there rather than in the case's own audit history, because that history is removed with the case.

The public portal's copy goes with the case. When a request, complaint or incident came in through the public portal, deleting or purging it also removes the portal submission it was registered from — and, for a request, any submission merged into it — with the files the requestor attached and the messages they wrote on it. A request's status page, its deliveries, the letters shared on the portal and its reading-room copies go too. The submission's reference then no longer opens anything on the portal.

A record decided in a built or sent release cannot be deleted from a request's Documents tab, and a release's packages cannot be deleted or cleaned up by housekeeping; they go only with the case itself.

Deleting and Retiring Privacy Subjects

A privacy subject (a program, system, initiative or AI system in Privacy program → Inventory → Subjects) leaves AccessPoint the same two ways as a case.

Delete a subject opened by mistake. Open the subject and choose … → Delete subject (needs the Delete assessments permission). The confirmation takes an optional reason. A subject can be deleted only while nothing substantive hangs off it; otherwise the dialog says what to deal with first:

What still names the subject What to do
An assessment, in any stage Nothing by hand — a subject with assessments is removed through retention after it is set to Sunset and its assessments have aged out
An incident, open or closed Unlink the subject on the incident
A request (Programs this request concerns) Remove the subject from the request
A commitment on the subject Delete it while it is still Proposed; a subject whose commitments were accepted is removed through retention
A registered system that names it as the system's own subject Clear it on the system in the Systems register

The subject's status does not matter — a subject that discovery created as Active by mistake can be deleted too. The organization-wide privacy program subject is never deleted and its type never changes: its Delete subject command is greyed out, its Type is read-only, and Retention review lists it as held back.

Retire a subject and let retention remove it. Set the subject's status to Sunset when the program, system or initiative is retired. AccessPoint records the day, shows Sunset since on the panel, and gives the inventory card a Sunset since chip. Each subject type can carry a Retention period (months) — Settings → Privacy subject choice fields → Subject types; leave it blank to keep subjects of that type indefinitely, which is the default. Once a Sunset subject's period has run from its Sunset day, it appears here as a Privacy subjects row. Moving the subject out of Sunset clears the day; setting it back starts the clock again. Subjects already in Sunset when you upgraded to 2.5.0 start their clock on the upgrade day.

A subject is held back (listed, but not purged) while it still has any assessment, an incident linked to it is not closed, a request linked to it is not closed, a commitment on it is still proposed or accepted, a registered system names it as its own subject and is not decommissioned, or it is the organization-wide privacy program subject.

Deleting or purging a subject removes its record of processing, its links to vendors, systems and controls, its data sources, compliance checklist, disclosures, commitments and translations. The vendors, systems and controls themselves are never removed. Both write a row in the purge log, and a manual delete also writes an entry in the audit ledger. A purged subject is not proposed again by discovery; a subject you delete by hand was a mistake, so its candidate becomes open again.