The European Data Protection Supervisor adopted this week “Guidelines on the protection of personal data processed by mobile applications provided by European Union institutions”.
While the guidelines are addressed to the EU bodies that provide mobile apps to interact with citizens (considering the mandate of the EDPS is to supervise how EU bodies process data), the guidance is just as valuable to all controllers processing data via mobile apps.
The Guidelines acknowledge that “mobile applications use the specific functions of smart mobile devices like portability, variety of sensors (camera, microphone, location detector…) and increase their functionality to provide great value to their users. However, their use entails specific data protection risks due to the easiness of collecting great quantities of personal data and a potential lack of data protection safeguards.”
Managing consent
One of the most difficult data protection issues that controllers of processing operations through mobile apps face is complying with the consent requirements. The Guidelines provide valuable guidance on how to obtain valid consent (see paragraphs 25 to 29).
- Adequately inform users and obtain their consent before installing any application on user’s smart mobile device
- Users have to be given the option to change their wishes and revoke their decision at any time.
- Consent needs to be collected before any reading or storing of information from/onto the smart mobile device is done.
- An essential element of consent is the information provided to the user. The type and accuracy of the information provided needs to be such as to put users in control of the data on their smart mobile device to protect their own privacy.
- The consent should be specific (highlighting the type of data collected), expressed through active choice, freely given (users should be given the opportunity to make a real choice).
- The apps must provide users with real choices on personal data processing: the mobile application must ask for granular consent for every category of personal data it processes and every relevant use. If the OS does not allow a granular choice, the mobile application itself must implement this.
- The mobile application must feature functionalities to revoke users’ consent for each category of personal data processed and each relevant use. The mobile application must also provide functionalities to delete users’ personal data where appropriate.
The Guidelines invite controllers to “analyse the compliance of its intended processing before implementing the mobile application during the feasibility check, business case design or an equivalent early definition stage of the project”. The controller “should take decisions on the design and operation of the planned mobile application based on an information security risk assessment”.
Other recommendations concern:
- data minimisation – “the mobile application must collect only those data that are strictly necessary to perform the lawful functionalities as identified and planned”.
- third party components or services – “Assess the data processing features of a third party component or of a third party service before integrating it into a mobile application”.
- security of processing – “Apply appropriate information security risk management to the development, distribution and operation of mobile applications” (paragraphs 38 to 41).
- secure development, operation and testing – “The EU institution should have documented secure development policies and processes for mobile applications, including operation and security testing procedures following best practices”.
- vulnerability management – “Adopt and implement a vulnerability management process appropriate to the development and distribution of mobile applications” (paragraphs 47 to 51).
- protection of personal data in transit and at rest – “Personal data needs to be protected when stored in the smart mobile device, e.g. through effective encryption of the personal data”.
***
Find what you’re reading useful? Consider supporting pdpecho.
Main points from FTC’s Internet of Things Report
FTC published on 27 January a Report on the Internet of Things, based on the conclusions of a workshop organised in November with representatives of industry, consumers and academia.
It is apparent from the Report that the most important issue to be tackled by the industry is data security – it represents also the most important risk to consumers.
While data security enjoys the most attention in the Report and the bigger part of the recommendations for best practices, data minimisation and notice and choice are considered to remain relevant and important in the IoT environment. FTC even provides a list of practical options for the industry to provide notice and choice, admitting that there is no one-size-fits-all solution.
The most welcomed recommendation in the report (at least, by this particular reader) was the one referring to the need of general data security and data privacy legislation – and not such legislation especially tailored for IoT. FTC called the Congress to act on these two topics.
Here is a brief summary of the Report:
The IoT definition from FTC’s point of view
Everyone in the field knows there is no generally accepted definition of what IoT is. It is therefore helpful to know what FTC considers IoT to be for its own activity:
In addition, FTC clarified that, consistent with their mission to protect consumers in the commercial sphere, their discussion of IoT is limited to such devices that are sold to or used by consumers.
Stunning facts and numbers
Data security, the elephant in the house
Most of the recommendations for best practices that FTC made are about ensuring data security. According to the Report, companies:
Attention to de-identification!
When a company states that it maintains de-identified or anonymous data, the Commission has stated that companies should
Notice and choice – difficult in practice, but still relevant
No need for IoT specific legislation, but general data security and data privacy legislation much needed
Share this:
Like this:
Leave a comment
Posted in Comments, News, US and Canada
Tagged data minimisation, data security, data security legislation, de-identification, defense-in-depth approach, federal trade commission, FTC data privacy legislation, FTC Report on Internet of Things summary, FTC Report on IoT, Gabriela Zanfir, Internet of Things, Internet of Things definition, notice and choice in Internet of Things, privacy, what is Internet of Things