The state of data privacy in the mobile apps space

8IJMF UIF OVNCFS PG NPCJMF BQQ EPXOMPBET IBT DPOTUBOUMZ JODSFBTFE PWFS UIF ZFBST EBUB QSJWBDZ SJTLT UIFTF BQQT NBZ QPTF IBWF OPU CFFO BEFRVBUFMZ BEESFTTFE

INTRODUCTION

Mobile phones have become a natural corollary to human life and are digital repositories of our everyday experiences. These mobile phones are loaded with applications (apps) that support our mobile based activities and in turn end up collecting a lot of our personal data including sensitive personal data, sometimes on real time basis, generating data privacy concerns for the users. Laws and regulations in relation to data privacy are sprouting all over the world, and amongst them the General Data Protection Regulation (EU) 679/2016 (GDPR) remains in the forefront. The GDPR provides an elaborate legal framework to ensure data privacy and allow data subjects more control over their personal data. GDPR has reinforced that Data Privacy is no longer an issue of trivial compliance and is part of everyday boardroom discussions and a matter of business necessity.

RISK ANALYSIS OF MOBILE APPS

With the numbers of mobile phone users are growing exponentially, market size of mobile phone applications has seen tremendous growth. For a market, which is expected to achieve market size of 497.31 billion dollars by 2026 , data privacy remains a nascent issue. While number of mobile app downloads have constantly increased in the years , data privacy risks these apps may pose have not been adequately addressed. It becomes important to analyze the issues that pose privacy risks for users.

of personal data

Apps collect all sorts of personal data, most of the times collection of such personal data depends on user’s express permission, which means one can toggle on or off permissions to control collection of personal data category. Personal data which apps can access and collect include, location data, personal data, health data, data from camera, wellbeing data etc. Furthermore, mobile phone devices come heavily embedded with various sensors such as microphone, camera, accelerometer, GPS, Wifi, etc. These sensors can generate very personal and copious amounts of data. It also increases the creation of metadata such as metadata in relation to location, time, temperature, and other things.

Much of the personal data is prima facilely, collected through consent, but it also happens behind users back, as observed in the case of metadata. Large part of metadata collection happens without express consent, by default use of sensors, device identifiers etc. With such large of amounts of personal data being generated and collected by way of these applications, risk of privacy invasion increases manifolds as it takes the app developers further away from privacy principles of data minimization and limited processing.

surveillance

Use of identifiers and sensors has seen rampant increase. With new mobile phones being introduced in the market every day, the underlying technology in relation to device identifiers and sensors has also improved. Mobile phone devices come with improved and sophisticated sensors and identifiers. These identifiers are help id and fingerprint the mobile device. While most these identifiers are incorporated as a necessity and were never intended to be utilized for other reasons such as targeted advertising, they are rampantly used by advertising companies to run targeted campaigns. For ex. The IMEI number or a Mac id being unique identifiers to track and isolate android or apple devices, they can also be used by advertising companies to sell ads targeting users having a particular device or model. Apples new ultra-wideband bionic chip which comes in all its latest devices can track and locate all of user movements in real time. This is the latest technology in everyday liquid surveillance, it leaves little or no control for users to control aspects of data processing as the primary design of the technology is resistant to privacy controls and transparency.

Ecosystems

A mobile app ecosystem consists of a large and complex network of actors and controllers, who are associated with the entire lifecycle of development deployment and functioning of the app. Privacy of personal data in mobile applications is largely dependent on how the app is implemented and how it is conceived in its development ecosystem. This inevitably leads to a trade off between functionality and privacy. A bridge between privacy and functionality, can be the concept of privacy by design and default. By following privacy by design and default principles every actor or component related to device hardware and operating system, software development, ad libraries and app store etc., will have to inculcate and design such features, which will automatically support user privacy right from the basic design without compromising on functionality.

While some element of privacy control does appear at various junctures, such as at operating system level, where user control and consent mechanism for data collection is provided, or at app platform level, where app stores require app developers to post a privacy policy and adhere to their data privacy guidelines. For example, Apple recently updated their privacy standards and requires app developers to make elaborate disclosures and put up a privacy policy before they can place their app on the Apple Appstore .

When large amount of personal data is generated, collected and processed, data security becomes an important concern. A recent study in this regard highlights that an exceptionally large portion of apps available today, contain known security lapses, were prone to information leakage and their usage threatened user privacy. In terms of privacy, these apps required more than necessary set of permissions, some of which were classified by Google as ‘’protection level dangerous’’ or “not intended for third party use”. It thus becomes clear that even though in the use of mobile application boomed in the pandemic, the state of mobile privacy did not improve for the better, leaving people exposed to greater privacy related vulnerabilities.

THE WAY FORWARD

Our lifestyles are digitally dependent, and our cultures are based on support from our devices and their applications, which control every aspect of our life and daily activities from lifestyle to education to entertainment and finance. The pandemic has further strengthened this pattern, and thus it becomes important then ever, that privacy obligations are not just remain legal words but are translated into everyday compliance.

and Recommendations Privacy regulators around the globe have come up with set of regulations and guidelines to ensure that legal requirements are incorporated in the overall app development and deployment process. Some examples of such guidelines and recommendation are Article 29 Working Party opinion on “Geolocation services on smart mobile devices” and “Apps on smart

on app developers and the

published “Privacy on the Go: Recommendation for the Mobile Ecosystems” . While many more of such guidance from regulators and industry bodies are available, it becomes imperative for app developers and other actors involved in the ecosystem to adhere and follow such guidelines and incorporate the same at every stage of app development and deployment process.

For processing personal data, apps rely on consent or permissions of the user. The prominent permission architecture is key to absolve all privacy requirements, as all acts relating to collection, sharing and processing of personal data is dependent on a single / universal consent.

The consent mechanism used by the apps is not adequately transparent and does not fulfill the requirement of “true and informed consent”. Thus lack of transparency and full disclosure of the consent mechanisms becomes the first issue in the current state of consent. Secondly, the permission architecture, are burdened to cover multiple groups of activities and processing operations. Studies are show that android apps request additional privacy-risking permissions every three months. Ideally, consent should be obtained for all processing operations under the same purposes and for different processing operations / purposes separate consent should be obtained. Usually, a single step of account registration is treated as consent (by way of action) for an embargo of things such as collection storage processing terms of use etc. Such single action consent seeking actions are not compliant with the privacy law requirements. Lastly, complex permission architecture denies users the right to negotiate consent for primary functionality of the app and for any third-party functionality as well.

information principles Transparency is one the primary privacy requirements second only to accountability. These are golden principles in data privacy that every app owner / developer should achieve. Transparency can be achieved when the app provides a privacy policy, privacy notices embedded in the app, and privacy statements and information submitted by the app is displayed on the app store where users can review permissions and privacy statements beforehand. Further apps should display information when seeking user inputs and provide explainers for app’s special functionality.

Notice / awareness is one of the fair information principles which relates to the golden requirement of openness or transparency. By giving out all the relevant information regarding data collection and handling practices to users, app developers can achieve this principle. Other fair information processing and Enforcement / Redress. What is required that the app ecosystem is at least build around these fair information practice principles.

Data Privacy legislations are aimed at giving more control to individuals over their personal data. And this gives rise to various rights to the data subjects. The GDPR provides data subjects with right to access, erasure, rectification, portability, object etc. It is important for app developers to clearly put out the rights available to users of the app and how they can exercise it. It further becomes essential to put in place simple modalities which allow data subjects to put in their requests and enable app developers to process and honor them. Honoring data subject requests is a shared responsibility of data controllers and data processors as to fully execute data subject requests there needs to be in place a mechanism between them to facilitate processing of data subject requests. This mechanism needs to be simple in design and execution, so that exercising privacy rights doesn’t seem like a burden.

Data Sharing among mobile applications remain a prime privacy concern. Apps share personal data of users with third parties as a matter of functionality and revenue. Apps in order to offer improved and wide range of functionality and features are heavily dependent on complex integration and associations with third parties. In addition to that, the practice of transferring personal data to third parties for the purpose of harvesting is also rampant. Sophisticated third-party trackers are embedded in the source code of multiple mobile apps which tracks, logs and transfers data about a single user, collected from multiple applications ultimately enabling the beneficiary company to form a profile of the user. The widespread and uncheck use of data sharing and harvesting can be attributed to the now popular “freemium” model which allows app developers companies to generate revenue from advertising.

laws regarding transfer and sharing data, unchecked data sharing practices create more complicates privacy issues for the user. Large portion of user privacy issues can be addressed if only the inbuilt permissions architecture allows granting consent to the app, the downstream processers and third parties who are seeking personal data, separately. Such, uncontrolled transmission of data across third parties leads to accountability issues, as well as poses risks of unaccountable and subtle data breaches.

It is important for app developer to be transparent regarding their data handling and sharing practices as well as remain accountable for personal data in their or the third party’s control. Unless steps are taken in this regard, data harvesting and pervasive data transfers will only grow.

1MFBTF SFBE DPODMVEJOH PO TVO EBZHVBSEJBOMJWF DPN