Mobile smartphone apps represent a powerful technology that will only become more important in the years to come. But the unique advantages of the smartphone as a platform — a device that's always on and connected, with access to real world information like user location or camera and microphone input — also raise privacy challenges. And given the sensitivity of the data that many consumers store on their phones, the stakes are even higher for manufacturers, carriers, app developers and mobile ad networks to respect user privacy in order to earn and retain the ever-important trust of the public.
Fortunately, frameworks exist for understanding the privacy rights and expectations of the users. The following guide of best practices pulls from documents like EFF's Bill of Privacy Rights for Social Network Users and the recently released White House white paper "Consumer Data Privacy in a Networked World" to set a baseline for what mobile industry players must do to respect user privacy.
Some of these practices may require the participation of other parties, like the mobile platform provider or ad networks. While each party carries some responsibility, application developers are in a position to take the lead on these issues, whether that means selecting an ad network for its responsible practices or supporting efforts by platforms to incorporate privacy-protective policies and practices.
A mobile user bill of rights
Developers need to create applications that respect these rights.
1. Individual control: Users have a right to exercise control over what personal data applications collect about them and how they use it. Although some access control exists at the operating system level in smart phones, developers should seek to empower users even when it's not technically or legally required by the platform.The right to individual control also includes the ability to remove consent and withdraw that data from application servers. The White House white paper puts it well: "Companies should provide means of with drawing consent that are on equal footing with ways they obtain consent. For example, if consumers grant consent through a single action on their computers, they should be able to withdraw consent in a similar fashion."
2. Focused data collection: In addition to standard best practices for online service providers, app developers need to be especially careful about concerns unique to mobile devices. Address book information and photo collectionshave already been the subject of major privacy stories and user backlash.Other especially sensitive areas include location data, and the contents and metadata from phone calls and text messages. Developers of mobile applications should only collect the minimum amount required to provide the service, with an eye towards ways to archive the functionality while anonymising personal information.
3. Transparency: Users need to know what data an app is accessing, how long the data is kept, and with whom it will be shared. Users should be able to access human-readable privacy and security policies, both before and after installation. Transparency is particularly critical in instances where the user doesn't directly interact with the application (as with, for example, Carrier IQ).
4. Respect for context: Applications that collect data should only use or share that data in a manner consistent with the context in which the information was provided. If contact data is collected for a "find friends" feature, for example, it should not be released to third parties or used to email those contacts directly. When the developer wants to make a secondary use of the data, it must obtain explicit opt-in permission from the user.
5. Security: Developers are responsible for the security of the personal data they collect and store. That means, for example, that it should be encrypted wherever possible, and data moving between a phone and a server should always be encrypted at the transport layer.
6. Accountability: Ultimately, all actors in the mobile industry are responsible for the behaviour of the hardware and software they create and deploy. Users have a right to demand accountability from them.
Best technical practices
How should developers best keep in line with this bill of rights? Here are some specific practices that developers should use to preserve user privacy.
• Anonymising and obfuscation: Wherever possible, information should be hashed, obfuscated, or otherwise anonymised. A "find friends" feature, for example, could match email addresses even if it only uploaded hashes of the address book.
• Secure data transit: TLS connections should be the default for transferring any personally identifiable information, and must be the default for sensitive information.
• Secure data storage: Developers should only retain the information only for the duration necessary to provide their service, and the information they store should be properly encrypted. Internal security: Companies should provide security not just against external attackers, but against the threat of employees abusing their power to view sensitive information.
• Penetrationtesting: Remember Schneier's Law: "Anyone, from the most clueless amateur to the best cryptographer, can create an algorithm that he himself can't break." Security systems should be independently tested and verified before they are compromised.
• Do Not Track: One way for users to effectively indicate their privacy preferences is through a Do Not Track (DNT) setting at the operating system (OS) level. Currently, DNT is limited mostly to web browsers, and only Mozilla's under-development Boot2Gecko supports the Do Not Track flag at the OS level. But developers would benefit from the clear statement of privacy preferences, and should encourage other OS makers to add support.
These recommendations represent a baseline, and all the players-from the application developers to the platform providers to the ad networks and more-should work to meet and exceed them. As the mobile app ecosystem has matured, users have come to expect sensible privacy policies and practices. It's time to deliver on those expectations.
Republished under Creative Commons Licence from Electronic Frontier Foundation.