<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>The Apps Law Blog &#187; privacy</title>
	<atom:link href="http://www.appslawblog.com/tag/privacy/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.appslawblog.com</link>
	<description>iPhone, mobile, Facebook and other software apps, and the law.</description>
	<lastBuildDate>Wed, 28 Jul 2010 20:15:30 +0000</lastBuildDate>
	<generator>http://wordpress.org/</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Facebook privacy settings you should get to know</title>
		<link>http://www.appslawblog.com/facebook-privacy-settings-you-should-get-to-know/</link>
		<comments>http://www.appslawblog.com/facebook-privacy-settings-you-should-get-to-know/#comments</comments>
		<pubDate>Thu, 04 Feb 2010 01:15:52 +0000</pubDate>
		<dc:creator>Eric Seidmon</dc:creator>
				<category><![CDATA[Facebook]]></category>
		<category><![CDATA[Arnstein & Lehr]]></category>
		<category><![CDATA[e-Commerce Times]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Misha Kerr]]></category>
		<category><![CDATA[privacy]]></category>

		<guid isPermaLink="false">http://www.appslawblog.com/?p=709</guid>
		<description><![CDATA[<p><a href="www.facebook.com"><img class="alignright" src="http://profy.com/wp-content/blogs.dir/1/files/2009/01/facebook-privacy-settings.png" alt="" width="323" height="166" /></a>Facebook recently modified its <a href="http://www.facebook.com/policy.php">privacy settings</a>; so should you. What may seem private may very well be public to all of cyberspace.</p>
<p>In an interview with <a href="http://www.technewsworld.com/rsstory/69158.html">e-Commerce Times</a>, <a href="http://legalnews.arnstein.com/">Arnstein &#38; Lehr</a> attorney <a href="http://legalnews.arnstein.com/misha-j-kerr/">Misha Kerr</a> made the&#8230;</p>]]></description>
			<content:encoded><![CDATA[<p><a href="www.facebook.com"><img class="alignright" src="http://profy.com/wp-content/blogs.dir/1/files/2009/01/facebook-privacy-settings.png" alt="" width="323" height="166" /></a>Facebook recently modified its <a href="http://www.facebook.com/policy.php">privacy settings</a>; so should you. What may seem private may very well be public to all of cyberspace.</p>
<p>In an interview with <a href="http://www.technewsworld.com/rsstory/69158.html">e-Commerce Times</a>, <a href="http://legalnews.arnstein.com/">Arnstein &amp; Lehr</a> attorney <a href="http://legalnews.arnstein.com/misha-j-kerr/">Misha Kerr</a> made the point abundantly clear that &#8220;what you think is a private page is not private, and you never know who has access to it.&#8221;</p>
<p>Privacy settings and how you use them are becoming the subject of intense litigation. Kerr represented a person who inadvertently attended a filming party for an adult website.  The young woman never signed a release for her images but ended up on the adult Web site anyway. Kerr sued on behalf of the client, claiming violation of privacy and damage to her reputation.</p>
<p>The defendant responded by showing photos the woman had posted to a social networking site which were risque, arguing that her reputation could not be damaged too seriously. Just a few changes to the woman&#8217;s privacy settings could have changed the lawsuit&#8217;s outcome.</p>
<p>Many Facebook users face a similar risk of having their private lives exposed if they opted for settings Facebook recommended in December 2009. They may not have understood to what they were were agreeing.</p>
<p>If you fall into this category, read on. If not, you should still read on unless you don&#8217;t care about your privacy. The recommended settings are somewhat unsettling.  They give Facebook the right to publicize your own Facebook page&#8217;s private information  such as your photos, status updates and items you&#8217;ve posted.</p>
<p>The Web site <a href="http://www.readwriteweb.com/archives/the_3_facebook_settings_every_user_should_check_now.php">ReadWriteWeb.com</a> lists the three most important privacy settings to make sure you have set to your needs.  The first covers things you share, such as your status updates, photos, videos and other posted items; the second addresses who can see your personal information; and the third determines whether your account is accessible to search engines like <a href="www.google.com">Google</a>.</p>
<p>All three  settings and more can be modified. For step-by-step directions, visit the <a href="http://www.readwriteweb.com/archives/the_3_facebook_settings_every_user_should_check_now.php">ReadWriteWeb.com link</a>.</p>
Similar Posts:<ul><li>None Found</li></ul>]]></content:encoded>
			<wfw:commentRss>http://www.appslawblog.com/facebook-privacy-settings-you-should-get-to-know/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Facebook pictures prevented woman from receiving disability benefits</title>
		<link>http://www.appslawblog.com/facebook-pictures-prevented-woman-from-receiving-disability-benefits/</link>
		<comments>http://www.appslawblog.com/facebook-pictures-prevented-woman-from-receiving-disability-benefits/#comments</comments>
		<pubDate>Wed, 02 Dec 2009 01:28:49 +0000</pubDate>
		<dc:creator>Eric Seidmon</dc:creator>
				<category><![CDATA[Facebook]]></category>
		<category><![CDATA[Canada]]></category>
		<category><![CDATA[Chippendales]]></category>
		<category><![CDATA[depression]]></category>
		<category><![CDATA[insurance]]></category>
		<category><![CDATA[International Business Times]]></category>
		<category><![CDATA[Manulife]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[social networking]]></category>

		<guid isPermaLink="false">http://www.appslawblog.com/?p=412</guid>
		<description><![CDATA[A woman's insurance company cut her disability benefits after its agent found photos of her on vacation through Facebook. The action could lead to a lawsuit. The dispute serves as a reminder that one posts on Facebook or any other social networking site is public information, not a private diary.  

]]></description>
			<content:encoded><![CDATA[<p><a href="www.facebook.com"><img class="alignright" src="http://lifeinthenhs.files.wordpress.com/2009/02/facebook.jpg" alt="" width="209" height="156" /></a>A dispute in <a href="http://canada.gc.ca/home.html">Canada</a> has brought light to an emerging privacy issue over the use of <a href="www.facebook.com">Facebook</a> photos. Nathalie Blanchard&#8217;s insurance company cut her disability benefits after their agent found photos of her on vacation through Facebook.  When she was diagnosed with severe depression her psychiatrist told her to go on vacation.  Until the payments ended this fall, she had been receiving monthly sick-leave benefits.  Blanchard now plans to take her insurer, <a href="http://www.manulife.com/public/home/index/0,,lang=en,00.html">Manulife</a>, to court.</p>
<p>Manulife told Blanchard that her Facebook photos showed that she was able to work.  According to Blanchard&#8217;s attorney, Manulife claimed that pictures of Blanchard having a good time at a <a href="http://www.chippendales.com/">Chippendales</a> bar show, at her birthday party and on a vacation were enough proof to show that she was no longer depressed.  Her attorney says she had the right to go on a vacation and claims that she was wrongfully dismissed from her benefits.</p>
<p><a href="http://www.ibtimes.com.au/articles/20091124/women-losses-disability-benefits-over-facebook-pictures.htm">International Business Times</a> reports that Manulife has declined to comment on this dispute but has said in a statement that the company would not deny or terminate a valid claim simply because of published information on social networking sites like Facebook.</p>
<p>However, Blanchard&#8217;s attorney is claiming that her doctor recommended she go on vacation and that Manulife terminated her disability benefits without proper medical recommendations, relying on the Facebook photos instead.</p>
<p>The lesson: Be careful what you post on Facebook or any other social networking site; it is public information, not a private diary.</p>
Similar Posts:<ul><li>None Found</li></ul>]]></content:encoded>
			<wfw:commentRss>http://www.appslawblog.com/facebook-pictures-prevented-woman-from-receiving-disability-benefits/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Lawsuits over Facebook&#8217;s Beacon app complicate possible settlements</title>
		<link>http://www.appslawblog.com/lawsuit-facebook-beacon-complicate/</link>
		<comments>http://www.appslawblog.com/lawsuit-facebook-beacon-complicate/#comments</comments>
		<pubDate>Tue, 27 Oct 2009 04:26:32 +0000</pubDate>
		<dc:creator>Eric Seidmon</dc:creator>
				<category><![CDATA[Facebook]]></category>
		<category><![CDATA[18 USC 2710]]></category>
		<category><![CDATA[apps]]></category>
		<category><![CDATA[Beacon]]></category>
		<category><![CDATA[California]]></category>
		<category><![CDATA[lawsuits]]></category>
		<category><![CDATA[Marketing]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[social networking]]></category>
		<category><![CDATA[Texas]]></category>
		<category><![CDATA[Video Privacy Protection Act]]></category>

		<guid isPermaLink="false">http://www.appslawblog.com/?p=254</guid>
		<description><![CDATA[In what has been developing into a cautionary tale of when good apps go bad, potential class-action settlements in California and Texas surrounding Facebook's Beacon ad program may substantially affect one another. The outcomes in California and Texas jurisdictions will also play a role in other cases involving Beacon, Blockbuster, and Facebook. ]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.facebook.com/index.php?lh=7d6fc40f1cd24235a283a18d20f1e52d&amp;"><img src="http://latimesblogs.latimes.com/.a/6a00d8341c630a53ef0120a5e17e8a970c-800wi" alt="" width="189" height="68" align="right" /></a>In what has been developing into a cautionary tale of when good apps go bad, potential class-action settlements in California and Texas surrounding Facebook&#8217;s <a href="http://en.wikipedia.org/wiki/Facebook_Beacon" target="_blank">Beacon ad program</a> may substantially affect one another.</p>
<p><a href="http://www.facebook.com/">Facebook</a> generates revenue through <a href="http://www.facebook.com/advertising/">advertising</a> and apps.  The Beacon ad program began with a promising future, but took several bad turns.  To put it simply, the Beacon ad program essentially told Facebook members about their friends&#8217; e-commerce activity.</p>
<p>However, a unexpected problem came to light; the program also tracked non-Facebook users. <a href="http://www.pcworld.com/article/140247/facebooks_beacon_ad_system_also_tracks_nonfacebook_users.html">PC World</a> reported that Beacon kept tabs on activities of all users in third-party partner sites, including people who never signed up for Facebook or who deactivated their Facebook accounts.  That information included the addresses of Web pages a user visited and information on action taken at the partner site. As a result, the privacy concerns that plagued Beacon from the first day turned into lawsuits.</p>
<p><span>In California, preliminary approval has been given to Facebook&#8217;s <a href="http://www.computerworld.com/s/article/9138271/Facebook_will_shut_down_Beacon_to_settle_lawsuit" target="_self">settlement</a> of a class-action lawsuit regarding Beacon. But the resolution of the other legal actions is more complicated.  Some consumers who are pursuing two other Beacon-related lawsuits in <a href="http://www.mediapost.com/publications/?fa=Articles.showArticle&amp;art_aid=115279" target="_blank">Texas</a> attempted to intervene in the case, but a federal magistrate rejected their effort. The magistrate ruled that the motion to intervene was filed over a year after the lawsuit was initially brought, </span><span>and therefore was untimely.</span></p>
<p>Some consumers in Texas are attempting to pursue their own class-action lawsuits against Facebook and <a href="http://www.blockbuster.com/">Blockbuster</a> (a large participant in the Beacon ad program).  However, if the California settlement is approved, the Texas lawsuits may be dismissed even though the Texas lawsuit against Blockbuster was filed before the California case.</p>
<p><a href="http://www.mediapost.com/publications/?fa=Articles.showArticle&amp;art_aid=116053">MediaPost</a> reports:</p>
<p style="padding-left: 30px;"><em><span>&#8220;The Califo</span></em><em><span>rnia agreement, entered into last month, calls for Facebook to shutter Beacon permanently and to pay $9.5 million, approximately two-thirds of which will fund a new privacy foundation. The individual consumers named in the complaint would receive damages ranging from $1,000 to $15,000, and their lawyers would be eligible to receive up to one-third of the settlement fund.&#8221;</span></em></p>
<p>Conversely, Texas consumers might be entitled to at least $2,500 each if their lawsuit proceeds.  A federal law (<a href="http://en.wikipedia.org/wiki/Video_Privacy_Protection_Act">Video Privacy Protection Act</a>, <a href="http://www.law.cornell.edu/uscode/18/usc_sec_18_00002710----000-.html">18 U.S.C. § 2710</a>) aimed specifically at protecting the confidentiality of movie rental records provides for up to $2,500 in damages.  Moreover, although Blockbuster&#8217;s contract with users calls for disputes to be heard by an arbitrator, a federal judge in Dallas ruled that the case could proceed in court.  The judge also ruled that because the agreement in Blockbuster&#8217;s contract allowed for the company to change the terms and conditions at any time, it was an &#8220;illusory&#8221; contract. Blockbuster now has a pending appeal in the Fifth Circuit Court of Appeals.  Additionally, those Blockbuster customers in Texas have also filed a lawsuit against Facebook.</p>
<p>The outcomes in California and Texas jurisdictions will also play a role in other cases involving Beacon, Blockbuster, and Facebook.   The judge in the California case could grant final approval to the settlement but he also told the lawyers to address whether the final agreement should cover Facebook members who might have claims under the Video Privacy Protection Act.</p>
Similar Posts:<ul><li>None Found</li></ul>]]></content:encoded>
			<wfw:commentRss>http://www.appslawblog.com/lawsuit-facebook-beacon-complicate/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Google Voice appeared to have security concern</title>
		<link>http://www.appslawblog.com/google-voice-appeared-to-have-security-concern/</link>
		<comments>http://www.appslawblog.com/google-voice-appeared-to-have-security-concern/#comments</comments>
		<pubDate>Fri, 23 Oct 2009 14:05:53 +0000</pubDate>
		<dc:creator>Eric Seidmon</dc:creator>
				<category><![CDATA[iPhone]]></category>
		<category><![CDATA[apps]]></category>
		<category><![CDATA[Google]]></category>
		<category><![CDATA[Google Voice]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[voicemail]]></category>

		<guid isPermaLink="false">http://www.appslawblog.com/?p=226</guid>
		<description><![CDATA[Google's new and innovative app, Google Voice, could create unanticipated security risks. What happens if names and phone numbers leak into the Internet?]]></description>
			<content:encoded><![CDATA[<p><a href="https://www.google.com/accounts/ServiceLogin?passive=true&amp;service=grandcentral&amp;ltmpl=bluebar&amp;continue=https%3A%2F%2Fwww.google.com%2Fvoice%2Faccount%2Fsignin%2F%3Fprev%3D%252F&amp;gsessionid=KtorGoUNRpISXFT_K_MbiA"><img src="https://www.google.com/accounts/grandcentral/icon_01.gif" alt="" width="158" height="49" align="right"/></a>Recently, it seemed as though the <a href="https://www.google.com/accounts/ServiceLogin?passive=true&amp;service=grandcentral&amp;ltmpl=bluebar&amp;continue=https%3A%2F%2Fwww.google.com%2Fvoice%2Faccount%2Fsignin%2F%3Fprev%3D%252F&amp;gsessionid=j8NuN8MJYb2yqKRt6ng4SA">Google Voice</a> app might have had a major security issue that could have resulted in a great privacy concern;  if it was not corrected, prying ears might have created legal issues.  According to <a href="http://www.boygeniusreport.com/2009/10/19/random-users-google-voice-mail-is-searchable-by-anyone/">The Boy Genius Report</a>, one of its readers claims that if you type “site:https://www.google.com/voice/fm/* ” into <a href="www.google.com">Google</a>, up pop voice messages that belong to random Google Voice accounts.</p>
<p>The messages include traditional voice messages as well as Google Voice&#8217;s innovative new feature, transcribed voice messages.  What was most worrisome for Google was the inadvertent invasion of privacy, in which  callers&#8217; phone numbers and names are listed.</p>
<p>However, <a href="http://www.i4u.com/article27710.html">i4u.com</a> reported that there was a possibility that the files were nothing more than promotional or test recordings done by Google.  If that were true, it still begs the question: why would these  recordings be hidden unless of course they weren&#8217;t promotional or test recordings at all?</p>
<p><a href="http://www.boygeniusreport.com/2009/10/19/random-users-google-voice-mail-is-searchable-by-anyone/">The Boy Genius Report</a> has reportedly received information that could clear up any confusion Google had created:</p>
<p style="text-align: left; padding-left: 30px;"><em>&#8220;UPDATE: It seems as if these voicemails have been publicly posted/shared online and Google indexes them. Here’s official word:</em></p>
<p style="text-align: left; padding-left: 30px;"><em>&#8216;Since the initial idea behind posting a voicemail, was precisely to share it with others, we did not restrict crawling of those messages that users post on the web, but we can certainly understand that users would want to make them public on their sites but not necessarily searchable directly outside of their own website. We made a change to prevent those to be crawled so only the site owner can decide to index them.&#8217;&#8221;</em></p>
<p style="text-align: left;"><a href="http://www.techcrunch.com/2009/10/19/the-best-of-the-google-voice-public-messages/">Techcrunch.com</a> claims that as a result, Google has decided to change its policy and no longer indexes the voice messages.</p>
Similar Posts:<ul><li>None Found</li></ul>]]></content:encoded>
			<wfw:commentRss>http://www.appslawblog.com/google-voice-appeared-to-have-security-concern/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
