<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: What Happens in Vegas Stays on Facebook</title>
	<atom:link href="http://jessicarandazza.com/social-media/facebookprivac/feed/" rel="self" type="application/rss+xml" />
	<link>http://jessicarandazza.com/social-media/facebookprivac/</link>
	<description>A PR Girl Trying To Change The World</description>
	<lastBuildDate>Wed, 01 Sep 2010 22:13:05 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Being Always &#8220;On&#8221; &#171; JessicaRandazza</title>
		<link>http://jessicarandazza.com/social-media/facebookprivac/comment-page-1/#comment-695</link>
		<dc:creator>Being Always &#8220;On&#8221; &#171; JessicaRandazza</dc:creator>
		<pubDate>Thu, 25 Feb 2010 05:25:32 +0000</pubDate>
		<guid isPermaLink="false">http://jessicarandazza.com/?p=94#comment-695</guid>
		<description>[...] Believe me, I&#8217;ve been there, and I&#8217;ve untagged a fair amount of photographs in my day. As I mentioned before, I even once deleted my entire Facebook account and started over just so I wouldn&#8217;t have to [...]</description>
		<content:encoded><![CDATA[<p>[...] Believe me, I&#8217;ve been there, and I&#8217;ve untagged a fair amount of photographs in my day. As I mentioned before, I even once deleted my entire Facebook account and started over just so I wouldn&#8217;t have to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Viranda</title>
		<link>http://jessicarandazza.com/social-media/facebookprivac/comment-page-1/#comment-43</link>
		<dc:creator>Viranda</dc:creator>
		<pubDate>Thu, 24 Sep 2009 00:31:54 +0000</pubDate>
		<guid isPermaLink="false">http://jessicarandazza.com/?p=94#comment-43</guid>
		<description>Jessica - Great post and I&#039;m on the same page in regards to a lot you&#039;ve mentioned. I think you need not be afraid of who you are - that said, a bit of privacy tweaking on FB can go a long way. Commenter above - great writeup as well...</description>
		<content:encoded><![CDATA[<p>Jessica &#8211; Great post and I&#8217;m on the same page in regards to a lot you&#8217;ve mentioned. I think you need not be afraid of who you are &#8211; that said, a bit of privacy tweaking on FB can go a long way. Commenter above &#8211; great writeup as well&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sarah Evans</title>
		<link>http://jessicarandazza.com/social-media/facebookprivac/comment-page-1/#comment-42</link>
		<dc:creator>Sarah Evans</dc:creator>
		<pubDate>Wed, 23 Sep 2009 17:29:36 +0000</pubDate>
		<guid isPermaLink="false">http://jessicarandazza.com/?p=94#comment-42</guid>
		<description>Jessica, Thank you for this honest look into your growth with a public profile. So many of us are learning daily the ups and downs of an online presence. I know that you are not alone in this quest to find the right balance of personal and professional.</description>
		<content:encoded><![CDATA[<p>Jessica, Thank you for this honest look into your growth with a public profile. So many of us are learning daily the ups and downs of an online presence. I know that you are not alone in this quest to find the right balance of personal and professional.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: C. Patel</title>
		<link>http://jessicarandazza.com/social-media/facebookprivac/comment-page-1/#comment-41</link>
		<dc:creator>C. Patel</dc:creator>
		<pubDate>Wed, 23 Sep 2009 16:38:17 +0000</pubDate>
		<guid isPermaLink="false">http://jessicarandazza.com/?p=94#comment-41</guid>
		<description>It has become common practice to look at the facebook, twitter, other social accounts of applicants during hiring, especially in those professions where the position requires the applicant to be sort of a &quot;public agent&quot; for the hiring company.  More simply -- A job where you have a real opportunity to make them look bad.

While most of us accept this practice as a qualification for employment, others (mostly those denied position because of the content on their sites) have challenged the validity of these practices under the Consumer Reporting Act. The federal Act was amended in 1998 by the &quot;Consumer Reporting Employment Clarification Act of 1998.&quot;  The legislature, recognizing the essential &quot;make-or-break&quot; function that a background check can play in gaining employment, wanted to make sure that REASONABLE PROCEDURES were used to create these reports.

The law was created most likely to deal with use of urinalysis, credit, and criminal history  for the purposes of qualification for employment.  The conventions of the internet and social networking sites were not likely contemplated, and the broad language of the Act has left interpretation of legislative intent to the Courts. 

The case law, however, indicates a very deferential standard, and as mentioned earlier, the reporting agency need only use REASONABLE PROCEDURES, the specific report need not be accurate. For example, in one case a credit reporting agency accidentally reported the bankruptcy of another person with the same name as the applicant.  The court held that even though the report was inaccurate, the Agency&#039;s procedures for collecting and reporting generally accurate, and was not held liable. 

Is looking at Facebook or Twitter an ACCURATE PROCESS? Further, even though the owner of the site posts the information, is it 3rd party information because it&#039;s collected from a website and not the person directly? -- There are different standards of liability if it is. Facebook and Twitter are account based, is this information private and therefore should not be subject of a background check?

These are some of the questions that the court&#039;s are dealing with, but it seems that most will allow the use of such information in background checks.  Again, I want to reiterate the test is whether the procedure was accurate, and not whether the report that is subject of litigation is correct.  So what if the report was wrong, collected partial information, or was the account of a completely different person? -- Even if a court holds that the procedures used are were unreasonable, damages are limited. 

Most courts have held that the act does not afford injunctive relief (the Act is silent).  So basically, even if the report was wrong, the court can&#039;t force the employer to hire you. (I&#039;m not sure if you would want want to work for someone you sued anyway).  Legal damages are also limited and you probably won&#039;t be able to get lost salary.  

In the end, most judges realize that importance of professionalism and will probably find that looking at your accounts is a reasonable procedure. In the end, you have no one to blame but yourself; you allowed that information to be posted, and you should know by now people will be looking at it.  Good Luck. 

&lt;i&gt;Consumer Reporting Act&lt;/i&gt;, 16 U.S.C. 1861 et seq. 
&lt;i&gt;Salazar v. Golden State Warriors&lt;/i&gt;, F.Supp.2d 1155 (N.D. Cal. 2000) (allowing the use of videotape surveillance without consent for grounds for firing).
&lt;i&gt;Sarver v. Experian Information Solutions&lt;/i&gt;, 390 F.3d 969, 971 (7th Cir. 2004)(reasonable procedures in credit reporting). 
&lt;i&gt; Owner-Operator Indep. Drivers Ass’n v. USIS Commercial Servs., Inc.&lt;/i&gt;, 537 F.3d 1184, 1193 (10th Cir. 2008)(&quot;Industry standards&quot; are admissible to show a process was reasonable).
&lt;i&gt;Washington v. CSC Credit Svcs.&lt;/i&gt;, 199 F. 3d 263, 268 (5th Cir.)(no injunctive relief under the Act).
16 C.F.R. Appendix, Part 600, at 516 (2009)(transactions and experiences exception explained).</description>
		<content:encoded><![CDATA[<p>It has become common practice to look at the facebook, twitter, other social accounts of applicants during hiring, especially in those professions where the position requires the applicant to be sort of a &#8220;public agent&#8221; for the hiring company.  More simply &#8212; A job where you have a real opportunity to make them look bad.</p>
<p>While most of us accept this practice as a qualification for employment, others (mostly those denied position because of the content on their sites) have challenged the validity of these practices under the Consumer Reporting Act. The federal Act was amended in 1998 by the &#8220;Consumer Reporting Employment Clarification Act of 1998.&#8221;  The legislature, recognizing the essential &#8220;make-or-break&#8221; function that a background check can play in gaining employment, wanted to make sure that REASONABLE PROCEDURES were used to create these reports.</p>
<p>The law was created most likely to deal with use of urinalysis, credit, and criminal history  for the purposes of qualification for employment.  The conventions of the internet and social networking sites were not likely contemplated, and the broad language of the Act has left interpretation of legislative intent to the Courts. </p>
<p>The case law, however, indicates a very deferential standard, and as mentioned earlier, the reporting agency need only use REASONABLE PROCEDURES, the specific report need not be accurate. For example, in one case a credit reporting agency accidentally reported the bankruptcy of another person with the same name as the applicant.  The court held that even though the report was inaccurate, the Agency&#8217;s procedures for collecting and reporting generally accurate, and was not held liable. </p>
<p>Is looking at Facebook or Twitter an ACCURATE PROCESS? Further, even though the owner of the site posts the information, is it 3rd party information because it&#8217;s collected from a website and not the person directly? &#8212; There are different standards of liability if it is. Facebook and Twitter are account based, is this information private and therefore should not be subject of a background check?</p>
<p>These are some of the questions that the court&#8217;s are dealing with, but it seems that most will allow the use of such information in background checks.  Again, I want to reiterate the test is whether the procedure was accurate, and not whether the report that is subject of litigation is correct.  So what if the report was wrong, collected partial information, or was the account of a completely different person? &#8212; Even if a court holds that the procedures used are were unreasonable, damages are limited. </p>
<p>Most courts have held that the act does not afford injunctive relief (the Act is silent).  So basically, even if the report was wrong, the court can&#8217;t force the employer to hire you. (I&#8217;m not sure if you would want want to work for someone you sued anyway).  Legal damages are also limited and you probably won&#8217;t be able to get lost salary.  </p>
<p>In the end, most judges realize that importance of professionalism and will probably find that looking at your accounts is a reasonable procedure. In the end, you have no one to blame but yourself; you allowed that information to be posted, and you should know by now people will be looking at it.  Good Luck. </p>
<p><i>Consumer Reporting Act</i>, 16 U.S.C. 1861 et seq.<br />
<i>Salazar v. Golden State Warriors</i>, F.Supp.2d 1155 (N.D. Cal. 2000) (allowing the use of videotape surveillance without consent for grounds for firing).<br />
<i>Sarver v. Experian Information Solutions</i>, 390 F.3d 969, 971 (7th Cir. 2004)(reasonable procedures in credit reporting).<br />
<i> Owner-Operator Indep. Drivers Ass’n v. USIS Commercial Servs., Inc.</i>, 537 F.3d 1184, 1193 (10th Cir. 2008)(&#8220;Industry standards&#8221; are admissible to show a process was reasonable).<br />
<i>Washington v. CSC Credit Svcs.</i>, 199 F. 3d 263, 268 (5th Cir.)(no injunctive relief under the Act).<br />
16 C.F.R. Appendix, Part 600, at 516 (2009)(transactions and experiences exception explained).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
