Right-to-be-forgotten / data subject erasure request internal queue trigger

Outcome. An erasure request gets logged into one queue the moment it comes in, with a task and a deadline reminder, so compliance never misses one even though HubSpot cannot perform the actual deletion as a workflow action.

Workflow map Enrollment, branches and actions at a glance marketing-ops-019

flowchart TD
    A[Erasure request status = Requested] --> B[Set erasure_requested_date]
    B --> C[Add to GDPR erasure queue]
    C --> D[Notify compliance owner]
    D --> E[Create review task, due 5 biz days]
    E --> F[Delay 5 business days]
    F --> G{Status still Requested?}
    G -->|Yes| H[Escalate to compliance owner + manager]
    G -->|No| I[No action, being handled]

When to use it, when not to

• UseUse once you have a way for a contact or an internal team member to flag "this person asked to be forgotten," whether through a form, a support ticket, or a manually set property.
• UseUse to make sure a request is never handled only by memory or a Slack message that scrolls away.
• SkipDo not use this fiche as the deletion mechanism itself. HubSpot has no workflow action that deletes a contact record or its associated data. Deletion happens through the GDPR delete tool in Settings or the API, run manually by a person after legal review, never automatically. [VERIFY]
• SkipDo not use if your process already runs the request through a dedicated case management or legal tool with its own SLA tracking; duplicating the queue there adds confusion.