Dhamaka Dhamaka Logo

Data Retention Policies

Dhamaka provides configurable retention periods for architecture discussions, audit logs, and technical documents. Policies can be set at the organization level with project-specific overrides, allowing you to align data lifecycle management with your enterprise data governance requirements.

Why Retention Policies Matter for Architecture Teams

Engineering organizations must balance competing requirements:

  • Retain records long enough to support knowledge continuity, compliance requirements, and potential IP disputes
  • Minimize data exposure by not retaining sensitive technical information longer than necessary, reducing breach risk

What Can Be Configured

Dhamaka allows independent retention periods for different data types:

  • Architecture discussions — AI-assisted conversations about system design, technical decisions, and implementation approaches
  • Audit logs — Records of who accessed what technical documentation and when
  • Technical documents — Uploaded design documents, specifications, and architectural diagrams

Each data type can have its own retention period, and projects can override organization defaults when specific requirements differ.

Typical Retention Periods

Data Type Typical Requirement
Architecture discussions 3-7 years (varies by industry and compliance requirements)
Audit logs 3-7 years (enterprise compliance)
Technical documents Life of system + retention period

Note: Always consult your compliance and legal teams to determine appropriate retention periods for your organization's specific requirements.

How Retention Works

  • Retention cleanup runs automatically on a scheduled basis
  • Data older than the configured retention period is eligible for deletion
  • Audit logs are archived before deletion to preserve integrity verification
  • All deletions are permanently documented for compliance reporting

Legal Hold Override

Data subject to a legal hold is never deleted by retention policies, regardless of age. This ensures compliance with preservation requirements during IP disputes, patent litigation, or regulatory investigations.

Related