Are you having trouble handling data subject access requests (DSARs)? Don't fret—you're definitely not alone. DSARs can be complex and time-consuming to deal with. Fortunately, this short 'n' simple primer is here to help!

In this guide, we'll cover everything from what a DSAR is and who submits them to how you should respond and the common challenges you'll encounter. We'll also answer one of the most elusive questions surrounding DSARs: Can they be automated? Let's dive right in.

What are Data Subject Access Requests?

The global digital landscape is rapidly evolving. In an effort to bolster data transparency and privacy, the General Data Protection Regulation (GDPR) granted EU residents and anyone doing business with EU organizations new rights regarding how organizations collect and process consumer personal data. The California Consumer Privacy Act (CCPA) and the more recent Virginia Consumer Data Protection Act (VCDPA) established similar obligations.

One of these rights is called the right of access. his right empowers individuals (“data subjects” under GDPR) to submit a request known as a data subject access request to learn what information your organization has about them and how you use it. Besides discovering or accessing their personal data, subjects can also use DSARs to request correction or deletion of their personal data.

Recent data privacy regulations like the GDPR and CCPA have increased the power of  consumers to make these requests, and the risk to companies of fumbling them. While this development certainly improves transparency for consumers, it also creates challenges for companies around the world.

Who can submit DSARs?

Anyone can submit a DSAR at any time. This includes but is not limited to customers, users, sales prospects, employees, contractors, job candidates, and donors. Individuals do not need to supply a reason for submitting a DSAR, and organizations can only ask questions that help verify the subject's identity or locate the requested data.

Individuals can also submit DSARs on behalf of others. Here are some examples of when this can occur:

  • A parent or guardian requests information on a child.
  • A court-appointed individual is in charge of handling someone else's affairs.
  • A contractor or employee requests data on behalf of their client or employer.

In these cases, it's imperative to verify that the person submitting the DSAR is genuinely doing so on behalf of the data subject. Organizations can do this by requesting supporting evidence of their relationship (e.g., birth certificates, power of attorney documentation, etc.).

What's required in a DSAR response?

DSARs usually request a copy of all personal data you have on a data subject. Sometimes, the subject may only request specific details. Either way, you're obligated to provide any data that is relevant to the request.

Here are some examples of the information that data subjects can request:

  • Confirmation that your organization processes their personal data.
  • Access to a subject's personal data.
  • Your lawful basis for processing the subject's data.
  • How long you'll store their data.
  • How the data was obtained and how it's used in automated decision-making and profiling.
  • Third parties with whom you share the subject's data.

How do you respond to Data Subject Access Requests?

Generally speaking, you must take four steps to process and fulfill DSARs.

1. Register, record, and authenticate the DSAR

Before your organization starts fulfilling a new DSAR, it should register the request, log it in a record system, and authenticate the user making the request.

2. Gather personal data

Next, you must discover and categorize the subject's personal data that you process and store.

3. Review the personal data

After collecting the subject's personal data, review or redact it to ensure that it meets DSAR requirements without disclosing any proprietary information or data of other subjects.

4. Deliver the data securely

Once you've completed the previous three steps, you can now deliver the information to the data subject. Make sure you do this as safely as possible—data breaches or leaks can be extremely expensive, both in money and reputational damage.

How long do you have to respond to DSARs?

Under the CCPA, you must respond to a DSAR within 45 days. The GDPR only gives you 30 days to do so. Although both laws offer extensions in certain cases, failure to respond to a DSAR within the proscribed timeframes can result in substantial fines and regulatory penalties. It can also damage your organization's reputation by suggesting that you don’t value transparency.

Why are DSARs so challenging to fulfill?

DSAR orchestration involves a complex workflow of verifying the request, finding the data, reviewing it, and delivering it to the subject. Bringing automation to the process would be a boon for organizations, but it’s easier said than done due to the following complexities:

Personal data can exist across multiple systems

Depending on the size of your organization, DSAR orchestration can encompass dozens, or even hundreds, of systems that collect and store information. This means you have to go through all of the steps mentioned above for each system your organization relies on—in-house legacy, cloud-based, data warehouse, and third-party—to fulfill the request.

This factor alone can exponentially increase the complexity of completing a single DSAR. Consequently, fulfilling DSARs can quickly become both time- and labor-intensive, costing you much more money and resources than you had originally envisioned.

The bottom line? If you don't keep all of a subject's personal data in one convenient place, you'll probably have to implement a data mapping process to keep track of everything and rely on a reporting tool to pull this information from several resources to generate a DSAR response efficiently.

No matter what business you’re in, this is a common conundrum you're likely to encounter. Personal data about your customers resides in more places than just your CRM—it's also in your financial and customer service systems, data logs, backups, websites, and many more locations across the cloud.

Personal data can exist in multiple formats

Besides existing in multiple systems, personal data also comes in multiple identifier formats, such as names, email addresses, accounts, and cookies, just to name a few. To make matters worse, your customer may be John Smith in one system, cookie AU9AtlDpEbAqfakUE in another, and reward member #59420392 in yet another. Before you can even think about fulfilling or automating DSARs, you need to be able to find and align all of this data—a heavy lift.

For example, let's pretend you've received a DSAR based on an email address. If this isn't the system identifier, you'll need to request more information from the data subject or try to figure out the correct data format by delving into your system. The latter option isn't always available since some systems only hold obscure identifiers. Without this information, not only is automation impossible, but your compliance is now at risk.

Current tools are inadequate

Even if you can locate all of a data subject's information, fulfilling the DSAR requires you to know and implement all of the steps of your workflow for each system. Tools like ticketing systems have proven to be valuable in helping customer service and IT help desks organize their workflows. And many have even added support for managing GDPR and CCPA DSARs. But they can only automate part of the process.

Ticketing systems can take care of tasks like ticket creation, receipt acknowledgment, and due date alerts. But they can't find, delete, or change all of the formats of a subject's personal data across all of your systems—that task falls to you. In other words, your ticketing system can tell you what to do, but you're still on the hook to actually orchestrae the DSAR and ensure that every step you take satisfies GDPR and CCPA. This actually comprises the bulk of complexity, time, and effort within your DSAR response workflow.

Regardless of the ticketing solutions, spreadsheets, and documented procedures you employ to streamline your DSAR response workflow, the actual process required to account for, modify, or remove personal data from each of your systems will still be manual to a significant degree.

So can DSAR orchestration ever be truly automated? Luckily, that's exactly what Ketch is for.

True automation for your Data Subject Access Requests

GDPR and CCPA compliance doesn't only let you avoid penalties; it's also a prime opportunity to establish and build trust with your customers. Quick, efficient responses to DSARs can elevate your brand by showing your clients that you take their data privacy seriously. But as you now know, accomplishing this isn't an easy feat.

If you're wondering if there's a better way to automate your DSAR response workflow, Ketch has got you covered. We built our platform from the ground up to automate the fulfillment of data subject access requests. And when we say "fulfillment," we really mean your entire workflow—not just ticket creation.

Want to remove compliance headaches and avoid hiring a costly data compliance analyst? Robust, automated DSAR orchestration is just a few steps away. Click here to schedule your Ketch demo and learn how our platform can simplify your DSAR response workflow.

To learn more about Ketch's innovative approach to Privacy Orchestration, download our white-paper here.

What are Data Deletion Rights?

Data transparency and privacy have become top of mind for both consumers and businesses. This is in large part due to the General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA) establishing rules regarding how organizations collect and process personal data. One of these rules focuses on consumer data deletion rights.

The GDPR's Right to Be Forgotten

The GDPR grants EU residents and anyone doing business with EU organizations the right to be forgotten. Also known as the right to erasure, it allows individuals to ask organizations to delete their personal data. An individual has the right to request this if:

  • The organization no longer needs the data for the original reason it collected it for.
  • A user withdraws their consent which acts as the lawful basis that the organization relies on to process the data.
  • An individual objects to the processing of their personal data and there is no legitimate interest to override this.
  • A person objects to their data being used for direct marketing purposes.
  • The organization is unlawfully processing a person's data.
  • An organization must delete personal data to comply with a legal obligation or ruling.
  • The organization has processed a child's personal data in order to offer information society services.
The CCPA's Right to Delete

Similar to the GDPR's right to be forgotten, the CCPA's right to delete allows individuals to ask organizations to erase their personal data if:

  • The organization collected the personal data from the consumer.
  • The organization no longer needs the personal information to fulfill one of the purposes identified in Cal. Civ. Code Sec. 1798.105 (d).
  • The organization is not entitled to retain the personal data under any of the general exemptions in Cal. Civ. Code Sec. 1798.145.
Data Deletion Requests are different from other DSARs

It's important to note that data deletion rights differ from data access rights. The latter requires organizations to create a report that outlines what information they have about a person and how they use it. Fulfilling data deletion requests usually requires more specificity, insight, and context into how you process the data.

To put this in perspective, an organization could manually fulfill DSARs for the most part if they only receive a low volume of them and only deal with few data sources. But doing so for data deletion requests is more complex.

What Do Data Deletion Requests Require?

Want to efficiently respond to data deletion requests? Then you should prioritize these two factors:

  1. Specificity: You should know where the data is stored as well as any third parties you share it with.
  2. Context: You should be able to correlate the data to an individual, regulatory, or business context in order to determine whether each specific data element must be deleted.

This sounds simple enough, right? Well, it quickly gets complicated! For this reason, we advise you to have a plan in place for managing data deletion requests.

A typical workflow for handling Data Deletion Requests

Here are the steps you should include in your process for taking care of data deletion requests:

  • Determine the legitimacy of the request.
  • Verify the requestor's identity and validate their request.
  • Define what data categories and attributes should be deleted.
  • Elucidate where you store the data.
  • Identify both the technical and business data owners.
  • Determine how to delete the data.
  • Identify who you share the data with and issue a deletion request to them.
  • Ensure you are not processing new data.
  • Define when you can completely fulfill the request.

Note that this outline doesn't include details like how to respond to the request, who manages the process, and which stakeholders are accountable at each step. It's also crucial to remember that policies and reports alone can't solve data deletion requests. To effectively address them, you need a technical solution that fits into your broader privacy management program.

Can you automate Data Deletion Requests?

Due to their complexity, data deletion requests can be more time-consuming and overwhelming to deal with than regular DSARs. Many ticketing-based solutions promise a seamless way to automate them. But like typical DSARs, this can be difficult (if not impossible) to do with these tools.

In truth, ticketing systems only automate tasks such as ticket creation, receipt confirmation, and deadline alerts. An individual's personal data often exists in several formats across numerous in-house, cloud-based, and third-party systems. Ticketing systems can't find, change, or delete all of these different data formats across your systems. That will still depend on you.

Essentially, a ticketing system can tell you what to do. But actually orchestrating the request and ensure your process meets GDPR and CCPA compliance is still on you. Unfortunately, this constitutes the majority of the work involved. So, is automating data deletion requests actually viable? It is with Ketch.

An easier way to Automate Data Deletion

Taking care of data deletion requests offers two main benefits:

  • You comply with GDPR and CCPA rules and avoid penalties.
  • It strengthens trust between your customers and your organization by proving that you take data privacy seriously.

But manually addressing these requests is often easier said than done. Ketch is here to change this. Our solution empowers you to automate your response workflow for DSARs by leveraging tools such as open-source APIs, syntax command templates, and system integration in conjunction with a central control system. As a result, you can automatically record, track, and respond to DSARs like data deletion requests faster and more effectively.

When it comes to privacy data compliance, Ketch puts your data systems to work so you don’t have to. Real automated orchestration of DSARs and data deletion requests is finally here to put an end to the confusion and headaches that usually accompany data compliance.

Click here to schedule your Ketch demo and learn how our platform can simplify your response workflow for DSARs and data deletion requests.

Tags
Privacy Tech
Published
May 14, 2021