Privacy Ref Blog

Don’t be too quick to publish a privacy notice

Having a privacy notice for customers to review is an essential part of any privacy program. When Delta Airlines added a privacy notice to their mobile app, “Fly Delta”, to comply with California law, the policy did not reflect reality. When creating a privacy notice you need to say what you do and do what you say.

Delta’s mobile app and a privacy notice

California’s Attorney General, Kamala D. Harris, has been very transparent in her plans for enforcement of the California Online Privacy Protection Act which requires an operator of a web site, including mobile apps, that collects personal information to conspicuously post a privacy notice. Last month AG Harris’s office gave Delta Air Lines (among other companies) 30 days to post a privacy notice in their mobile app; Delta did not comply.

In a press release last Thursday, AG Harris’s office announced that a lawsuit had been filed against Delta seeking to halt distribution of their app plus impose a fine of $2,500 for each violation of the California law. A copy of the complaint can be found here.

On Friday Delta responded by publishing a privacy notice for its mobile app. Ashkan Soltani, “an independent researcher and consultant focused on privacy, security, and behavioral economics” who was previously a technologist at the Federal Trade Commission, discovered that the app collected and shared an iPhone’s UDID, a unique identifier for each device, something that was not stated in the published privacy statement.

Did the development team understand the privacy notice requirements?

At a minimum it would be fair to say that there was a lack of understanding on the part of the privacy notice’s writer about how the app worked. Unfortunately this is not unusual as legally trained individuals may not be technology savvy and the technologists may not be legally knowledgeable.

There is often a disconnect in communications between a legal team and a technical team. The two disciplines have different priorities and use different terminology. What may be a viewed as a common practice by the technologists may be viewed as a legal problem by the attorneys. Without a “common language” the attorneys may not have known what to ask and the technologists may not know what to share.

Avoiding the problem – Privacy by Design

The publishing of a privacy notice with the mobile or any other application should be a business requirement of a project from the start. The same can be said of meeting any other privacy standards imposed by an organization. Developers, business analysts, and project managers may not be completely versed in an organization’s internal and external privacy requirements; a privacy specialist must have a seat at the table when requirements are being defined.

Make a Privacy Risk Assessment an integral part of the design stage of any initiative, e.g. when designing the technical architecture of a system, pay particular attention to potential unintended uses of the personal information.

Base identity metasystems on the “Laws of Identity,” intended to codify a set of fundamental principles to which universally adopted, sustainable identity architecture must conform.

Consider privacy in system development lifecycles and organizational engineering processes. System designers should be encouraged to practice responsible innovation in the field of advanced analytics.

Embed privacy into regulatory approaches that may take the form of self-regulation, sectoral privacy laws, omnibus privacy legislation and more general legislative frameworks, calling for an approach guided by “flexibility, common sense and pragmatism.”

In addition to an effective awareness program, the first three of these actions should be incorporated into the practices of any organization that is undertaking the implementation of a new system. In Delta’s case, this would have provided the necessary details and time to create a complete, accurate privacy notice.

Bob Siegel, the founder and President of Privacy Ref, Inc., has extensive professional experience in the development and improvement of privacy policies and procedures, the definition of performance metrics to evaluate privacy maturity, and the evaluation of compliance. He utilizes a combination of alignment, adaptability, and accountability strategies to guide organizations in achieving their privacy goals.

He is a Fellow of Information Privacy (FIP) and a Certified Information Privacy Professional, awarded from the International Association of Privacy Professionals, with concentrations in U.S. private-sector law (CIPP/US), US public sector law (CIPP/G), European law (CIPP/E), and Canadian law (CIPP/C). He is also a Certified Information Privacy Manager (CIPM) and Privacy Technologist (CIPT).

Siegel is a member of the IAPP faculty, has served on the Certification Advisory Board for the CIPM program the Publications Advisory Board.

On our last webinar (as of this writing) I discussed how a company can handle data subject’s rights requests under GDPR. Many of these requests are going to require attention, such as those ‘right to be forgotten’ requests. Others may seem daunting but can be handled easily and may not require any direct participation from your end.
Continue reading this post...