ARTICLE
30 September 2019

Saikali And Paine Explain The Catch-22 Of GDPR's Subject Access Requests

SH
Shook, Hardy & Bacon

Contributor

Shook, Hardy & Bacon has long been recognized as one of the premier litigation firms in the country. For more than a century, the firm has defended companies in their most substantial national and international products liability, mass tort and complex litigation matters.

The firm has leveraged its complex product liability litigation expertise to expand into several other practice areas and advance its mission of “being the best in the world at providing creative and practical solutions at unsurpassed value.” As a result, the firm has built nationally recognized practices in areas such as intellectual property, environmental and toxic tort, employment litigation, commercial litigation, government enforcement and compliance, and public policy.

Shook Partner Al Saikali and Associate Kate Paine have authored "Subject Access Requests and Identity Verification: Navigating a Data Controller's Catch-22" for Financier Worldwide
United States Privacy

Shook Partner Al Saikali and Associate Kate Paine have authored "Subject Access Requests and Identity Verification: Navigating a Data Controller's Catch-22" for Financier Worldwide. The article offers practical advice for how companies can respond to subject access requests, through which individuals can request data a company possesses under the EU's General Data Protection Regulation (GDPR). If an individual requests data, Paine and Saikali explain, the data controller must verify the individual's identity, but it must not request more identifying data than necessary.

"The keys to identity verification are the existence of reasonable doubt about the requester’s identity, and requesting only what additional information is 'necessary' – keeping in mind the GDPR’s bedrock principles of data minimisation and proportionality – and that can be obtained by 'reasonable measures,'" the authors explain. "Ensuring that the information requested, and the measures employed to obtain that information, are reasonable turns on a more nuanced context-driven and risk-based approach. In many situations, the most reasonable method of confirming the requester’s identity will be to use data already in the controller’s possession."

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

Mondaq uses cookies on this website. By using our website you agree to our use of cookies as set out in our Privacy Policy.

Learn More