Privacy owner
The action waits until this owner approves or denies it.
Workflows · Customer-account deletion
Customer deletion waits for retention review and the Privacy owner.
Record the account, deletion scope, retention evidence, policy decision, and deletion result before removal.
Example workflow. Execution requires a configured tool with provider permissions for this action; see the connection’s operation reference or bring your company tool to the demo.
Agent request
Delete account cust_4821 and its retained application data
Deletion is irreversible and can remove records that remain subject to retention requirements.
- Identity
- privacy-agent · Privacy operations
- Target
- customer/cust_4821
- Cost
- Recorded agent cost
- Evidence
- Verified request, data inventory, and retention review
Policy decision
Customer-account deletion requires the Privacy owner.
Tool call resumes
The connected data tool runs the approved deletion and returns its result.
Tool call stays blocked
The account data remains in place and the deletion does not run.
Execution order
The agent request stops before the connected tool runs.
- 01Privacy agent requests account deletion
- 02Deixic checks the account, scope, retention evidence, and policy
- 03Privacy owner decides
- 04Connected data tool returns the deletion result
Activity history keeps the request, decision, cost, and result.
Keep the procedure for the next request.
Keep the policy and decision history, save the steps and evidence as a skill, and test changes on real sessions; an approval stays specific to its request.