There’s lots of guides on the internet to consent and so-forth, but relatively few that dive into hands-on implementation details. DataGrail is happy to describe two less-discussed aspects of a compliant GDPR programme: Data inventory and mapping and operationalizing GDPR requests.
Data inventory and mapping
When speaking to companies, we’ve observed confusion surrounding how to perform data mapping and inventory. Often, legal teams possess a strong understanding of regulatory requirements and the goals of company operations but they don’t share the same knowledge of systems and data movements implemented across marketing and sales.
As a modern business, it’s likely that you store more personal data, in more systems, than you’re aware of. This guide will help locate all of it.
A straightforward manner of building a comprehensive data mapping is:
Pay close attention to these classes of high-risk systems:
Be aware that many companies -- like Salesforce, Adobe, Google, and Oracle -- offer suites of tools for marketing and sales. Carefully track down the exact subsets of their tools your company uses and create a process for authorizing (with your legal team) any new usage or data flows.
It is a best practice, even if you aren't a SOC 2 or similarly certified organization, to establish a mandatory vendor evaluation process, including legal, before any new software is purchased or new data flows are implemented. Otherwise, your mapping may be out of date within months.
Implementing a data subject intake and response process
With your data inventory exercise complete, you’re ready to craft your GDPR / CCPA data request intake and response process.
You also need an internal request intake method, so that GDPR requests directed to your sales or marketing teams aren’t dropped. Train your teams to never ignore these requests -- and if there is any doubt about what is being requested -- to notify legal to handle disposition. These requestors are often annoyed by a sales or marketing communication, making careful handling crucial.
Below is a 3-step process for efficiently handling data requests.
Step 1: Receiving and initially responding to a request
After receiving a request, send the requestor an automated receipt. Your goal here is twofold:
Once you have a request in hand, and an acknowledgement sent, classify the requestor as a customer, former customer, or a prospect. This informs what identity verification you need to perform and what systems will have to be searched for data. Depending on the request intake modality, you should also verify control of the email address for which the request was submitted and perform identity verification, if necessary.
Step 2: Compiling and organizing request data
Now you must search all the systems identified above for personal data related to this subject; here, the rule of thumb is that a company with a £100 million turnover will have approximately 75 systems that contain personal data. If you have identified fewer, it is very likely your inventory has missed some of the systems.
After extracting all the data, we suggest providing it in two forms: a properly formatted human-readable extract, and an Article 20 structured, machine-readable format. This allows a single internal process to satisfy Article 15 and 17 data subject rights, as well as Article 20 portability rights.
Providing a properly formatted and structured summary of the data is crucial to avoid any confusion, as you want the requestor to clearly understand what data you have, why you have it, and what you’re doing with it.
Step 3: Completing a request
Finally, send the data you have gathered to the requestor. And make sure you respond to all requests, even those you deem invalid or for which you can’t surface any personal data. It’s a best practice to send your response to the requestor in some way that affirmatively confirms receipt.
Keep a work diary, both to inform the further evolution of your internal GDPR handling process and to supply to regulators in case of any complaint.
At the end of this process, you will have successfully completed a GDPR request!
Article originally published on GDPR:Report