Critical Path: Here's how Path can save itself, if it acts fast
Summary: Four simple steps that Path can follow -- right now -- to save its reputation and potentially, its business.
Earlier today I posted about how upstart social network Path was discovered uploading iOS user's entire address books to it's servers without notification and without asking for permission.
Here are four simple things that Path can do to right the ship, but the clock's ticking...
- Don't wait for Apple to approve the 2.0.6 version of your iOS app with the opt-in feature. That could take days or weeks.
- Allow users to delete their address book contents via your Web portal right now. (And do us a favor and dispense with the PR sounding "Automatic Moments" crap, we know that it's just spin for automatically share our location).
- Promise that the Address Book data that you've already compiled will be permanently deleted.
- Beg for mercy. Don't spin it or try the "it's a feature" garbage, either. Just come clean and tell your users that you screwed up.
It's quite simple really. If Path did the above by tomorrow, I'd consider re-installing the iOS app. But if it doesn't, Path will suffer irreparable damage and users will defect in droves.
Path already dodged a bullet with it's creepy automatic location sharing "feature" and I'm not sure that it can pull another rabbit out of its hat unless it takes immediate and decisive action.
Would you use Path for iOS in its current state?
Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.

Talkback
RE: Critical Path: Here's how Path can save itself, if it acts fast
As beautiful as Path is, and as good as its user experience, I won't be using it again until this is fixed.
RE: Critical Path: Here's how Path can save itself, if it acts fast
Not using it again is good, but ...
The company was obviously deceptive about harvesting that data. Can they really be trusted to not use it or sell it for whatever purpose?
I know you're calling for that data to be deleted, but can Path really be trusted to do so? Is there any way to legally force Path to delete it? Is there a law or at least legal precedent to use as leverage?
Folks saying "I won't use it again until it's fixed" is fine. Frankly, I haven't used it and won't, now ... or probably ever, since I wouldn't feel like I could trust them. But I'm equally concerned about MY data already being in Path's databases without my permission, what they might do with it, and how that might impact me -- and I'm not even a Path user/customer.
RE: Critical Path: Here's how Path can save itself, if it acts fast
Privacy in iOS
Grabbing all the data you can is such a temptation for a programmer when bandwidth and servers are so cheap....
P
There should be no recovery for this product
RE: Critical Path: Here's how Path can save itself, if it acts fast
Who does such things?