capabilities.work

Data Subject Erasure Request

A 2-step recipe with Didomi. We can help you get access.

Recipe · 2 steps

Data Subject Erasure Request

with Didomi

Find an end user by internal ID and delete their consent record to fulfil an erasure request.

  1. Retrieve the end user matching the supplied organization user ID. Branch on whether a user was returned: delete it when present, otherwise end.
  2. Delete the matched user's consent record, fulfilling the right-to-erasure request. The deleted ConsentUser object is returned on success.
What you'll need to have ready
  • token: A valid Didomi JWT used as the bearer token for the Authorization header.
  • organizationId: The ID of the organization the user belongs to.
  • organizationUserId: Your organization's internal user ID identifying the data subject (email, phone or client ID).
For your developer

Arazzo workflow didomi:data-subject-erasure, 2 operations: {$sourceDescriptions.consentsUsersApi.url}#/paths/~1consents~1users/get → {$sourceDescriptions.consentsUsersApi.url}#/paths/~1consents~1users~1{id}/delete. Specs on APIs.io.

More recipes with Didomi

Classify a Vendor and Register a CookieCreate a Consent User and Assign an Internal IDCreate and Verify a Privacy CenterDeploy a Consent NoticeGroup Notices Under a TemplateIssue a Consent Token for an End UserProvision an Organization and Invite a MemberRecord a Consent Event and Confirm StatusRegister and Verify a CookieSubmit Notice Text Content for Approval