Skip to main content
This is an example implementation of a GDPR-compliant data deletion workflow using Humancheck. This demonstrates how to integrate human review for compliance-sensitive operations, but Humancheck can be used for any data operation that requires human oversight.

Overview

The data deletion workflow:
  1. User requests data deletion (GDPR right to be forgotten)
  2. System identifies all data associated with the user
  3. Request human review for verification
  4. Reviewer verifies and approves deletion
  5. System deletes all user data

Implementation

Basic Data Deletion Workflow

Advanced Features

Partial Data Deletion

Data Export Before Deletion

Scheduled Deletion

Compliance Features

GDPR Compliance Tracking

Verification Requirements

Routing Rules

Route data deletion requests to compliance team:

Dashboard Integration

The data deletion request appears in the dashboard with:
  • User identification (ID, email)
  • Data summary (what will be deleted)
  • Request type (GDPR, user request, etc.)
  • Data categories and counts
  • Export availability (if applicable)
Reviewers can:
  • ✅ Approve deletion after verification
  • ❌ Reject if verification fails or user identity is unclear
  • ✏️ Modify to schedule deletion or change scope

Best Practices

  1. Always require review: Data deletion should never be automatic
  2. Provide comprehensive summaries: Show what data will be deleted
  3. Maintain audit trails: Log all deletion requests and decisions
  4. Verify user identity: Ensure the request is legitimate
  5. Consider data export: Offer to export data before deletion
  6. Use appropriate urgency: GDPR requests may have legal deadlines
  • GDPR Article 17: Right to erasure
  • CCPA: California Consumer Privacy Act
  • Data retention policies: Some data may need to be retained for legal reasons
  • Backup considerations: Ensure backups are also handled

Next Steps