本文へ移動
cccskills
無料GitHub で公開

retention-schedule

Designs and implements data retention schedules compliant with GDPR Article 5(1)(e) storage limitation principle. Maps data categories to retention periods with legal basis justification, regulatory minimum holding periods, and automated review triggers for schedule maintenance. Activate for retention policy, storage limitation, data lifecycle, retention period queries.

インストール方法を見る

含まれるファイル(5)

  • SKILL.md12.8 KB
  • assets/template.md1.6 KB
  • references/standards.md2.8 KB
  • references/workflows.md3.2 KB
  • scripts/process.py11.8 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Data Retention Schedule Design and Implementation

Overview

A data retention schedule is the foundational governance document that specifies how long each category of personal data is retained, the legal basis for that retention period, and the triggers for review or deletion. GDPR Article 5(1)(e) establishes the storage limitation principle: personal data shall be kept in a form which permits identification of data subjects for no longer than is necessary for the purposes for which the personal data are processed. This skill provides the complete framework for building, maintaining, and enforcing a category-based retention schedule.

Legal Foundation

GDPR Article 5(1)(e) — Storage Limitation

Personal data shall be kept in a form which permits identification of data subjects for no longer than is necessary for the purposes for which the personal data are processed. Personal data may be stored for longer periods insofar as the personal data will be processed solely for archiving purposes in the public interest, scientific or historical research purposes, or statistical purposes in accordance with Article 89(1), subject to implementation of appropriate technical and organisational measures.

GDPR Recital 39 — Storage Limitation Elaboration

Personal data should be adequate, relevant, and limited to what is necessary in relation to the purposes for which they are processed. Personal data should be processed only if the purpose of the processing could not reasonably be fulfilled by other means. In order to ensure that the personal data are not kept longer than necessary, time limits should be established by the controller for erasure or for a periodic review.

GDPR Article 13(2)(a) and Article 14(2)(a) — Transparency

The controller shall provide the data subject with the period for which the personal data will be stored, or if that is not possible, the criteria used to determine that period.

GDPR Article 30(1)(f) — Records of Processing

Where possible, the envisaged time limits for erasure of the different categories of data must be recorded in the Records of Processing Activities.

Retention Schedule Construction

Step 1: Data Inventory and Categorization

Identify and categorize all personal data processed by the organization:

Category IDData CategoryExample Data ElementsProcessing PurposeLegal Basis (Art. 6)
CAT-001Employee HR RecordsName, address, NI number, salary, performance reviewsEmployment administrationArt. 6(1)(b) Contract + Art. 6(1)(c) Legal obligation
CAT-002Customer Account DataName, email, phone, address, account preferencesService deliveryArt. 6(1)(b) Contract
CAT-003Customer Transaction RecordsPurchase history, payment details, invoicesContract performance and legal obligationArt. 6(1)(b) Contract + Art. 6(1)(c) Legal obligation
CAT-004Marketing Contact DataName, email, consent records, campaign interactionsDirect marketingArt. 6(1)(a) Consent
CAT-005Website AnalyticsIP address, device data, browsing behaviour, cookiesWebsite optimizationArt. 6(1)(f) Legitimate interest
CAT-006Job Applicant DataCV, cover letter, interview notes, referencesRecruitmentArt. 6(1)(b) Pre-contractual steps
CAT-007CCTV FootageVideo recordings of premisesSecurity and safetyArt. 6(1)(f) Legitimate interest
CAT-008Supplier Contact DataName, email, phone, company, contract termsVendor managementArt. 6(1)(b) Contract
CAT-009Customer Support RecordsTickets, correspondence, complaint recordsService delivery and qualityArt. 6(1)(b) Contract + Art. 6(1)(f) Legitimate interest
CAT-010Financial and Tax RecordsAccounts, tax filings, audit reports, bank statementsLegal complianceArt. 6(1)(c) Legal obligation

Step 2: Determine Retention Periods

For each data category, determine the retention period based on:

  1. Statutory minimum: Legal requirements mandating minimum retention (e.g., tax records: 6 years under HMRC requirements).
  2. Contractual necessity: Duration of the contract plus any post-contractual obligations.
  3. Limitation periods: Time within which legal claims may be brought (e.g., 6 years for contract claims under Limitation Act 1980 in the UK; 3 years for tort claims).
  4. Regulatory requirements: Sector-specific retention mandates (e.g., FCA record-keeping rules, MiFID II requirements).
  5. Legitimate business need: Justifiable operational necessity beyond legal minimums (must be documented and proportionate).

Step 3: Retention Schedule Matrix

The following is the retention schedule for Orion Data Vault Corp:

Category IDData CategoryRetention PeriodLegal Basis for RetentionRetention TriggerReview Frequency
CAT-001Employee HR RecordsDuration of employment + 6 yearsLimitation Act 1980 s.5 (contract); Employment Rights Act 1996Employment termination dateAnnual
CAT-002Customer Account DataDuration of account + 2 yearsContractual necessity; limitation period bufferAccount closure dateAnnual
CAT-003Customer Transaction Records6 years from transaction dateHMRC record-keeping; Companies Act 2006 s.386; Limitation Act 1980Transaction completion dateAnnual
CAT-004Marketing Contact DataUntil consent withdrawn + 30 days processingConsent-based; deletion upon withdrawalConsent withdrawal date or 24 months since last engagementBiannual
CAT-005Website Analytics26 months from collectionICO guidance; CNIL recommendation on analytics cookiesData collection dateAnnual
CAT-006Job Applicant Data6 months from recruitment decision (unsuccessful); duration of employment + 6 years (successful)ICO Employment Practices Code; limitation period for discrimination claims (6 months from decision)Recruitment decision dateAfter each recruitment cycle
CAT-007CCTV Footage30 days from recording (standard); up to 6 months if incident flaggedICO CCTV Code of Practice; proportionality principleRecording dateMonthly
CAT-008Supplier Contact DataDuration of contract + 6 yearsLimitation Act 1980; contractual necessityContract termination dateAnnual
CAT-009Customer Support Records3 years from case closureLegitimate interest; limitation period for service-related claimsCase closure dateAnnual
CAT-010Financial and Tax Records6 years from end of financial year (standard); 20 years (deeds and title documents)HMRC requirements; Companies Act 2006 s.388; Limitation Act 1980 s.8End of relevant financial yearAnnual

Step 4: Retention Period Justification Template

For each retention period exceeding the minimum statutory requirement, document the justification:

RETENTION PERIOD JUSTIFICATION — Orion Data Vault Corp
------------------------------------------------------
Category: [CAT-XXX — Category Name]
Proposed Period: [X years from trigger event]
Statutory Minimum: [X years, cite statute]
Proposed Excess: [X additional months/years]

Justification for Excess Period:
1. [Specific business need — e.g., contractual warranty period extends 12 months beyond statutory minimum]
2. [Risk assessment — e.g., historical claims data shows 3% of claims filed in year 5-6]
3. [Regulatory expectation — e.g., FCA expects retention beyond statutory minimum for conduct risk purposes]

Proportionality Assessment:
- Volume of data subjects affected: [number]
- Sensitivity of data: [low/medium/high]
- Risk to data subjects from extended retention: [assessment]
- Mitigating measures: [e.g., access restriction, pseudonymization after statutory minimum]

Approved by: [DPO Name]
Date: [YYYY-MM-DD]
Next Review: [YYYY-MM-DD]

Retention Review Triggers

Automatic Triggers

The following events trigger an immediate review of the applicable retention period:

  1. Retention period expiry: Automated alert 30 days before the retention period for any data category expires.
  2. Legislative change: Any amendment to statutes cited as the legal basis for a retention period (e.g., changes to Companies Act, tax legislation, sector-specific regulations).
  3. Regulatory guidance update: Publication of new ICO, EDPB, or sector-specific regulatory guidance on retention.
  4. Purpose change: Any change to the purpose for which data in a category is processed.
  5. Data breach: Following a data breach involving a data category, review whether the retention period contributed to the scope of the breach.
  6. Data subject complaint: Complaint or challenge from a data subject regarding the retention period for their data.
  7. Litigation or regulatory investigation: Commencement of legal proceedings or regulatory investigation affecting a data category.

Scheduled Review Cycle

Review TypeFrequencyScopeResponsible
Category-level reviewAs per schedule (see retention matrix)Individual data category retention period, legal basis, and justificationData Owner + DPO
Full schedule reviewAnnual (Q1)Entire retention schedule, all categories, legislative scanDPO + Legal + IT
Regulatory alignment checkBiannualCross-reference retention periods against current statutory requirementsLegal Counsel
Technical compliance auditAnnual (Q3)Verify that automated deletion and archiving systems enforce scheduled periodsIT + DPO

Implementation Guidance

Technical Implementation

  1. Metadata tagging: Every data record must carry metadata indicating its data category (CAT-XXX), creation/collection date, retention trigger date, and calculated deletion date.
  2. Automated monitoring: Deploy retention monitoring that scans data stores against the retention schedule and flags records approaching or exceeding their retention period.
  3. Deletion queue: Records exceeding their retention period enter an automated deletion queue with a 14-day grace period for review before permanent deletion.
  4. Audit logging: All retention actions (creation, review, extension, deletion) must be logged with timestamp, actor, and justification.
  5. Suppression lists: Maintain suppression records for deleted data subjects to prevent re-collection where appropriate (e.g., marketing opt-out lists).

Governance Requirements

  1. Data owners: Each data category must have a designated data owner responsible for reviewing and approving retention periods.
  2. DPO oversight: The Data Protection Officer reviews and approves all retention periods and any exceptions.
  3. Board reporting: Retention schedule compliance metrics (percentage of data within retention period, volume of data deleted, exceptions granted) are reported to the board quarterly.
  4. Training: All staff who handle personal data must receive training on the retention schedule applicable to their function, refreshed annually.

Common Retention Period Reference (EU/UK)

RequirementStatutory PeriodSource
Tax records (UK)6 years from end of accounting periodHMRC; TMA 1970 s.34
Company accounting records6 years from end of financial yearCompanies Act 2006 s.388
Employment records (general)6 years from terminationLimitation Act 1980 s.5
Payroll records6 years from end of tax yearIncome Tax (PAYE) Regulations 2003
Health and safety records40 years from last entryCOSHH Regulations 2002; Ionising Radiations Regulations 2017
Anti-money laundering records5 years from end of business relationshipMoney Laundering Regulations 2017 reg.40
Consumer contracts6 years from breachLimitation Act 1980 s.5
Personal injury claims3 years from date of knowledgeLimitation Act 1980 s.11
Discrimination claims (employment)6 months from act complained ofEquality Act 2010 s.123
CCTV footage30 days (ICO guidance)ICO CCTV Code of Practice
Pension records6 years from end of scheme year (minimum); 12 years recommendedPensions Act 2004; Limitation Act 1980

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Implements 42 CFR Part 2 protections for substance use disorder patient records. Covers written consent requirements stricter than HIPAA, re-disclosure prohibition, court order procedures, qualified service organization agreements, and 2024 amendments aligning Part 2 with HIPAA. Keywords: 42 CFR Part 2, substance use disorder, SUD records, re-disclosure, consent, Part 2 amendments.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Guides assessment of third-country adequacy decisions under GDPR Article 45 for international data transfers. Covers the current EC adequacy decisions list, adequacy assessment criteria, partial adequacy handling, and monitoring of adequacy decision reviews. Keywords: adequacy decision, Article 45, third country, adequate protection, EC adequacy list.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Implements age-gating mechanisms for online services to restrict access based on user age. Covers hard gates versus soft gates, neutral age prompts, re-verification triggers, circumvention prevention, and regulatory requirements under GDPR, COPPA, UK Online Safety Act, and DSA. Keywords: age gate, age restriction, neutral prompt, children, online services, access control.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Evaluates and implements age estimation and verification technologies for online services. Covers facial age estimation, digital ID verification, self-declaration with risk assessment, AI-based age estimation, and the accuracy versus privacy tradeoff. Includes ICO guidance and euCONSENT framework. Keywords: age verification, age estimation, facial analysis, digital ID, children, online safety.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Preparing EU AI Act compliance documentation for high-risk AI systems. Covers Annex III classification, technical documentation under Art. 11, conformity assessment, risk management systems, and CE marking requirements. Keywords: EU AI Act, high-risk AI, Annex III, conformity assessment, CE marking.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

Implements GDPR Art. 22 automated decision-making and AI Act Art. 14 human oversight requirements for AI systems. Covers identification of solely automated decisions, meaningful human intervention design, logic explanation mechanisms, and contestation procedures. Keywords: Art. 22, automated decision, human oversight, AI Act, profiling, contestation.

日本語の概要は準備中です。原文の説明を表示しています。

mukul975/Privacy-Data-Protection-Skills3032026年3月17日 更新

mukul975 のスキルをすべて見る

このスキルの問題を報告する