Databases
AuraScore 81/100

HR Database Retention and Anonymization Verification Checklist

Technical audit checklist for automated PII retention schedules, anonymization routines, and schema masking in HR databases.

Use this template when implementing or auditing automated data purging and anonymization rules within HR database systems to ensure compliance with data protection laws.

Template

Role: Lead Data Governance Architect and Database Security Specialist.

Context

  • Enterprise organisation: {{company_name}}
  • Database technology: {{hr_database_type}}
  • Mandatory retention window: {{retention_schedule_period}}
  • Privacy legal framework: {{jurisdiction_framework}}
  • Transformation strategy: {{anonymization_method}}
  • Target schema tables: {{audit_target_tables}}

Task

Generate a rigorous database audit checklist to evaluate automated purging, pseudonymous transformation, and PII masking routines in {{hr_database_type}} to satisfy {{jurisdiction_framework}} compliance across {{company_name}}.

Method

  1. Review targeted tables in {{audit_target_tables}} for direct identifiers, indirect identifiers, and relationship linkages.
  2. Assess timestamp columns tracking candidate rejection, employment termination, and offboarding events against {{retention_schedule_period}}.
  3. Evaluate automated batch jobs, triggers, and stored procedures applying {{anonymization_method}}.
  4. Verify that irreversible masking cannot be reversed through re-identification attacks or cross-table join analysis.
  5. Inspect foreign key cascade behaviors to ensure orphaned records do not retain residual PII.
  6. Audit database transaction logs, replica nodes, and backup lifecycle policies to ensure purged data is aged out.
  7. Validate immutable audit logging for every purge execution to confirm defensibility under {{jurisdiction_framework}}.

Constraints

  • MUST include explicit SQL validation checks or query strategies for each verification item.
  • MUST NOT recommend manual data editing or ad-hoc table alterations without audit tracking.
  • All items must differentiate between active employment records and records eligible for {{anonymization_method}}.
  • Keep checklist items concise, actionable, and focused on database-level implementations.

Output format

1. Audit Scope & Privacy Parameters

  • Summary of target tables, retention thresholds, and legal context.

2. Schema & Identifier Discovery Checklist

  • 3-4 markdown items auditing column sensitivity and candidate identifiers.

3. Automated Anonymization & Purge Engine Checklist

  • 4-5 markdown items auditing stored procedures, triggers, and rollback protection.

4. Backups, Replicas & Log Expiry Checklist

  • 3-4 markdown items verifying backup pruning and compliance audit logs.

Self-review

  • Ensure every section uses markdown task checkboxes [ ] with verification queries noted.
  • Confirm the anonymization method specified in {{anonymization_method}} is directly evaluated.
  • Check that backup and replica sanitization is explicitly addressed alongside live tables.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

developers
developers-databases
research-productivity-operations
databases
data-governance
privacy