This GDPR rights request guide gives you a reusable checklist for asking an organisation to show, correct, restrict, transfer, or delete personal data. It also includes copy-and-paste templates, an identity-verification checklist, and practical steps to take if the response is late, incomplete, or refused.
Overview
The General Data Protection Regulation (GDPR) gives individuals rights over personal data processed by organisations that fall within its scope. Your request is usually sent to the organisation that decides why and how your data is used, often called the controller. A privacy notice, account settings page, customer-support channel, or data protection contact may identify the correct route.
You do not generally need to use legal wording. State which right you are exercising, provide enough information to help the organisation find your records, and keep a copy of everything you send. The organisation may ask for information to confirm your identity, but verification should ordinarily be relevant and proportionate to the risk of disclosing personal data.
Responses are generally due without undue delay and normally within one month of receiving the request. A complex request may take longer, but an extension should be explained within the initial period. Because rules can depend on the organisation, the data involved, and applicable national procedures, check the organisation's current privacy information and your data-protection authority's guidance if the situation is disputed.
| Right | What it can help you do | Useful wording |
|---|---|---|
| Access | Ask whether your data is being processed and request a copy, plus relevant information about its use. | “Please provide a copy of my personal data and the associated processing information.” |
| Rectification | Correct inaccurate data or complete information that is incomplete. | “Please correct the following inaccurate information and confirm when it has been updated.” |
| Erasure | Ask for personal data to be deleted where the legal conditions apply. | “I request erasure of the personal data listed below.” |
| Restriction | Ask an organisation to limit how it uses data while a dispute or other issue is considered. | “Please restrict processing of this data while its accuracy is being checked.” |
| Portability | Request certain data in a structured, commonly used, machine-readable format, where the right applies. | “Please provide the portable data in a commonly used machine-readable format.” |
| Objection | Object to processing in circumstances where GDPR provides an objection right, including some direct-marketing situations. | “I object to the processing described below. Please stop the relevant processing unless a lawful exception applies.” |
These rights are not automatic deletion or disclosure commands in every circumstance. Legal obligations, freedom of expression, public-interest duties, legal claims, other people's rights, and other exemptions may affect the outcome. A refusal should identify the reason in understandable terms where required.
Checklist by scenario
Before sending any request
- Identify the organisation and, if possible, its privacy or data-protection contact.
- Choose the specific right or rights you want to exercise.
- List relevant identifiers, such as an account email, customer number, order reference, or former address.
- Set a narrow date range or data category when that will make the request clearer.
- Remove unnecessary sensitive information from attachments.
- Save the final request, attachments, delivery confirmation, and the date it was received.
Access request template
Subject: GDPR access request
Hello,
I am requesting access to my personal data under the GDPR. Please confirm whether you process personal data about me and provide a copy of the relevant data, together with the information required about its use.
To help locate my records: [name], [account email or customer reference], and [other relevant identifier]. Please include data held between [date] and [date], if applicable.
Please let me know if you need proportionate information to verify my identity. I would prefer the response by [secure channel or email].
Regards,
[name]
[contact details]
Correction, deletion, restriction, or objection template
Subject: GDPR request concerning my personal data
Hello,
I am exercising my right under the GDPR regarding the following personal data: [describe the data and where it appears].
My request is to: [correct the data / erase the data / restrict processing / record my objection]. The reason is: [brief explanation, if useful]. Supporting information is attached: [list attachments].
Please confirm receipt and explain the action taken. If you refuse all or part of this request, please explain the reason and tell me how to complain to the relevant data-protection authority.
Regards,
[name]
[contact details]
After sending
- Record the date the organisation received the request; this is more useful than the date you drafted it.
- Note any identity-verification request and respond through a verified channel.
- Calculate a one-month review date, while allowing for any properly explained extension.
- Compare the response with each part of your request rather than treating a partial answer as complete.
- Send one concise follow-up listing missing items, dates, and the remedy you want.
What to double-check
- Scope: Confirm that GDPR is likely to apply. The organisation's location, services, processing activities, and your circumstances can matter.
- Correct recipient: A processor may not be able to decide your request. Ask it to forward the request or identify the controller where appropriate.
- Identity checks: Do not send a full identity document automatically. Ask what is needed, why it is needed, how it will be protected, and whether sensitive fields can be obscured.
- Data format: For portability, specify the data source and a practical machine-readable format, while recognising that portability applies only in defined circumstances.
- Third-party information: An access response may need to protect another person's rights, so some content may be removed or withheld.
- Marketing objections: Identify the channels and addresses involved, unsubscribe separately if convenient, and retain evidence if messages continue.
- Security: Verify the recipient's web address and contact details before uploading identification or downloading files. The Government Website Verification Guide offers broader checks for official-looking portals.
Keep a simple evidence log with the request date, delivery method, replies, identity checks, missing information, and follow-up dates. If the issue involves suspected account compromise, use the Identity Theft Recovery Checklist alongside the privacy request.
Common mistakes
- Sending a vague message such as “delete everything” without identifying the account or data involved.
- Submitting several conflicting requests without explaining which outcome is preferred.
- Assuming a request overrides a retention duty, a legal claim, or another applicable exemption.
- Providing more personal information than needed for identity verification.
- Counting from the wrong date or ignoring a documented extension notice.
- Accepting an automated privacy-centre result without checking whether it answers every part of the request.
- Deleting emails, screenshots, or account records before the dispute is resolved.
If the organisation misses the deadline, send a dated follow-up. If it refuses or provides an incomplete response, ask for the specific legal basis, the data or processing covered, and the available complaint route. You can then contact the data-protection authority responsible for the matter. Keep expectations realistic: a regulator may investigate or give guidance, but it may not resolve every private dispute immediately.
When to revisit
Revisit this checklist before submitting a request to a new organisation, after an account or address change, and whenever the organisation changes its privacy notice, portal, or verification process. It is also worth reviewing before seasonal account clean-ups or other planning cycles when you may be contacting several services at once.
Rules, regulator complaint links, contact routes, and online workflows can change. Before acting, verify the current privacy contact, the applicable data-protection authority, and any instructions about secure identity checks. Recalculate the response date for each request rather than reusing an old deadline.
Final action checklist: choose the right, verify the recipient, limit the data you disclose, send the relevant template, save proof of delivery, record the response date, and follow up in writing if the answer is late or incomplete. This creates a clear record you can use if escalation becomes necessary.