The Paranoid Can Relax, Facebook Dials Up Privacy With Places

Next Story

iLunascape: Free iPad Browser Combines Tab Browsing With iPad-Specific UI

Updated: After careful consideration, I’m retracting my B and replacing it with a C-, penalizing Facebook for superfluous complexity and a lack of transparency. I wrote the original article on Wednesday evening, after attending the press event, carefully reading the company’s blog post, comparing notes and talking to several Facebook representatives. While the following information is correct, Facebook did not fully explain that there are three different stages to “opting-in.” We talked to Facebook on the phone today, expressed our concern, and they acknowledged that there was a lack of clarity. Facebook is currently making a demo video to properly address these privacy issues. In the meantime, Jason Kincaid has delivered a must-read explanation of these three opt-in stages here.

The following is my original post:

Less than one hour after Facebook struck the ceremonial gong, signaling the official birth of Places, the ACLU of Northern California was ready to cry foul play.

In a 429-word post titled, “Facebook Places: Check This Out, Before You Check In,” the ACLU branch rips the new feature for a perceived lack of user control, complaining (in dramatically bold font) that “in the world of Facebook Places, “no” is unfortunately not an option.” While this anonymous ACLU member may have a real knack for writing movie trailers, I don’t buy the case they’re building against Facebook.  To be honest, I’ve never been a fan of Facebook’s history with privacy, but they are making a real effort to dial up privacy with Places.

So while all sins are not forgiven, let’s start with a solid B for Places and a promise not to burn them at the stake (at least not today). First, let’s walk through what you need to know as a user (this post is updated with further clarification from Facebook’s Director of Policy Communications, Barry Schnitt).

Facebook will not automatically broadcast your location data on Places. You cannot pass go, you cannot collect $200, until you give Facebook the greenlight. As a first time user, you have to check-in yourself via the iPhone app or touch.facebook.com or your friend has to check-in for you. If your friend tries to check you in, you have two options: pick “not now” or to accept friend check-ins (as implied, once you select yes, you will automatically accept friend check-ins). In their Places guide, the ACLU brings up the valid point that if you pick “not now,” you will continue to receiving annoying check-in requests every time a friend tags you. Of course, there’s an easy fix, simply go into your privacy settings, click on “customize settings” under “Sharing On Facebook,” scroll down to the second section (“Things Others Share”) and switch “Friends Can Check Me Into Places” to disabled.

Places will tell you when your friend has checked you in. Similar to photo tags, you will be notified every time a friend checks you in. And like photos, you can untag yourself. The ACLU and other critics are wagging their fingers at Facebook for automating this process and not giving the user the choice to accept or reject every single request. Facebook had to make a judgment call here, between enhancing control and making the experience easy and enjoyable. As a new user, I would be frustrated by a service that demanded my attention for every friend check-in. Of course there is a chance that a rampaging ex-girlfriend or arch nemesis will exploit this tool to slander your good name, tying you to trysts that never happened or houses of ill repute—- then again, there is that nifty difty defriend option.

Here Now is not the devil. This is probably the most controversial aspect of Places. The feature is enabled by default if you have loose privacy settings, however, it is not enabled if you’ve set your master privacy control to Friends of Friends or Friends or if you’ve customized your settings to be restrictive.

Under “People Here Now,”  you can see who else has checked into a location with you. This public check-in  (which is only public to those that have checked into the location) is only available for a short period of time. In a longer post detailing the features of Places, the ACLU chided Facebook for not giving users granular controls on Here Now. The ACLU claims that users can only choose between enable and disable and cannot narrow their Here Now audience to just friends or something more customized. While Here Now is technically an on or off switch, by turning it off and customizing your Places profile, Facebook effectively achieves the ACLU’s demands. As Facebook’s Director of Policy Communications, Barry Schnitt told us, “By configuring the Places I Check-In setting, which can be configured granularly, and turning off Here Now, you guarantee that only the people you specify will see you on a Place page. Their [the ACLU] suggestion adds complexity without adding any utility and we are very surprised that a privacy advocate would be taking such a position, especially after all of the progress we’ve made in making control on Facebook simple and easy to use.”

The default is friends-only. When you begin completing and accepting check-ins only your friends can see your activity, not your friends or friends or your college network, just your friends. I can’t really give Facebook a lot of credit for this one, it’s just good common sense. Under your privacy settings you can customize this further, even selecting which friends can see your check-ins. Considering the sensitivity around location, I think Zuckerberg & Co. recognized early on that any default less than “friends only” would be an open invitation for privacy sharks.

Your apartment is safe. During the press conference, someone asked the Facebook team what would happen if someone turned their apartment into a “place” on Facebook, how could they protect their privacy in that situation? We spoke to Facebook Product Manager Michael Sharon who says the company has a strong system in place to rapidly accept complaints from users. While there is no set time frame for handling a red flag, he says problems will be dealt with swiftly and often within 24 hours. See video below.

Sharing is not always caring: the ACLU’s best point. There is one place where I find common ground with the ACLU: Facebook’s policy when it comes to sharing location information with third-party applications. As a user, the applications you install will need your explicit permission to get your check-in information. That’s valid, however, if your friend has weak privacy settings, s/he is free to share your check-in information to applications and Connect partners. This can be easily remedied by unchecking a box in your privacy settings but it is permitted by default.  According to Schnitt, this exchange exposes information on your “check-ins, details about a place, ability to search for places and check-ins from friends.”

Not surprisingly, Facebook claims this is all in the name of creating “new social experiences with location.”

I completely agree that it will ultimately enhance applications (and Facebook’s bottom line) but this should be an opt-in service. For example, when you first check-in or accept check-ins, Facebook should immediately ask you if you want to give your friends’ applications access to your check-in data. To be fair to its users, Facebook needs to increase the visibility of this feature. Because nlike the other settings, like Here Now, this exchange takes place in the background and I suspect the vast majority of Facebook users will not know that their data is being quietly siphoned off by their friends’ applications.

If after all this you’re still thrusting your pitchfork in the air, you can always click here.

Bonus: On Wednesday, we also got a chance to sit with Sharon for a longer, 5-minute interview. He discussed the story behind Facebook Places, the importance of tagging and navigating their partnerships.

More information can be found on Facebook’s blog post here.

(Top image via Flickr/Colin Purrington)

blog comments powered by Disqus