data-retention
Design data retention and deletion policies with regulatory basis for each data type. Use when a client needs to define how long different data categories are kept, when they are deleted, and what the regulatory or business justification is.
What this skill does
# Data Retention and Deletion Policy Design Design a complete data retention and deletion policy covering inventory, regulatory minimums, retention schedule, legal hold procedures, deletion runbook, and technical implementation guidance. ## Step 1: Data Inventory Identify and classify all data types the client holds. For each, document: | Data Category | Subcategory | Format | Storage Location | Contains PII? | Regulatory Category | |--------------|-------------|--------|-----------------|--------------|---------------------| | Customer PII | Contact info | DB records | CRM, AMS, LOS | Yes | GLBA, state privacy | | Customer PII | SSN/Tax ID | Encrypted DB | Core system | Yes — sensitive | GLBA, FCRA | | Transactions | Policy premiums | DB records | AMS | Yes | State DOI | | Transactions | Loan origination | DB + documents | LOS + file storage | Yes | RESPA, TRID | | Communications | Email correspondence | Email archive | Exchange/O365 | Maybe | FINRA 4511, state | | Communications | Recorded calls | Audio files | Call recording platform | Maybe | State recording law | | Audit logs | System access | Log files | SIEM | Partial | SOX, SOC 2 | | Financial records | Ledger entries | DB records | Accounting system | No | SOX, tax | | Documents | Applications | PDF/scanned | Document management | Yes | Varies by type | | Documents | Policy/loan docs | PDF | Document management | Yes | State DOI, RESPA | | Documents | Adverse action notices | PDF | Document management | Yes | ECOA, FCRA | | Claims records | FNOL and adjuster notes | DB + docs | Claims system | Yes | State DOI | | Marketing | Prospect data | CRM | CRM | Yes | CCPA, CAN-SPAM | | HR | Employee records | HR system | HRIS | Yes | State labor law | ## Step 2: Regulatory Minimum Retention by Data Type ### Insurance | Record Type | Minimum Retention | Clock Starts | Citation | |-------------|------------------|--------------|---------| | Policy files (all lines) | 5 years | Policy expiration | Most state DOI regulations | | Policy files (life insurance) | 6 years | Policy expiration | Many states — use most restrictive | | Claims files | 5 years | Claim closure | State DOI (varies; verify per state) | | Agent licensing records | 3 years | License termination | NAIC Producer Licensing Model Act | | Market conduct records | 5 years | Record creation | State DOI market conduct exams | | Premium tax records | 4 years | Tax filing | State DOI / state revenue dept | | Complaint records | 5 years | Complaint closure | Most state DOI regulations | | Advertising/marketing materials | 3 years | Last use | State DOI unfair trade practices | | Surplus lines affidavits | 3–5 years | Filing date | State surplus lines law (varies) | ### Mortgage | Record Type | Minimum Retention | Clock Starts | Citation | |-------------|------------------|--------------|---------| | Loan application and disclosures | 3 years | Consummation or action taken | Reg Z § 1026.25 | | TRID Loan Estimates and CDs | 3 years | Consummation | Reg Z § 1026.25(c) | | RESPA servicing records | 2 years | Date of action | Reg X § 1024.38 | | HMDA Loan Application Register | 3 years | LAR submission | Reg C § 1003.5(b) | | ECOA adverse action notices | 25 months | Date notice given | Reg B § 1002.12 | | FCRA adverse action notices | 5 years | Date notice given | FCRA § 1681p | | BSA/AML Currency Transaction Reports | 5 years | Filing date | 31 CFR 1010.430 | | BSA/AML Suspicious Activity Reports | 5 years | Filing date | 31 CFR 1020.320 | | BSA Customer Identification records | 5 years | Account closure | 31 CFR 1020.220 | | QM/ATR income/asset documentation | 3 years | Consummation | Reg Z § 1026.43(e)(4) | | MERS registration records | Life of loan + 7 years | Payoff/transfer | MERS operating procedures | ### Financial Services / General | Record Type | Minimum Retention | Clock Starts | Citation | |-------------|------------------|--------------|---------| | FINRA customer account records | 6 years | Account closure | FINRA Rule 4511 | | FINRA communications (general) | 3 years | Creation (first 2 years easily accessible) | FINRA Rule 4511 | | FINRA order tickets | 3 years | Order date | FINRA Rule 4511 | | SEC investment advisor records | 5 years | Creation | 17 CFR 275.204-2 | | SOX financial records | 7 years | Fiscal year end | SOX § 802 | | Tax records | 7 years | Tax filing | IRS general guidance | | GLBA privacy notices | 6 years | Issuance | 16 CFR Part 314 | | Employment records | 4–7 years | Employment end | State labor law (varies) | ## Step 3: Retention Schedule Build the master retention schedule combining regulatory minimums with business requirements. Apply the most restrictive applicable period. **Retention period table format:** | Data Category | Business Minimum | Regulatory Minimum | Regulatory Citation | Approved Maximum | Active Storage | Archive Storage | Delete Action | |--------------|-----------------|-------------------|---------------------|-----------------|----------------|-----------------|---------------| | [Category] | [N years] | [N years] | [Citation] | [N years] | [N years] | [N years after archive] | [Auto-delete / Manual review / Anonymize] | **Approved maximum** = the point at which data must be deleted absent a legal hold. Typically regulatory minimum + 1–2 years buffer for litigation. ## Step 4: Legal Hold Procedures When litigation, regulatory investigation, or government inquiry begins, standard retention schedules are suspended for affected data. **Legal hold process:** 1. **Trigger identification** — Litigation hold triggers: receipt of subpoena, preservation letter, or when litigation is reasonably anticipated 2. **Hold notice** — Legal counsel issues written hold notice to all custodians of potentially relevant data 3. **System hold flags** — IT sets a legal hold flag on affected records in all systems; automated deletion is blocked for flagged records 4. **Custodian acknowledgment** — All recipients of hold notice confirm in writing 5. **Scope documentation** — Hold notice specifies: data categories in scope, date range, relevant systems, custodians 6. **Hold log** — Maintain a log of all active legal holds: matter name, date issued, data scope, custodians, systems 7. **Hold release** — Legal counsel issues release notice when matter is resolved; IT removes hold flags; standard retention schedule resumes 8. **Periodic review** — Active holds reviewed quarterly to confirm continued necessity ## Step 5: Deletion Runbook For each data category at end of retention period: **Automated deletion (preferred for structured data):** ``` 1. Automated job runs [daily / weekly / monthly] 2. Query: SELECT records WHERE retention_expiry_date <= TODAY() AND legal_hold_flag = FALSE 3. For PII: overwrite with zeros or cryptographically erase encryption key (key deletion) 4. For non-PII: standard delete + transaction log purge 5. Generate deletion certificate: timestamp, record count, data category, deletion method, operator 6. Log deletion certificate to immutable audit log 7. Alert to compliance officer if deletion count exceeds threshold (potential pipeline issue) ``` **Manual review deletion (for complex or high-value records):** 1. System generates deletion candidate list 60 days before expiry 2. Compliance officer reviews list; approves or applies legal hold extension 3. Approved deletions executed by IT with certificate generated 4. Certificate filed in compliance records **Backup and archive purge:** - Backup media must be included in retention/deletion scope - Backups older than retention period must be purged on the same schedule - For tape backups: overwrite-3-pass standard (NIST SP 800-88) - Cloud backups: confirm provider's deletion API deletes all copies including geo-redundant replicas - Certificate of destruction issued by vendor for physical media destruction **Anonymization (alternative to deletion where operational data is needed):** - Replace PII fields with synthetic v
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.