> 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-access-or-export-request.md). # Fulfill a privacy access or export request Verify a privacy request, prepare the approved data package, and keep protected evidence safe. Podigee Audio Video Ad Server lets an authorized privacy operator fulfill a verified request for access to personal data or for a portable export. After the first mention, this article uses Podigee Ad Server for the product name. The workflow checks authority and scope before it prepares an evidence package. It does not include raw identities or credentials. Use this task when a verified person asks to see their data or receive a portable copy. Use the privacy policy workflow first when you need to change the rules for identity, consent, retention, or regional processing. ## Before you start * You have permission to operate privacy requests in the selected workspace. * A privacy case exists and is still open. * The request includes verified identity evidence and an approved legal basis. * You know whether the person asks for access or for portability. * You know the deadline that you must meet, if one applies. * You know the approved recipient and the safe channel for the package. Do not start a request when the identity evidence, case scope, or authority is unclear. Keep the case pending and resolve the missing evidence first. ## 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 only active privacy cases in the current workspace. Each option includes the case kind, severity, state, and a short reference. Check the reference against the request before you continue. ## Select the requested outcome 1. Set **Requested outcome** to **Provide access to personal data** when the requester needs to inspect the data. 2. Set it to **Provide portable personal data** when the requester needs a portable copy. 3. Select **Authority for this request**. 4. Add the fulfillment deadline when the case has a promised or statutory deadline. The selected outcome becomes part of the request record. Do not choose portability only because it looks more complete. Use it when the requester or the approved process requires a portable copy. ## Verify the person and the scope For an access or portability request, check these items before you submit: * The privacy case is for the current workspace. * The identity evidence matches the current case version. * The request type matches the approved request. * The legal basis is the reviewed basis for this case. * The approved subject is the person named in the case. * The recipient and delivery channel are approved for this data. The result can contain record digests and evidence references. It must not contain a raw name, email address, access token, credential, or unredacted event payload. If the person or case does not match, stop the job. Do not create a second case to bypass the scope check. ![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 data package 1. Select **Review** before you submit the job. 2. Check the request type, case, authority, subject scope, deadline, and expected record count. 3. Check that protected identity fields are excluded. 4. Check that aggregate, commercial, financial, security, and audit evidence keeps the retention required for the active obligation. 5. Confirm the approved recipient and download or delivery method. The package is based on the exact case version. If the case changes while you work, the job stops without a state change. Return to the current case and review it again. ## Submit and wait for 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, record count, and redaction result. 4. For access or portability, select **Download package** and use the approved secure channel. 5. Record the delivery or handoff in the privacy case according to your local process. The package is signed and bound to the request. Keep the completion receipt with the case. Do not copy the package into an unapproved ticket, email, chat, spreadsheet, or local folder. ## If the request cannot be completed * **Identity is uncertain:** keep the case pending. Ask for the missing verification through the approved channel. Do not disclose any data. * **The case changed:** return to the case, check the new version, and submit again only when the scope is still approved. * **The package contains invalid or incomplete evidence:** stop the operation and report the issue. Do not download or send the package. * **The recipient or delivery channel is not approved:** keep the case pending and update the approved recipient before you continue. * **The request is lawfully declined:** record the decision, reason, authority, and receipt. Do not mark the request as fulfilled. ## Expected result The verified request has one recorded outcome. An access or portability request has a signed, downloadable package with protected identity data excluded. The privacy case, operation, audit receipt, and relevant evidence use the same case version and request type. ## 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 the rules that govern future requests. Use [Create an evidence package](/documentation/grow-and-monetize/monetization/create-an-evidence-package.md) when a business, financial, or operational review needs a broader evidence set. --- # 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-access-or-export-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.