> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/grow-and-monetize/monetization/fulfill-a-privacy-deletion-or-restriction-request.md). # Fulfill a privacy deletion or restriction request Apply an approved deletion or restriction request without removing required business evidence. Podigee Audio Video Ad Server lets an authorized privacy operator apply a verified deletion, restriction, or objection request to one exact subject. After the first mention, this article uses Podigee Ad Server for the product name. The workflow pseudonymizes or restricts the approved subject and keeps the evidence that another legal, commercial, financial, security, or audit duty still requires. Use this task when the approved request changes how personal data may be kept or used. Use [Fulfill a privacy access or export request](/documentation/grow-and-monetize/monetization/fulfill-a-privacy-access-or-export-request.md) when the requester only needs to inspect or receive a copy of the data. ## Before you start * You have permission to operate privacy requests in the selected workspace. * A privacy case exists and is still open. * The case has verified identity evidence and an approved legal basis. * The approved request is deletion, restriction, or objection. * You know the exact person and the approved scope of the change. * You know which connected partners or delivery surfaces need follow-up. Do not start the job when the identity, case scope, or authority is uncertain. Keep the case pending and obtain the missing proof first. A deletion or restriction must never be used to bypass a commercial, financial, security, or audit retention duty. ## Open the privacy request job 1. Open **Monetization > Revenue jobs**. 2. Select **Security, privacy, and audit**. 3. Select **Fulfill a privacy request**. 4. Choose the open privacy case from **Privacy request**. The list shows active privacy cases in the current workspace. Check the case reference, scope, and state against the approved request before you continue. ## Select the request and legal basis 1. Set **Requested outcome** to **Erase personal data**, **Restrict processing**, or **Record and apply an objection**. 2. Select **Authority for this request**. 3. Add the fulfillment deadline when the case has a promised or statutory deadline. The selected outcome becomes part of the request record. Select only the outcome that the approved request requires. Do not select erasure when the approved result is a temporary restriction. ## Select the exact person When you select a mutating outcome, Podigee Ad Server shows **Person affected**. Select the person named in the verified case. Check these items before you submit: * The person is inside the case scope. * The identity evidence digest still matches the current case version. * The person is not a different person with a similar name. * The request type, legal basis, and deadline match the approved case. * The connected systems and delivery surfaces that use this identity are known. The subject selection is required for deletion, restriction, and objection. It prevents a broad workspace action when the case covers one person. If the case covers a workspace, the operation still resolves the exact subject recorded in the approved directives. ![The current One Podigee Operations page shows the delivery assurance area where operators review active work and delayed evidence.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-6db53133b0902c0ebe2d348da5710f6f8cfe7c7b%2Fdoc-monetization-067-operations.png?alt=media) *Check related work before you complete a sensitive request.* ## Review the effect before you submit 1. Select **Review**. 2. Check the case, request type, legal basis, person, scope, deadline, and expected effect. 3. Check the partner and delivery follow-up list. 4. Check which aggregate, commercial, financial, security, and audit evidence remains retained. 5. Confirm that no raw identity, credential, or unredacted event payload will be included in the completion evidence. The operation checks the exact case revision and identity evidence again when it runs. If the case changes after this review, the operation stops without applying the request. Review the current case before you submit again. ## Submit and verify the result 1. Select **Fulfill request**. 2. Wait for the operation to reach **Completed**. 3. Open the result and check the request type, case state, subject scope, and action. 4. Check the partner and delivery follow-up items. Complete each item in its owning system or record why it is not required. 5. Keep the completion receipt with the privacy case. For an erasure request, the person is pseudonymized and disabled. For a restriction or objection, processing for the person is restricted and verification is expired. The privacy case moves to resolved only after the operation completes. The history remains available for the permitted retention period. ## If the operation stops * **Identity or authority is uncertain:** keep the case pending. Do not apply a partial change or disclose the result. * **The case changed:** review the new case version and submit only when the current scope is approved. * **The subject is outside the case scope:** stop and correct the case. Do not broaden the request from the workflow form. * **A required record must be retained:** record the retention reason and keep the protected evidence. Do not delete it to make the request look complete. * **A partner still has an approved copy:** follow the partner's verified removal or restriction process and attach its receipt to the case. * **The result is incomplete or invalid:** do not tell the requester that the request is complete. Keep the case pending and contact the privacy owner. ## Expected result The approved deletion, restriction, or objection applies to the exact verified person and scope. Required business evidence remains available with its protection and retention class. The case, operation, audit receipt, and follow-up records agree on the request type, case version, subject, and final state. ## Next useful tasks Use [Configure privacy, identity, retention, and regional use](/documentation/grow-and-monetize/monetization/configure-privacy-identity-retention-and-regional-use.md) to change future data-use rules. Use \[Fulfill a privacy access or export request] (fulfill-a-privacy-access-or-export-request.md) when the requester needs to inspect or receive a copy of the data. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.podigee.com/documentation/grow-and-monetize/monetization/fulfill-a-privacy-deletion-or-restriction-request.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.