AgenticFor DevelopersDatabases & Data Engineering

Data Retention & Archiving Strategy.

When storage costs are growing, compliance requires data retention policies, or users need a right-to-erasure implementation.

ChatGPT Β· Claude Β· GeminiΒ·AdvancedΒ·~1750 tokens
Curated by the AIPP team
Last updated 14 May 2026 Β· v3
data-retention-archiving-strategy-4.md Β· 1750 words
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task.

# Context
- Pack: Developers & Tech Professionals
- Category: Databases & Data Engineering
- Use case: Data Retention & Archiving Strategy
- Source task:
  - Design a data retention and archiving strategy for {{describe_application_and_data_types}}.
  - Step 1: data classification by retention requirement (operational, regulatory, archival, ephemeral).
  - Step 2: retention policy definition per data class (how long to keep in hot storage, cold storage, and when to delete).
  - Step 3: automated archiving implementation (which data moves where and when).
  - Step 4: compliance requirements (GDPR right to erasure, HIPAA retention minimums, financial record requirements).
  - Step 5: cost impact of the strategy.

# Goal
Data classification, retention policies per class, archiving automation design, compliance mapping, and cost impact analysis.

# Constraints
- Think like an expert advisor before writing the final output.
- Ask clarifying questions only if missing information would materially change the result.
- Avoid generic filler, vague advice, and unsupported claims.
- Make the output specific, practical, and ready to use.

# Output
Data classification, retention policies per class, archiving automation design, compliance mapping, and cost impact analysis.

The variables to fill in

PlaceholderWhat to put thereExample
{{role}}Roledata lifecycle expert
{{use_case}}Your specific valuedata retention & archiving strategy
{{describe_application_and_data_types}}Describe application and data typesExample describe application and data types

How to customize this prompt

  1. Replace each {{double-curly}} with your real context.
  2. Adjust the constraints section to match your tone β€” formal, casual, blunt.
  3. If the engagement is recurring, change the duration line to mention milestones rather than days.
  4. Run it in your tool of choice. The output should be ready to paste with at most one small edit.

When to use

When storage costs are growing, compliance requires data retention policies, or users need a right-to-erasure implementation.

PRO TIP

The right to erasure under GDPR applies to every system that holds the data β€” a thorough data map is the prerequisite to any erasure implementation.

Related prompts

Structured

Technical Problem Debugger

Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.

Structured

System Design Advisor

Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.

Structured

No-Code Tool Selector

Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.

Structured

Data Analysis Prompt

Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.

β˜… THIS PROMPT IS IN A PACK

The Developer Toolkit Pack

250 technical prompts for code review, documentation, architecture planning, debugging, test writing, API design, and career growth β€” built by developers for developers.

Browse more prompts β†’