Path discovered phoning home with your address book
Summary: Upstart social network Path was discovered uploading users' complete address book to its servers. Completely inexcusable in today's privacy-sensitive society.
That's basically the response from Path's management after the popular social networking service was discovered uploading users' complete address book to its servers.
Path, for the unfamiliar, is a relatively new social network, billed as a "smart journal that helps you share life with the ones you love." Think Foursquare meets Instagram meets (insert name here).
Developer Arun Thampi discovered the privacy issue and posted this to his blog:
It all started innocently enough. I was thinking of implementing a Path Mac OS X app as part of our regularly scheduled hackathon. Using the awesome mitmproxy tool which was featured on the front page of Hacker News yesterday, I started to observe the various API calls made to Path’s servers from the iPhone app. It all seemed harmless enough until I observed a POST request to https://api.path.com/3/contacts/add.
Upon inspecting closer, I noticed that my entire address book (including full names, emails and phone numbers) was being sent as a plist to Path. Now I don’t remember having given permission to Path to access my address book and send its contents to its servers, so I created a completely new “Path” and repeated the experiment and I got the same result – my address book was in Path’s hands.
Um, yeah. Your entire address book.
Now I don't know about you, but I'd certainly expect a feature like address book upload to be opt-in (and optional) -- not hidden with no way to opt-out. The other problem is the once Path already has your contact data, there's no way to delete it -- at least that I can find.
Path CEO Dave Morin quickly went into damage control mode and gave the classic It's-a-feature-not-a-bug response, saying that the app uploads your entire address book "in order to help the user find and connect to their friends and family on Path quickly and effeciently as well as to notify them when friends and family join Path." Morin goes on to explain that Path 2.0.6 for iOS makes address book upload opt-in, noting that it's pending App Store approval.
Dan, it might be time to call in a few favors at Apple and get 2.0.6 escalated.
Not clearly disclosing a "feature" like complete address book upload and not giving users a simple way to opt-out is inexcusable. Many thanks to Arun (and the mitmproxy tool) for exposing this privacy breach.
Delete.
Update: It's time for Apple to require that developers to disclose aspects of their apps that will impact user's privacy. This is one key area where the Android Market does things better than the App Store does. Here's a sample of the permission screen that you must acknowledge before installing the app My Tracks.
Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.



Talkback
RE: Path discovered phoning home with your address book
Agreed.
RE: Path discovered phoning home with your address book
RE: Path discovered phoning home with your address book
This must be a joke. The part about privacy-sensitive society that is.
RE: Path discovered phoning home with your address book
And then there are the ones who don't bother to even mention half the things they do in the EULA at all ...
Audit
Sad this isn't enforced in the OS
So why did "app store" approve this version?
(1) It's just information, I trust them to only use it appropriately, they're on our side!
(2) Probably planted there by a conspiracy from apple's competitors, to discredit them.
(3) On second thought, apple doesn't have any competitiors...you can't compete with God.
(4) No big deal, privacy is overrated and much less important than having the latest useless crap on my igadget.
RE: Path discovered phoning home with your address book
Look up sarcasm
RE: Path discovered phoning home with your address book
RE: Path discovered phoning home with your address book
RE: Path discovered phoning home with your address book
RE: Path discovered phoning home with your address book
Fully agree, but really, with so many apps coming from outside US borders, and mainly Asia, where integrity has totally a different significance, good luck in getting it to happen.
I suppose one solution might be to refrain from using any app which does not origonate in the US - but then one has the challenge of trying to realistically determine that detail. Often a look at user docs can be a big clue (Chinglish, eg.), but not always.
Enron was totally US-held
Yes.. and no...
However, no context is given as to what those operation calls are actually used for. You typically need to ask the developer directly what they intend to use the calls for, and even that isn't necessarily the truth (though some are pretty good about disclosing usage on their website or product description). This is already a big issue around resources that in-app advertisements need. They often need full access to the internet, and possibly your location to serve up localized ads. However, granting access to that also allows the app itself to piggy-back on those opt-in credentials to send/post your location to a server somewhere.
If I were a malicious app developer, I could say, "today I'm requiring access to your address book to locally show you a list of contacts for some [insert plausible, innocent purpose here]. Not doing anything fishy with them.". Especially for a social network app like "Path", this seems reasonable, so you opt in by installing the application.
Later, I change the app so I'm scraping your contacts and uploading them to my server. You upgrade (or allow Android to auto-upgrade since the declared operations haven't changed).
I issue another upgrade a week later and remove that scraping code.
And suddenly, I've managed to turn a very innocent app into a very evil one and then back to an innocent one. I've gotten your contacts and you probably don't even know it. And unless someone is scrutinizing every release that comes out, nobody will know I was able to at some point.
Bingo....not what....why
Still better than the Apple approach though
Simple solution
A journal is something private
Even if we supported e.g. iCloud all data would get uploaded encrypted and nobody could read it. I think that this is essential for a product that keeps a lot of your private data. You can export and import entries in over five formats and choose between exporting a single entry or the whole diary. This is very important, because essentially you would loose all your entries if a company would go out of business and offered no export functionality.
The apps requiring all those permissions