Skip to content
Rights & Requests calendar_today Updated: 6 April 2026 schedule 8 min read

GDPR Data Subject Rights: The Complete Guide for Business Owners

The GDPR gives individuals 8 rights over their personal data. As a business owner, you must handle these requests correctly, within one month, free of charge, and well documented. This guide explains each right and what you need to do.

summarize Key Takeaways
  • check_circle Data subjects have 8 rights under the GDPR; you must respond to each request within one month
  • check_circle You may not charge for the first request, unless it is manifestly unfounded or excessive
  • check_circle Always verify the identity of the requester before providing or deleting data
  • check_circle Keep a register of all received requests and how you handled them
  • check_circle GDPRWise automatically generates response templates for each type of request

The 8 rights at a glance

The GDPR (General Data Protection Regulation) gives every person whose data you process - customers, employees, website visitors - a set of rights. As a business owner, you are required to take every request seriously and handle it correctly.

These are the 8 rights:

  1. Right to information - know which data you process and why
  2. Right of access - receive a copy of their data
  3. Right to rectification - have incorrect data corrected
  4. Right to erasure - have data deleted (“right to be forgotten”)
  5. Right to restriction - temporarily stop processing
  6. Right to data portability - receive data in a readable format
  7. Right to object - object to certain types of processing
  8. Right regarding automated decision-making - not be subject to purely automated decisions

Before you start: the ground rules

Regardless of which right someone invokes, the same ground rules always apply:

Deadline: you have a maximum of one month to respond. For complex requests, you may extend this once by two months, but you must inform the requester within the first month about the delay and the reason.

Costs: the first request is always free. You may only charge a reasonable fee if the request is manifestly unfounded or excessive (think of someone submitting the same request every week).

Identity verification: always verify the requester’s identity before providing or modifying data. Ask for a copy of an ID document, but redact the national ID number and photo - you don’t need that information.

Registration: keep a register of all received requests, the date, the type of right, and how you handled them. The supervisory authority can request this register.

1. Right to information

What it means: people have the right to know which data you process, why, how long you retain it, who you share it with, and what rights they have. This right is “proactive” - you must actively provide this information, not just when someone asks.

How to arrange this:

  • Publish a clear privacy policy on your website
  • Inform customers when collecting data (signup forms, contracts)
  • Always mention: the purpose, the legal basis, the retention period, and the rights of the data subject

Common mistake: a privacy policy that nobody understands. Write in plain language, not legal jargon.

2. Right of access

What it means: someone can ask you for a copy of all personal data you process about them. This is the most common request, known as a “subject access request” or DSAR (Data Subject Access Request).

How to respond:

  1. Verify the requester’s identity
  2. Collect all data you have about this person, across all systems (CRM, email, accounting, HR)
  3. Send an overview with: which data, for what purpose, from whom received, with whom shared, how long retained
  4. Deliver this in an understandable format (e.g. PDF)

Deadline: within one month.

Note: you must not include data of other persons. If a file also contains data about third parties, redact it.

3. Right to rectification

What it means: if personal data is inaccurate or incomplete, the data subject can request correction or completion.

How to respond:

  1. Check whether the data is indeed inaccurate
  2. Correct it in all your systems
  3. Have you shared the data with third parties (e.g. a processor)? Inform them about the change as well
  4. Confirm the correction in writing to the requester

Practical tip: many systems allow customers to update their own data (think of an account page). That is the easiest route.

4. Right to erasure (“right to be forgotten”)

What it means: people can ask you to delete their personal data. This is not an absolute right - there are exceptions.

When you must delete:

  • The data is no longer needed for the original purpose
  • The data subject withdraws consent (and there is no other legal basis)
  • The data subject rightfully objects
  • The data was processed unlawfully

When you may refuse:

  • The data is needed for a legal obligation (e.g. fiscal retention requirement of 7 years)
  • For exercising the right to freedom of expression
  • For establishing or exercising legal claims

How to respond:

  1. Verify the identity
  2. Assess whether an exception applies
  3. Delete the data from all systems, including backups (where reasonable)
  4. Inform any recipients of the data
  5. Confirm the deletion or explain why you refuse

5. Right to restriction of processing

What it means: the data subject can ask you to temporarily stop processing. This is a kind of “pause button” - you keep the data but may no longer actively use it.

When this right applies:

  • The accuracy of the data is disputed (during verification)
  • The processing is unlawful, but the data subject does not want deletion
  • You no longer need the data, but the data subject does (for a lawsuit)
  • The data subject has objected and you are assessing whether your grounds outweigh theirs

In practice: mark the data as “restricted” in your system. You may only process it with the data subject’s consent, or for legal claims.

6. Right to data portability

What it means: the data subject can request the data they provided themselves in a structured, commonly used, and machine-readable format, and to transfer that data to another organisation.

When this right applies:

  • The processing is based on consent or a contract
  • The processing is automated (not on paper)

Format: use a common format such as CSV, JSON, or XML. Not PDF - that is not machine-readable.

Note: this right only applies to data that the data subject themselves provided. Derived data (analyses, scores, profiles) is not covered.

7. Right to object

What it means: the data subject can object to the processing of data, particularly when you process on the basis of legitimate interest or for direct marketing.

For direct marketing: the objection is always valid. You must immediately stop processing data for marketing purposes. No discussion possible.

For legitimate interest: you must assess whether your interests outweigh the rights of the data subject. If not, you must stop the processing.

How to respond:

  1. Is it about direct marketing? Stop immediately
  2. Is it about legitimate interest? Make an assessment and document it
  3. Inform the data subject about your decision

8. Right regarding automated decision-making and profiling

What it means: people have the right not to be subject to a decision based solely on automated processing (including profiling) if that decision significantly affects them.

When this is relevant:

  • You use an algorithm to automatically reject credit applications
  • You make automatic price discrimination based on profiles
  • You automatically select applicants without human assessment

For most SME business owners: this right is rarely relevant. If you don’t make fully automated decisions that significantly affect people, you don’t need to worry about this much.

If it is relevant: ensure there is always an option for human intervention, and inform data subjects that they have this right.

Response templates

We have created ready-to-use email templates for the most common requests. Copy them, adjust your company details, and send.

What should you do now?

A checklist to get your obligations in order:

  • Ensure your privacy policy is up to date and mentions all rights
  • Set up a procedure for receiving and handling requests
  • Appoint someone responsible for handling requests
  • Use our response templates as the basis for your own responses
  • Set up a register for received requests
  • Train your employees - they must know how to recognise a request and forward it
  • Test your procedure: how quickly can you retrieve all data about one person from all your systems?
auto_awesome Do you know what data you process?

GDPRWise scans your website and maps out which personal data you collect, who you share it with, and what rights your visitors have. So you know exactly what to answer when you receive a request.

GW
GDPRWise Editorial

This article was written by the GDPRWise team and reviewed by our privacy experts. We regularly review our content for accuracy and legal correctness.