Data Privacy: A runbook for engineer cover
welcome to this free extract from
an online version of the Manning book.
to read more
or

8 Exporting user data: Data Subject Access Requests

 

This chapter covers

  • What Data Subject Access Requests (DSARs) are
  • How DSARs fit into a company’s overall privacy commitments
  • Shaping the DSAR fulfillment process
  • Automating DSARs
  • Customizing the data in DSARs
  • How administrators can create DSARs

In this chapter, we will discuss Data Subject Access Requests (DSARs). As privacy laws like GDPR and CCPA become more entrenched in the public consciousness, leaders at all kinds of companies are seeing DSARs land on their desk, and they need to respond to them. Unless they are able to do so accurately and expediently, they risk reputational harm and possible fines. This chapter will help such leaders in three ways.

First, we will look at the DSAR workload and assess how companies are faring in the face of customer requests. This will help leaders and their executive supervisors make informed decisions around data governance, resourcing, training, and outreach. This part of the chapter is geared to a wide range of stakeholders.

Second, we will look at backend data and how those responsible for storing and extracting data to support DSARs can make decisions about architecture. These decisions are critical in both manual and automated fulfillment of DSARs. This section is geared more toward engineers but it could also be instructive for attorneys, since they need to understand the tradeoffs involved in various approaches to fulfilling DSARs.

8.1 What are DSARs?

8.1.1 What rights do DSAR regulations give to users?

8.1.2 An overview of the DSAR request fulfillment process

8.2 Setting up the DSAR process

8.2.1 The key steps in creating a DSAR system

8.2.2 Building a DSAR status dashboard

8.3 DSAR automation, data structures, and data flows

8.3.1 DSAR components

8.3.2 Cuboids: A subset of DSAR data

8.3.3 DSAR templates

sitemap