Course contentsShow
← Data Science
Lesson 1908 of 2,14544. Data Ethics and PrivacyFree lesson

Data Subject Access Requests (DSARs)

Learning how to handle requests from individuals to access their personal data and what information must be provided.

Data Subject Access Requests (DSARs)

You'll learn how to respond when someone asks, "What data do you have about me?"

Under GDPR (and similar privacy laws), individuals have the right to access their personal data that your organization holds. When someone exercises this right, they're making a Data Subject Access Request (DSAR). As a data scientist working with personal data, you need to understand how to handle these requests properly.

What Must You Provide?

When someone submits a DSAR, you must provide:

  • What data you hold about them (copy of all personal data)
  • Why you're processing it (legal basis and purpose)
  • Who you've shared it with (recipients or categories)
  • How long you'll retain it
  • Where it came from (if not directly from them)
  • What automated decisions involve their data (if any)

The Data Science Challenge

DSARs can be tricky for data teams because personal data may be scattered across:

  • Multiple databases and data warehouses
  • Training datasets and model artifacts
  • Logs and monitoring systems
  • Archived or versioned data (remember DVC?)
  • Derived features and aggregations

You need robust data lineage tracking to trace an individual's data through your entire pipeline—from collection through transformation to final use.

Timeframe and Format

You typically have one month to respond (extendable to three months if complex). The information must be provided in a "concise, transparent, intelligible and easily accessible form, using clear and plain language."

Key Takeaway: DSARs require you to locate, compile, and explain all personal data about an individual across your entire data ecosystem—making data lineage, documentation, and metadata management essential privacy compliance tools.