Verification protects the requester
Some privacy requests involve access to, deletion of, or changes to personal data. The responder may need to confirm that the requester is allowed to receive or affect that data before taking action.
- Verification may depend on account details, contact channels, or other evidence.
- The responder should ask only for what is needed for the request.
- A person on the response team reviews verification status before fulfillment.
Responding to verification requests
Follow the responder's instructions and ask questions if the requested step is unclear. Avoid sending extra sensitive documents outside the approved channel.
- Check that the verification message came from the company handling your request.
- Use the requested upload or response channel when provided.
- Ask the company what alternative verification options are available if needed.
If you cannot complete a verification step
You may no longer have access to an old account, or the requested evidence may not be available. Tell the company what prevents you from completing the step and ask how it can review another way of confirming your connection to the data.
- An email link or code checks access to an inbox; the team may still need to review your relationship to the records.
- Never share your account password or a code intended to sign in to another service.
- If someone is acting for you, ask the company what evidence of authority it needs rather than sending unrelated identity documents.
Need more help?
Product support is available at support@privacyrequests.co. Requesters should contact the company handling the request first because that company controls the case record and response decisions.