How to prepare a privacy request response
Prepare a privacy request response with verified scope, documented searches, proposed redactions, and a draft for a qualified privacy reviewer.
Free app. Runs on your Mac with the Claude or Codex plan you already have.
What it means to prepare a privacy request response
To prepare a privacy request response, tie a verified request to the systems and records covered by your approved procedure. Document where you searched, what each search returned, and which records belong to the person who made the request. Review those records for proposed disclosure or other handling, then assemble a draft and its supporting evidence. A qualified privacy reviewer uses that material to decide what may be released and what still needs work.
A DSAR response, meaning a response to a data subject access request, is one type of privacy response. If your team handles a GDPR access request, use the procedure your organization has approved for the case. A request for correction or deletion needs different item-level decisions. In each case, the privacy request evidence pack records how you reached those decisions. Keep verification references, search notes, and handling decisions in restricted working material. Put only the material intended for the requester into the draft and proposed attachments.
What it does for the business
- Give system owners precise requestsA coverage register shows the export, date range, or confirmation that each owner still owes. The privacy team can follow up on a specific dependency and give the owner the scope needed to resolve it.
- Focus qualified review on real decisionsAn item register shows which fields are proposed for disclosure and which need a ruling. The reviewer can go directly to the source passage and the proposed copy instead of reconstructing the record from email threads.
- Make a case handoff easier to pick upA dated request record and evidence index let a colleague continue the work using the same scope and identifiers. They can see which search results have been reconciled and who owns the rest.
- Find recurring problems with record retrievalAfter the case review, look at which authorized sources took extra work to check. Privacy operations can use that evidence to improve retrieval instructions or clarify who owns a system before another request arrives.
How to prepare a privacy request response, step by step
Confirm the request, authority, and approved scope
The search starts with a verified person and an approved description of the records to look for.
What to do
- Record the request ID and version, request type, and scope in the case record. If the person clarifies the request later, keep that clarification and its date so a reviewer can tell which scope guided the work.
- Confirm identity verification using the approved procedure. If an agent is acting for the person, check the scope and current validity of that authority. Use a case reference for the verification evidence and keep the evidence itself in restricted storage.
- Record receipt and approved due timestamps separately, with time zones when they affect interpretation. Link the due date to its approved source. Bring any unresolved deadline, jurisdiction, or procedural issue to the qualified reviewer for a decision.
- If verification or authority is missing or expired, limit work to intake and verification. Record the precise evidence needed and who can resolve it before a search for personal records begins.
Why
The same name can appear in records about more than one person. A verified identifier gives system owners a reliable starting point. An approved scope and due date also let the team coordinate work using the same case facts.
Reconcile the searches across the approved systems
A missing export and a documented search with no match tell the reviewer different things.
What to do
- Build a system coverage register with a row for each scoped system. Include the owner, verified search identifier reference, date range, search or export date, and evidence locator. Include processor and archive searches when the approved procedure calls for them.
- Ask owners to document the search they actually ran and the limits on what it reached. Mark whether it returned records, returned no match, or still needs a manual search. Mark any source outside confirmed scope with the reason.
- Match the exports to the verified subject using source identifiers. Set aside namesakes or conflicting identifiers for review. Reconcile unique records so an overlapping export does not inflate the number of records you have reviewed.
- Keep unmatched scope items visible. If a source is unavailable, identify the exact export or access dependency and the person who can resolve it. Keep a pending search distinct from a search that returned no records.
Why
Reviewers need to know which parts of the scope the evidence covers. A coverage row explains what a search could find and which result it produced. That detail is especially important when an empty export and a system that was never searched look similar in a summary.
Record proposed handling for each item
Each proposed inclusion, redaction, or action needs a record locator and a reason.
What to do
- For an access request, build a disclosure manifest that links each record and version to its source and verified subject. Record the proposed handling, the reason, any needed reviewer decision, and the path to the corresponding review copy.
- Identify third-party data by field or passage. Apply the organization's approved redaction rules to labeled review copies and retain the source originals. Where the procedure leaves the treatment open, hold the affected item and make the decision easy to find.
- Check the review copy as a recipient would see it. Confirm that text intended to be removed cannot still be read or extracted and that the remaining material matches the intended record and version.
- For a correction or deletion request, record the proposed action and its supporting authority. Flag conflicting identities, legal holds, and other dependencies for review. Treat the action as proposed until the authorized owner can furnish evidence of completion.
Why
An item decision can be reviewed only when the reviewer can locate the record, understand why it was included, and match it to the output copy. An explicit hold keeps an unresolved field or record from passing unnoticed into the release set.
Write the draft and verify the attachment set
The draft and attachments should say exactly what the reviewed evidence supports.
What to do
- Use approved organization wording and the supplementary information required by the supplied procedure. Write the response the reviewer would actually assess, with the available subject data and the attachments you have prepared.
- Keep the draft and proposed attachments apart from internal search and redaction logs. Check that the correct subject references, files, and versions appear in the response material. Keep verification evidence in its restricted location.
- Reconcile the attachment list with the item register and the files themselves. Open each attachment and confirm it contains the intended version. Compare factual statements in the draft with the evidence and the approved scope.
- Label incomplete or held drafts clearly for internal use. Give the reviewer the unresolved searches and item decisions alongside the draft so they can see what prevents release.
Why
A draft can be well written and still expose the wrong copy or describe a search that never finished. Reviewing the text and every proposed attachment against the working records catches mistakes that a prose edit would miss.
Hand off the open issues and release decision
The qualified reviewer needs a clear record of what is ready and what still blocks release.
What to do
- List every open system search, unresolved identity match, and disclosure question that affects the case. Give each an owner and a specific next action, with the relevant evidence or the exact missing source.
- Have a qualified reviewer check the case version, identity and authority, scope, due date source, item decisions, and actual draft files. Record the review outcome and the issues that still need resolution.
- Confirm which draft and attachments are under review and what approval remains before anyone uses them. If a secure channel has been proposed, identify it for the authorized owner to use after the release decision.
Why
A clear handoff helps the reviewer make a decision using the same case facts as the preparer. It also helps a system owner respond to an outstanding search without receiving requester-facing materials or records outside their assignment.
Common mistakes
- Starting a search before verificationKeep the work at intake until the procedure confirms the person's identity and any agent authority.
- Recording a missing export as zeroMark the system as pending and record the dependency that would let you complete the search.
- Merging records based on name aloneKeep ambiguous matches held until a verified identifier supports the link.
- Redacting fields without recording the basisUse approved rules and retain a reason and locator for the reviewer.
- Attaching the working logs to the draftCheck that each proposed attachment is intended for the requester and matches the reviewed item version.
What a good result looks like
- A request record with verified authority, approved scope, and an approved due-date source.
- One coverage row per scoped system, with dated search evidence or an explicit pending action.
- Unique subject records tied to source locators and proposed item decisions.
- A draft and actual attachments checked for subject, version, and third-party handling.
- A qualified privacy reviewer identified as the owner of the release decision.
And then what? Using the result
- Ask each system owner for the specific evidence needed to clear their outstanding search.
- Send the draft and review copies through your approved internal review process.
- Resolve held item decisions and record the reviewer's basis in the restricted case file.
- Record the release decision and preserve the evidence the reviewer used.
When to run it
- An access request reaches the privacy teamConfirm identity and scope first, then use the coverage and item registers to coordinate collection and prepare a reviewable response.
- Several teams hold relevant recordsGive each owner the verified search scope and use the coverage register to track what comes back from each system.
- A correction or deletion request touches multiple recordsUse the item register to show which actions are proposed and which depend on resolving identity, a legal hold, or a reviewer decision.
Questions people ask
How do you prepare a privacy request response?
Confirm identity and scope under the approved procedure, reconcile each system search, and attach evidence to each proposed item decision. Prepare the response and attachments as a draft for qualified privacy review.
What belongs in a DSAR response evidence pack?
Include the request and authority references, system coverage register, item decisions, source locators, draft, and proposed attachments. Keep restricted evidence and reviewer notes in the internal case file.
How do you handle third-party data in a GDPR access request?
Identify the affected fields or passages and apply the approved procedure for the case. Hold unresolved items for qualified privacy review and retain the original record and the proposed copy.
What do you record when a system search is incomplete?
Record the system as pending, the scope already covered, the missing evidence, and the owner who can supply it. Keep that gap visible in the handoff and mark any affected response draft as internal.
Who approves a privacy request response for release?
The qualified privacy owner or authorized reviewer makes the release decision under the organization's approved procedure. Provide that person with the exact draft, attachments, and unresolved decisions.
How do you record a proposed correction or deletion?
Create an item-level action or hold tied to the record, reason, and authority. Record completion only when the authorized owner has evidence the operation took place.
More jobs in Lawyers
Prepare a privacy request response, on your own Mac.Free app. Runs on your Mac with the Claude or Codex plan you already have. Your files stay on your computer.
Download for Mac