Skip to content
Incident response · Template

Retention and Archiving Schedule Builder

A records retention schedule that works for incident response: record type, legal basis, retention period, archive tier, deletion method and legal-hold override, with security logs kept long enough to find out when an intrusion actually started.

Template & sample only · See the sample ↓ — a structured starting point with sample content, not legal, audit, certification or investment advice.

Template & sample only. Generated from a PlayCISO template as a starting point: it is not legal, audit, certification, investment or professional advice. Review, adapt and validate it for your organisation before you rely on it.You are looking at sample data. Replace it with your own details below — the document regenerates as you type and your copy is saved in this browser.

Build a retention schedule: for each record type, the legal basis or business reason, how long it is kept, where it is archived, how it is deleted and whether a legal hold can stop the deletion. Security logs are included on purpose: if logs expire before an intrusion is found, nobody can say when it started or what was taken. The calculator flags short log retention, automated deletion with no legal-hold override and rows with no reason or period. A preset table covers AI assistant evidence (Claude as the example): fixed provider windows, local cleanup defaults and the telemetry you have to keep yourself.

Also as
Retention controls in place (weighted)
47/100
8 of 9 items assessed
Record types scheduled
8
Log types kept under 12 months
0
Automated deletion with no legal-hold override
1
CCTV footage and badge access records
No readable retention period
0
No legal basis or reason recorded
0
No deletion method
0
AI evidence you control kept under 12 months
1
Claude Code local files (~/.claude transcripts, tool results, file snapshots) (30 days). Late-discovered AI incidents need these sources to reach back.
AI evidence with no hold or preservation path
0

Your context

Retention schedule

One row per record type. Write the period as a number and unit (90 days, 13 months, 7 years) so the calculator can read it. Sample periods are illustrative; legal requirements differ by country and sector.

AI assistant evidence (preset)

Preset rows for AI assistant and agent evidence, using Claude as the example. Some windows are fixed by the provider; the rest are whatever your own policy sets, and several only exist if switched on before an incident. Periods marked as your policy are illustrative. Source: Invictus Incident Response, Frontier Forensics: Anthropic (Oct 2026).

Control requirements

  • Security logs are kept for at least 12 months, with the most recent 90 days searchable immediatelyPCI DSS v4.0 Req. 10.5.1material

  • Log sources needed for investigations are listed and covered: identity, VPN and remote access, firewall and DNS, EDR, email, cloud audit, SaaS admin

  • Archived logs and evidence are protected from change or deletion (write-once storage or equivalent) and access is logged

  • A legal-hold process can suspend deletion for named systems, people or date ranges within one business daymaterial

  • Personal data is not kept longer than needed for its purpose, and each period has a recorded reasonGDPR Art. 5(1)(e)

  • Deletion is automated where possible, and manual deletions are recorded with date and approver

  • Suppliers holding your records follow the schedule, and return or delete data at contract end with confirmation

  • Archived data can be restored and searched within the time an investigation needs; this is tested yearly

  • The schedule is reviewed yearly and when a new system, regulation or business line is added

Policy text

Loading…

Sample report · illustrative data

Sample result: retention and archiving schedule

Example schedule for an invented freight company: one row per record type with its driver, retention period, archive tier, deletion method and legal-hold override. Periods are illustrative; confirm local law with counsel.

Retention schedule (excerpt)

Record typeRetentionArchive tierDeletion methodLegal-hold override
Incident records and forensic evidence7 yearsCold / archive (restore in days)Manual review and deletePer schedule
Backups (full)90 daysCold / archive (restore in days)Automated expiryManual only
Financial and tax records7 yearsHot then coldManual review and deleteYes, deletion suspended on hold
Employee HR files6 yearsWarm (searchable within hours)Secure wipeManual only
CCTV footage and badge access records30 daysHot (searchable now)Automated expiryNo

Summary checks the builder reports

  • Record types scheduled
  • Log types kept under 12 months
  • Automated deletion with no legal-hold override (CCTV in this example)
  • Rows with no readable retention period, no legal basis or no deletion method
  • AI assistant evidence you control kept under 12 months, and any with no hold or preservation path

Also generated

A weighted control checklist (for example security logs kept at least 12 months with the recent 90 days searchable) and a six-part policy text covering purpose, the schedule, security logs, legal hold, deletion and review.

Made-up example data. Your own run uses your inputs. Downloads of the full report need Pro.

TL;DR

What this template gives you

5 points
  • Retention schedules are usually written for privacy and tax. This one is written so an incident investigation still has the evidence it needs.
  • Security logs are kept for at least 12 months in the sample because attackers often go unnoticed for weeks or months; if the logs expire first, nobody can say when an intrusion began or what was taken.
  • Every row has a legal-hold override. The calculator flags automated deletion that a hold cannot stop.
  • Sample periods are illustrative. Confirm each one with counsel for your countries and sector.
  • An AI assistant evidence preset lists the fixed windows (Claude Activity Feed six years from enablement, CSV audit export up to 180 days with a 24-hour download link, Claude Code local transcripts 30 days by default) and the telemetry you must keep yourself. Source: Invictus Incident Response, Frontier Forensics: Anthropic (Oct 2026).

Frequently asked questions

How long should security logs be kept?

At least 12 months is a common baseline, with the most recent 90 days searchable immediately. PCI DSS asks for 12 months of audit log history with 3 months immediately available where it applies. The reason is practical: intrusions are often found weeks or months after they start, and an investigation needs logs from before the start.

What is a legal-hold override?

A way to suspend deletion of specific records when counsel expects an investigation, claim or regulatory inquiry. Without it, automated expiry can destroy evidence you are legally required to keep. The override must reach every system that deletes automatically, including log platforms and backups.

Does keeping logs longer conflict with GDPR?

Not if there is a recorded reason. GDPR's storage-limitation principle requires that personal data is kept no longer than necessary for its purpose. Security monitoring and incident investigation are recognised purposes; record the reason and the period, protect access to the logs, and delete them when the period ends.

How long is AI assistant evidence kept?

It depends on who holds it. For Claude, per Invictus Incident Response (Frontier Forensics: Anthropic, Oct 2026): the Compliance API Activity Feed keeps records six years from when it is first enabled, with no backfill; the Enterprise CSV audit export looks back up to 180 days and its download link expires after 24 hours; Claude Code local transcripts are cleaned up after cleanupPeriodDays, 30 days by default. Agent telemetry, inference-hook records and your own API request logs are kept for as long as your policy says, and only exist if you set them up before the incident.

Is this a finished document I can rely on?

No. Every tool in this suite is a template with sample content. It gives you a structured, editable starting point and generates a document from your own answers, but it is not legal, audit, certification, investment or professional advice. Review and adapt the output, and have it checked by the appropriate specialist before you rely on it.

Who can use it?

The page and sample are public. Customising the template is Pro; a free account gets 3 runs in total, shared across every Pro tool, and the generated document is free to view on the page. Download is Pro: downloading or copying the document (Word, PDF, Markdown, CSV) is never part of the free runs. Pro is $5/month or $40/year. Your work is saved in your own browser.

The tools people use most on PlayCISO.

All tools