Congress asks Tim Cook for an explanation of iOS address book policy
The Path scandal revealed some dangerous negligence in the way Apple handles your address book data, and recent studies have confirmed that the scale of this is huge - apps like Facebook, Twitter and Instagram all make use of the opportunity for free access to all of your contacts, and some apps do access them without even asking your permission.
This seems to counter Apple’s own philosophy on privacy as Steve Jobs himself has underlined numerous times the utmost importance of security of user data. That’s why we were relieved when Apple finally clarified that it’s going to take measures against frivolous interpretation of its guidelines and turn the guidelines into a rule:
“Apps that collect or transmit a user’s contact data without their prior permission are in violation of our guidelines. We’re working to make this even better for our customers, and as we have done with location services, any app wishing to access contact data will require explicit user approval in a future software release,” Apple spokesman Tom Neumayr said for AllThingsD.
So overall, Apple has finally solved a problem that should have been addressed long time ago. Now, what’s interesting is that Cupertino has responded literally minutes after Congress sent a letter, asking for an explanation. Will it get a response beyond what Apple’s spokesperson has just said and does it really need it? Check out the letter below to see what Congress is concerned about.
Mr. Tim Cook
Chief Executive Officer, Apple Inc.
1 Infinite Loop
Cupertino, CA 95014
Dear Mr. Cook:
Last week, independent iOS app developer Arun Thampi blogged about his discovery that the social networking app “Path” was accessing and collecting the contents of his iPhone address book without ever having asked for his consent. The information taken without his permission — or that of the individual contacts who own that information — included full names, phone numbers, and email addresses. Following media coverage of Mr. Thampi’s discovery, Path’s Co-Founder and CEO Dave Morin quickly apologized, promised to delete from Path’s servers all data it had taken from its users’ address books, and announced the release of a new version of Path that would prompt users to opt in to sharing their address book contacts.
This incident raises questions about whether Apple’s iOS app developer policies and practices may fall short when it comes to protecting the information of iPhone users and their contacts.
The data management section of your iOS developer website states: “iOS has a comprehensive collection of tools and frameworks for storing, accessing, and sharing data. … iOS apps even have access to a device’s global data such as contacts in the Address Book, and photos in the Photo Library.” The app store review guidelines section states: “We review every app on the App Store based on a set of technical, content, and design criteria. This review criteria is now available to you in the App Store Review Guidelines.” This same section indicates that the guidelines are available only to registered members of the iOS Developer Program. However, tech blogs following the Path controversy indicate that the iOS App Guidelines require apps to get a user’s permission before “transmit[ting] data about a user”.
In spite of this guidance, claims have been made that “there’s a quiet understanding among many iOS app developers that it is acceptable to send a user’s entire address book, without their permission, to remote servers and then store it for future reference. It’s common practice, and many companies likely have your address book stored in their database.” One blogger claims to have conducted a survey of developers of popular iOS apps and found that 13 of 15 had a “contacts database with millions of records” — with one claiming to have a database containing “Mark Zuckerberg’s cell phone number, Larry Ellison’s home phone number and Bill Gates’ cell phone number.”
The fact that the previous version of Path was able to gain approval for distribution through the Apple iTunes Store despite taking the contents of users’ address books without their permission suggests that there could be some truth to these claims. To more fully understand and assess these claims, we are requesting that you respond to the following questions:
- Please describe all iOS App Guidelines that concern criteria related to the privacy and security of data that will be accessed or transmitted by an app.
- Please describe how you determine whether an app meets those criteria.
- What data do you consider to be “data about a user” that is subject to the requirement that the app obtain the user’s consent before it is transmitted?
- To the extent not addressed in the response to question 2, please describe how you determine whether an app will transmit “data about a user” and whether the consent requirement has been met.
- How many iOS apps in the U.S. iTunes Store transmit “data about a user”?
- Do you consider the contents of the address book to be “data about a user”?
- Do you consider the contents of the address book to be data of the contact? If not, please explain why not. Please explain how you protect the privacy and security interests of that contact in his or her information.
- How many iOS apps in the U.S. iTunes Store transmit information from the address book? How many of those ask for the user’s consent before transmitting their contacts’ information?
- You have built into your devices the ability to turn off in one place the transmission of location information entirely or on an app-by-app basis. Please explain why you have not done the same for address book information.
Please provide the information requested no later than February 29, 2012. If you have any questions regarding this request, you can contact Felipe Mendoza with the Energy and Commerce Committee Staff at 202-226-3400.
Henry A. Waxman, Ranking Member
G.K. Butterfield, Ranking Member
Subcommittee on Commerce, Manufacturing, and Trade
cc: Dave Morin
Path, Co-Founder and CEO
 Arun Thampi, Path Uploads Your Entire iPhone Address Book to Its Servers, mclov.in (Feb. 8, 2012) (available at http://mclov.in/2012/02/08/path-uploads-your-entire-address-book-to-their-servers.html).
 Dave Morin, We Are Sorry, Path Blog (Feb. 8, 2012) (available at http://blog.path.com/post/17274932484/we-are-sorry).
 iOS Data Management (available at https://developer.apple.com/technologies/ios/data-management.html).
 App Store Review Guidelines (available at https://developer.apple.com/appstore/guidelines.html).
 Andrew Couts, Path Privacy Debacle: Is Apple to Blame?, Digital Trends (Feb. 8, 2012) (available at http://www.digitaltrends.com/mobile/path-privacy-debacle-is-apple-to-blame/).
 Dustin Curtis, Stealing Your Address Book, dcurtis (available at http://dcurt.is/stealing-your-address-book). See also Stuart Dredge, Path’s Privacy Problem Poses Questions for all Social Apps, The Guardian (Feb. 9, 2012) (available at http://www.guardian.co.uk/technology/appsblog/2012/feb/09/path-privacy-apps?newsfeed=true); Maryam Nabi, Story the Week: Path’s Privacy Concerns, Financial Times (Feb. 11, 2012) (available at http://blogs.ft.com/fttechhub/2012/02/story-the-week-paths-privacy-concerns/#axzz1mH3eQZ2U); Charlie Osborne, iOS Apps: Massive Invasion of User Privacy, ZDNet (Feb. 8, 2012) (available at http://www.zdnet.com/blog/igeneration/ios-apps-massive-invasion-of-user-privacy/15138).