A useful request makes it easy to identify the information, understand your concern and reply to you. More personal information is not always better: start with the minimum evidence needed for the issue you want reviewed.
Identify the controller and the information
Find the website’s privacy notice or rights contact. Include the exact page URL and identify the facts you are asking it to review. Avoid vague requests to remove everything about you from the internet.
Explain the request and its grounds
Say whether you want correction, erasure, restriction or consideration of an objection. Describe the circumstances in plain language. Erasure has exceptions, including legal obligations and freedom of expression; a controller may have reasons to retain information.
Keep verification proportionate
A controller may ask for information needed to verify identity. Use its verified, secure channel and consider whether the information requested is necessary. Never send identity documents to an unverified address or attach them to a public post.
Track the response
Keep the date, recipient and a copy of your request. Controllers generally must respond within one month, with possible extensions in qualifying cases. A response is not the same as approval. If you disagree with the answer, your national data protection authority can explain complaint options.
Read the source guidance
Explore directory requests or read about Google delisting.
Continue with your situation
For a publisher that has replied, see how to read a directory refusal. If you have not received a reply, use our directory follow-up guide. To review what assistance should deliver, see the final-report checklist.
