Map data retention requirements across [Jurisdictions] for [DataTypes] considering [RegulationsList]. Define default retention, event-based retention (e.g., last activity), and exceptions under legal hold managed via [LegalHoldProcess]. Identify conflicts (minimum vs. maximum retention) and propose a defensible disposition approach. Include approval workflow and record of processing updates with [DPO_Name] oversight.
Output format:
Retention Mapping Table: Data Type | Jurisdiction | Law/Clause | Min/Max | Default | Exceptions | Notes.
Decision Tree (textual) for applying retention vs. hold.
Evidence & Audit Log fields required.
Change Management steps when laws update.
Provide unambiguous definitions to enable automation in backup platforms and information governance tools.