<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.lexblog.com/~d/styles/itemcontent.css"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">
   <channel>
      <title>Ad Law Access</title>
      <link>http://www.adlawaccess.com/</link>
      <description />
      <language>en</language>
      <copyright>Copyright 2013</copyright>
      <lastBuildDate>Mon, 17 Jun 2013 13:14:48 -0500</lastBuildDate>
      <pubDate>Mon, 17 Jun 2013 13:14:48 -0500</pubDate>
      <generator>http://www.movabletype.org</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 

            <feedburner:info uri="adlawaccess" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://www.adlawaccess.com/index.xml" /><feedburner:feedFlare href="http://add.my.yahoo.com/rss?url=http%3A%2F%2Fwww.adlawaccess.com%2Findex.xml" src="http://us.i1.yimg.com/us.yimg.com/i/us/my/addtomyyahoo4.gif">Subscribe with My Yahoo!</feedburner:feedFlare><feedburner:feedFlare href="http://www.newsgator.com/ngs/subscriber/subext.aspx?url=http%3A%2F%2Fwww.adlawaccess.com%2Findex.xml" src="http://www.newsgator.com/images/ngsub1.gif">Subscribe with NewsGator</feedburner:feedFlare><feedburner:feedFlare href="http://feeds.my.aol.com/add.jsp?url=http%3A%2F%2Fwww.adlawaccess.com%2Findex.xml" src="http://o.aolcdn.com/favorites.my.aol.com/webmaster/ffclient/webroot/locale/en-US/images/myAOLButtonSmall.gif">Subscribe with My AOL</feedburner:feedFlare><feedburner:feedFlare href="http://www.bloglines.com/sub/http://www.adlawaccess.com/index.xml" src="http://www.bloglines.com/images/sub_modern11.gif">Subscribe with Bloglines</feedburner:feedFlare><feedburner:feedFlare href="http://www.netvibes.com/subscribe.php?url=http%3A%2F%2Fwww.adlawaccess.com%2Findex.xml" src="http://www.netvibes.com/img/add2netvibes.gif">Subscribe with Netvibes</feedburner:feedFlare><feedburner:feedFlare href="http://fusion.google.com/add?feedurl=http%3A%2F%2Fwww.adlawaccess.com%2Findex.xml" src="http://buttons.googlesyndication.com/fusion/add.gif">Subscribe with Google</feedburner:feedFlare><feedburner:feedFlare href="http://www.pageflakes.com/subscribe.aspx?url=http%3A%2F%2Fwww.adlawaccess.com%2Findex.xml" src="http://www.pageflakes.com/ImageFile.ashx?instanceId=Static_4&amp;fileName=ATP_blu_91x17.gif">Subscribe with Pageflakes</feedburner:feedFlare><item>
         <title>Jessica Rich Named Director of the FTC's Bureau of Consumer Protection</title>
         <description>&lt;p&gt;Today, Federal Trade Commission (&amp;ldquo;FTC&amp;rdquo;) Chairwoman Edith Ramirez announced that Jessica Rich has been named Director of the FTC&amp;rsquo;s Bureau of Consumer Protection (the &amp;ldquo;Bureau&amp;rdquo;).  Rich, who has more than 22 years of experience at the Commission, currently serves as Associate Director in the Bureau&amp;rsquo;s Division of Financial Practices. She will take over the Bureau Director role from Acting Bureau Director Charles Harwood, who will return to his previous position as Deputy Bureau Director.&lt;/p&gt;
&lt;p&gt;As Bureau Director, it is expected that Rich will continue to focus the Commission&amp;rsquo;s efforts on addressing a number of key emerging technology issues, including consumers&amp;rsquo; increased use of the mobile Internet, expanding consumer data collection by businesses, and privacy issues relating to the growing interconnection between everyday consumer devices.&lt;/p&gt;
&lt;p&gt;For additional background about Rich, please see the &lt;a href="http://www.kelleydrye.com/publications/client_advisories/0821"&gt;Kelley Drye client advisory&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;On June 27, Kelley Drye &amp;amp; Warren will convene top government policy-makers from the FTC and CPSC, industry thought-leaders, and marketing law specialists at the &lt;a href="http://www.kelleydrye.com/events/seminars/0187"&gt;Advertising and Privacy Law Summit&lt;/a&gt; in Washington, D.C. This full-day seminar will look ahead to priorities for the new Director of the FTC&amp;rsquo;s Bureau of Consumer Protection. To inquire about attendance at this invitation-only event, please email &lt;a href="javascript:location.href='mailto:'+String.fromCharCode(100,99,101,118,101,110,116,115,64,107,101,108,108,101,121,100,114,121,101,46,99,111,109)+'?subject=Summit%20Attendance%20Inquiry'"&gt;dcevents@kelleydrye.com&lt;/a&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AdLawAccess/~4/bSBh7x2BEO4" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AdLawAccess/~3/bSBh7x2BEO4/</link>
         <guid isPermaLink="false">http://www.adlawaccess.com/2013/06/articles/federal-trade-commission/jessica-rich-named-director-of-the-ftcs-bureau-of-consumer-protection/</guid>
         <category domain="http://www.adlawaccess.com/articles">Federal Trade Commission</category>
         <pubDate>Mon, 17 Jun 2013 12:55:23 -0500</pubDate>
         <dc:creator>Dana B. Rosenfeld</dc:creator>
      
      <feedburner:origLink>http://www.adlawaccess.com/2013/06/articles/federal-trade-commission/jessica-rich-named-director-of-the-ftcs-bureau-of-consumer-protection/</feedburner:origLink></item>
            <item>
         <title>New York Times Article Discusses Potential Liability for Celebrity Endorsements</title>
         <description>&lt;p&gt;A recent &lt;a href="http://bits.blogs.nytimes.com/2013/06/09/disruptions-celebrities-product-plugs-on-social-media-draw-scrutiny/"&gt;New York Times article&lt;/a&gt; discussed the FTC&amp;rsquo;s scrutiny of companies who engage celebrities to endorse their products in social media. The article serves as a timely reminder that this form of advertising, unless conducted carefully, can result in liability and monetary penalties for the celebrity and the advertiser.&lt;/p&gt;
&lt;p&gt;The FTC is concerned that consumers will believe these celebrity endorsements aren&amp;rsquo;t ads and that the celebrities haven&amp;rsquo;t been compensated in exchange. &amp;ldquo;In a traditional ad with a celebrity, everyone assumes that they are being paid,&amp;rdquo; according to Mary K. Engle, associate director of the advertising practices division at the FTC. &amp;ldquo;When it&amp;rsquo;s not obvious that it is an ad, people should disclose that they are being paid.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;&lt;a href="http://www.adlawaccess.com/2013/03/articles/advertising-1/ftc-updates-com-disclosures-guide-to-address-mobile-viewing-and-spaceconstrained-ads/"&gt;As we noted in March&lt;/a&gt;, the FTC&amp;rsquo;s updated &amp;ldquo;.com Disclosures&amp;rdquo; guides provide some &amp;ldquo;does and don&amp;rsquo;ts&amp;rdquo; for this form of advertising. Notwithstanding the typically short length of these postings, the guides provide that celebrity endorsements in social media must contain clear and conspicuous language indicating that the endorsements are sponsored. While the .com Disclosures are not law, they do highlight the FTC&amp;rsquo;s thinking on what federal law requires with this form of advertising.&lt;/p&gt;
&lt;p&gt;Celebrities and companies who engage in this form of advertising would be wise to understand the .com Disclosures and related laws &amp;mdash; or to consult with legal counsel who does &amp;mdash; so that they can avoid legal liability and reap the benefits that can come with this form of advertising.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Special Counsel &lt;/em&gt;&lt;a href="http://www.kelleydrye.com/attorneys/joseph_wilson"&gt;&lt;em&gt;Joe Wilson&lt;/em&gt;&lt;/a&gt;&lt;em&gt; contributed to this post.&lt;/em&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AdLawAccess/~4/GIOOalp2F0Q" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AdLawAccess/~3/GIOOalp2F0Q/</link>
         <guid isPermaLink="false">http://www.adlawaccess.com/2013/06/articles/advertising-1/new-york-times-article-discusses-potential-liability-for-celebrity-endorsements/</guid>
         <category domain="http://www.adlawaccess.com/articles">Advertising</category><category domain="http://www.adlawaccess.com/articles">Federal Trade Commission</category><category domain="http://www.adlawaccess.com/articles">Social Media</category>
         <pubDate>Thu, 13 Jun 2013 07:29:24 -0500</pubDate>
         <dc:creator>Gonzalo E. Mon</dc:creator>
      
      <feedburner:origLink>http://www.adlawaccess.com/2013/06/articles/advertising-1/new-york-times-article-discusses-potential-liability-for-celebrity-endorsements/</feedburner:origLink></item>
            <item>
         <title>Supreme Court To Clarify Standing For False Advertising</title>
         <description>&lt;p&gt;On June 3, 2013, the &lt;a href="http://www.supremecourt.gov/qp/12-00873qp.pdf"&gt;U.S. Supreme Court agreed to hear&lt;/a&gt; Lexmark International&amp;rsquo;s petition from a lower court ruling that a party with merely a &amp;ldquo;reasonable interest&amp;rdquo; to protect had standing to sue for false advertising under Section 43(a) of the Lanham Act, 15 U.S.C. &amp;sect; 1125(a)(1).  The counterclaiming party, Static Controls, alleged that Lexmark engaged in false advertising by informing customers that Static infringed various patents and copyrights.  Lexmark and Static are not actual competitors.&lt;/p&gt;
&lt;p&gt;The Supreme Court will decide the appropriate test for standing in these circumstances, which has divided the lower courts.  In some Circuits only actual competitors have standing to sue for false advertising under the Lanham Act, whereas other Circuits apply a multi-factor test typically used for antitrust claims.  Here, the Sixth Circuit applied a&lt;a href="http://www.ca6.uscourts.gov/opinions.pdf/12a0289p-06.pdf"&gt; more lenient &amp;ldquo;reasonable interest&amp;rdquo; test&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The Supreme Court&amp;rsquo;s forthcoming decision (not likely before late 2013 or early 2014) creates potential opportunities for false advertising plaintiffs if the Court adopts a more lenient standard, and potentially greater protection against false advertising claims nationwide if the Court adopts a more stringent standing requirement applicable to all Circuits.  In all events, Static&amp;rsquo;s counterclaims are a reminder that what is said about a lawsuit by a party outside of court&amp;mdash;to customers and others&amp;mdash;may give rise to potential liability, or at least the headache of defending against accusations of wrongdoing.       &lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AdLawAccess/~4/evGufXl76YU" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AdLawAccess/~3/evGufXl76YU/</link>
         <guid isPermaLink="false">http://www.adlawaccess.com/2013/06/articles/advertising-litigation/supreme-court-to-clarify-standing-for-false-advertising/</guid>
         <category domain="http://www.adlawaccess.com/articles">Advertising Litigation</category>
         <pubDate>Wed, 12 Jun 2013 13:00:47 -0500</pubDate>
         <dc:creator>Paul R. Garcia</dc:creator>
      
      <feedburner:origLink>http://www.adlawaccess.com/2013/06/articles/advertising-litigation/supreme-court-to-clarify-standing-for-false-advertising/</feedburner:origLink></item>
            <item>
         <title>FTC Updates COPPA FAQs in Advance of July 1 Rule Changes</title>
         <description>&lt;p&gt;This week, the Federal Trade Commission announced the latest update to its&lt;a href="http://business.ftc.gov/documents/Complying-with-COPPA-Frequently-Asked-Questions"&gt; frequently asked questions&lt;/a&gt; (&amp;ldquo;FAQs&amp;rdquo;) document to assist online operators as they prepare for changes to the Children&amp;rsquo;s Online Privacy Protection (&amp;ldquo;COPPA&amp;rdquo;) Rule, which go into effect on July 1, 2013.  The updated FAQs address the parental notice and consent obligations for operators that feature a Facebook &amp;ldquo;Like&amp;rdquo; button on their site.  The new question and answer (&lt;em&gt;see&lt;/em&gt; FAQ I.10) read as follows:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;10.  I have a child-directed website.  Can I put the Facebook Like button on my site without providing notice and obtaining verifiable parental consent?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Section 312.5(c)(8) of the Rule has an exception to its notice and consent requirements where:  &lt;br /&gt;
&amp;bull;	a third-party operator only collects a persistent identifier and no other personal information; &lt;br /&gt;
&amp;bull;	the user affirmatively interacts with that third-party operator to trigger the collection; and &lt;br /&gt;
&amp;bull;	the third-party operator has previously conducted an age-screen of the user, indicating the user is not a child.  &lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;em&gt;If the third-party operator meets all of those requirements, and if your site doesn't collect personal information (except for that covered by an exception), you don't need to provide notice or obtain consent.  This exception doesn't apply where the third party collects more information than a persistent identifier &amp;mdash;  for example, where the third party also collects user comments or other user-generated content.  In addition, a child-directed website can't rely on this exception to treat particular visitors as adults and track their activities.  If your inclusion of the Facebook Like button satisfies all these criteria, you may rely on this exception under the Rule.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;The new Q&amp;amp;A is the latest effort by FTC Staff (also see &lt;a href="http://www.adlawaccess.com/2013/05/articles/privacy-and-information-securi/ftc-issues-latest-update-to-coppa-faqs/"&gt;here&lt;/a&gt;, &lt;a href="http://www.adlawaccess.com/2013/05/articles/privacy-and-information-securi/ftc-reaches-out-to-businesses-on-coppa/"&gt;here&lt;/a&gt;, and &lt;a href="http://www.adlawaccess.com/2013/04/articles/privacy-and-information-securi/ftc-issues-updated-coppa-faqs/"&gt;here&lt;/a&gt;) to educate operators of websites and online services directed to children about their obligations under the amended Rule. &lt;br /&gt;
&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AdLawAccess/~4/Nl2B69YPeXM" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AdLawAccess/~3/Nl2B69YPeXM/</link>
         <guid isPermaLink="false">http://www.adlawaccess.com/2013/06/articles/privacy-and-information-securi/ftc-updates-coppa-faqs-in-advance-of-july-1-rule-changes/</guid>
         <category domain="http://www.adlawaccess.com/articles">Privacy and Information Security</category>
         <pubDate>Thu, 06 Jun 2013 10:31:28 -0500</pubDate>
         <dc:creator>Matthew Sullivan</dc:creator>
      
      <feedburner:origLink>http://www.adlawaccess.com/2013/06/articles/privacy-and-information-securi/ftc-updates-coppa-faqs-in-advance-of-july-1-rule-changes/</feedburner:origLink></item>
            <item>
         <title>Ohio Lawsuit Alleges Deceptive Advertising by Jos. A. Bank</title>
         <description>&lt;p&gt;On May 24, 2013, Ohio consumers filed a class action lawsuit in U.S. District Court (N.D. Ohio) alleging that advertising by clothing retailer Jos. A. Bank violates the &lt;a href="http://codes.ohio.gov/orc/1345"&gt;Ohio Consumer Sales Practices Act&lt;/a&gt; (&amp;ldquo;CSPA&amp;rdquo;) and state sale price statutes.  &lt;em&gt;See&lt;/em&gt; Schneider v. Jos. A. Bank Clothiers, Inc., No. 1:13-cv-01175-SL (N.D. Ohio Filed on May 24, 2013).&amp;nbsp;  According to the Complaint, Jos. A. Bank&amp;rsquo;s television, radio, print, and online advertising falsely promotes substantial savings (including &amp;ldquo;free&amp;rdquo; offers) on men&amp;rsquo;s suits, sportcoats, and dress pants by basing the advertised &amp;ldquo;discount&amp;rdquo; prices on grossly inflated and illusory &amp;ldquo;regular prices&amp;rdquo; that do not represent the prices at which any of the clothing items are sold.&lt;/p&gt;
&lt;p&gt;As one purported example of Jos. A. Bank&amp;rsquo;s alleged illegal conduct, the Complaint describes an instance where an Ohio consumer purchased a suit for &amp;ldquo;70% Off&amp;rdquo; of the advertised regular price of $895.&amp;nbsp;  The Plaintiffs allege that the $895 &amp;ldquo;regular price&amp;rdquo; does not reflect the actual price regularly paid by consumers for the applicable suit, and that the suit is substantially inferior in value to the advertised regular price.&amp;nbsp;  Ohio law defines a &amp;ldquo;regular price&amp;rdquo; as &amp;ldquo;the price at which the goods or services are openly and actively sold by a supplier to the public on a continuing basis for a substantial period of time.&amp;rdquo;&amp;nbsp; In addition, the Complaint asserts that Jos. A Bank&amp;rsquo;s claims that its sales are for a &amp;ldquo;limited time,&amp;rdquo; &amp;ldquo;today only,&amp;rdquo; or similar terms, are false and deceptive because the company maintains its sales offers on a nearly continuous basis.&lt;/p&gt;
&lt;p&gt;The lawsuit claims that Jos. A Bank&amp;rsquo;s conduct violates Ohio Administrative Code section &lt;a href="http://codes.ohio.gov/oac/109:4-3-04"&gt;109:4-3-04&lt;/a&gt;, which imposes certain requirements when making &amp;ldquo;free&amp;rdquo; promotional offers, and section &lt;a href="http://codes.ohio.gov/oac/109:4-3-12"&gt;109:4-3-12&lt;/a&gt;, which prohibits an advertiser from using certain terms (e.g., &amp;ldquo;regularly. . .&amp;rdquo;, &amp;ldquo;now. . .;&amp;rdquo; &amp;ldquo;reduced from. . . to . . .,&amp;rdquo;) unless the comparison is to the advertiser&amp;rsquo;s legitimate regular price.  &lt;br /&gt;
&lt;br /&gt;
The plaintiffs are seeking compensatory damages that are based on the difference between the allegedly inflated &amp;ldquo;regular price&amp;rdquo; that each class member paid for a clothing item, and the &amp;ldquo;true&amp;rdquo; lower regular price for each such item. &lt;br /&gt;
&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AdLawAccess/~4/yUCQrAXH-wE" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AdLawAccess/~3/yUCQrAXH-wE/</link>
         <guid isPermaLink="false">http://www.adlawaccess.com/2013/06/articles/advertising-litigation/ohio-lawsuit-alleges-deceptive-advertising-by-jos-a-bank/</guid>
         <category domain="http://www.adlawaccess.com/articles">Advertising Litigation</category>
         <pubDate>Wed, 05 Jun 2013 09:53:48 -0500</pubDate>
         <dc:creator>Matthew Sullivan</dc:creator>
      
      <feedburner:origLink>http://www.adlawaccess.com/2013/06/articles/advertising-litigation/ohio-lawsuit-alleges-deceptive-advertising-by-jos-a-bank/</feedburner:origLink></item>
            <item>
         <title>Eleventh Circuit Rules Best Buy's ID Swipe Policy Does Not Violate Federal Privacy Law</title>
         <description>&lt;p&gt;On Tuesday, the Eleventh Circuit ruled that Best Buy&amp;rsquo;s policy of swiping drivers&amp;rsquo; licenses when customers return purchases does not violate the federal Drivers&amp;rsquo; Privacy Protection Act of 1994 (&amp;ldquo;DPPA&amp;rdquo;).  In a &lt;em&gt;per curiam&lt;/em&gt; opinion, the court affirmed the U.S. District Court for the Southern District of Florida&amp;rsquo;s dismissal of the putative nationwide class action and determination that the DPPA does not apply to information supplied by the customer.&lt;/p&gt;
&lt;p&gt;The lawsuit arose in October 2011 when the plaintiff attempted to return a computer mouse at a Best Buy store in Florida.  During that transaction, the store cashier requested the plaintiff&amp;rsquo;s driver&amp;rsquo;s license to complete the return and, when the plaintiff supplied it, scanned the license&amp;rsquo;s magnetic strip.  The plaintiff demanded that Best Buy delete the magnetic strip information, but Best Buy stated it could not.  The plaintiff then filed a complaint against the company, alleging that Best Buy&amp;rsquo;s policy violated the DPPA, which prohibits knowingly obtaining, disclosing, or using personal information, from a motor vehicle record, for an unpermitted purpose.&lt;/p&gt;
&lt;p&gt;The Eleventh Circuit agreed with the District Court that the DPPA was intended to prohibit the disclosure of personal information originating from the state department of motor vehicle records only and not from the driver&amp;rsquo;s license holder.  Thus, the court concluded, the plaintiff had failed to state a claim for which relief could be granted.  The court explained that the DPPA was enacted to prevent state employee access to and disclosure of personal records and regulates disclosure of information by the state and supplied by the state only.&lt;/p&gt;
&lt;p&gt;The court also acknowledged in a footnote that the return policy on the back of the Best Buy receipt that the plaintiff received with his purchase notified him of the company&amp;rsquo;s policy of swiping drivers&amp;rsquo; licenses for returns.  It stated:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;Best Buy tracks exchanges and returns on an individual level.  When you exchange or return an item, we require a valid form of ID&amp;hellip;.  Some of the information from your ID may be stored in a secure, encrypted database of customer activity that Best Buy and its affiliates use to track exchanges and returns.  Valid forms of ID accepted are: U.S., Canadian, or Mexican Driver&amp;rsquo;s License, U.S. State ID, Canadian Province ID, U.S. Military ID or Passport.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Accordingly, the consumer was advised of Best Buy&amp;rsquo;s policy to required IDs for returns and opted to proceed anyway.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Associate &lt;a href="http://www.kelleydrye.com/attorneys/katherine_riley"&gt;Katherine E. Riley&lt;/a&gt; contributed to this post. Ms. Riley is admitted only in Massachusetts. She is practicing under the supervision of principals of the firm who are members of the D.C. Bar.&lt;/em&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AdLawAccess/~4/3hBPj0Repoc" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AdLawAccess/~3/3hBPj0Repoc/</link>
         <guid isPermaLink="false">http://www.adlawaccess.com/2013/05/articles/privacy-and-information-securi/eleventh-circuit-rules-best-buys-id-swipe-policy-does-not-violate-federal-privacy-law/</guid>
         <category domain="http://www.adlawaccess.com/articles">Privacy and Information Security</category>
         <pubDate>Fri, 31 May 2013 16:08:54 -0500</pubDate>
         <dc:creator>Kristi Wolff</dc:creator>
      
      <feedburner:origLink>http://www.adlawaccess.com/2013/05/articles/privacy-and-information-securi/eleventh-circuit-rules-best-buys-id-swipe-policy-does-not-violate-federal-privacy-law/</feedburner:origLink></item>
            <item>
         <title>White House Nominates New CPSC Commissioner and CPSC Adds Director of Compliance and Field Operations</title>
         <description>&lt;p&gt;With a looming departure date for Consumer Product Safety Commission (&amp;quot;CPSC&amp;quot; or &amp;quot;Commission&amp;quot;) Commissioner Nancy Nord that would leave the CPSC without a quorum, the &lt;a href="http://www.whitehouse.gov/the-press-office/2013/05/23/presidential-nominations-sent-senate-0"&gt;Obama Administration announced&lt;/a&gt; last week the nomination of former Rep. Ann Marie Buerkle to serve as a Republican Commissioner. During her single term, Congresswoman Buerkle criticized what she described as an &lt;a href="http://www.buerkleforcongress.com/know-the-facts/issues/energy-and-the-environment/"&gt;unchecked growth of government&lt;/a&gt; that stifled the free enterprise of small businesses. Her nomination will likely be paired with &lt;a href="http://www.adlawaccess.com/2013/01/articles/consumer-product-safety/round-two-president-obama-renominates-marietta-robinson-as-cpsc-commissioner/"&gt;Marietta Robinson's nomination&lt;/a&gt;, President Barack Obama's pick in 2012 to fill the seat left vacant by Democratic Commissioner Thomas Moore.&lt;/p&gt;
&lt;p&gt;In the wake of the White House's nomination, Ray Aragon quietly became the Commission's Director of Compliance and Field Operation. Although the CPSC has not issued a press release announcing the new Director or modified its online organization chart, Mr. Aragon is listed in the CPSC's phone directory and presumably has begun handling matters. Mr. Aragon was most recently a partner at McKenna Long &amp;amp; Aldridge LLP, with a commercial litigation practice that included product liability claims.&lt;/p&gt;
&lt;p&gt;This &lt;a href="http://www.adlawaccess.com/2013/01/articles/consumer-product-safety/round-two-president-obama-renominates-marietta-robinson-as-cpsc-commissioner/"&gt;Kelley Drye advisory&lt;/a&gt; provides background regarding these two individuals and what the new leadership means for the CPSC.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AdLawAccess/~4/M7pWtpA5ss8" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AdLawAccess/~3/M7pWtpA5ss8/</link>
         <guid isPermaLink="false">http://www.adlawaccess.com/2013/05/articles/consumer-product-safety/white-house-nominates-new-cpsc-commissioner-and-cpsc-adds-director-of-compliance-and-field-operations/</guid>
         <category domain="http://www.adlawaccess.com/articles">Consumer Product Safety</category>
         <pubDate>Thu, 30 May 2013 10:40:12 -0500</pubDate>
         <dc:creator>Christie Grymes Thompson</dc:creator>
      
      <feedburner:origLink>http://www.adlawaccess.com/2013/05/articles/consumer-product-safety/white-house-nominates-new-cpsc-commissioner-and-cpsc-adds-director-of-compliance-and-field-operations/</feedburner:origLink></item>
            <item>
         <title>FTC Seeks Public Comment on Proposed Amendments to the Telemarketing Sales Rule</title>
         <description>&lt;p&gt;On May 21, the Federal Trade Commission (&amp;ldquo;FTC&amp;rdquo;) issued a Notice of Proposed Rulemaking (&amp;ldquo;NPRM&amp;rdquo;) regarding proposed amendments to the Telemarketing Sales Rule (&amp;ldquo;TSR&amp;rdquo;).  Notably, the proposed changes would: (1) expressly state that the seller or telemarketer bears the burden of demonstrating an existing business relationship with a customer whose number is listed on the Do Not Call Registry, or that it has obtained an express written agreement from such customer; and (2) clarify that the exemption for calls to businesses extends only to calls inducing sale or contribution from the business, and not to calls inducing sales or contributions from individuals employed by the business.  The Commission believes that these proposed revisions are consistent with current enforcement policy.&lt;br /&gt;
&lt;br /&gt;
In addition, the FTC proposes to amend the Rule to explicitly state the following requirements, which it also believes are consistent with current enforcement policy.  These proposed amendments would:&lt;/p&gt;
&lt;ol&gt;
    &lt;li&gt;Modify the prohibition against sellers sharing the cost of Do Not Call Registry fees to emphasize that the prohibition is absolute;&lt;/li&gt;
    &lt;li&gt;Illustrate the types of impermissible burdens on consumers that deny or interfere with their right to be placed on a seller&amp;rsquo;s or telemarketer&amp;rsquo;s entity-specific do-not-call list (such as requiring the person to listen to a sales pitch before accepting the Do Not Call request or assessing a charge or fee for honoring the request); and&lt;/li&gt;
    &lt;li&gt;Clarify that the recording memorializing the express verifiable authorization required before a seller or telemarketer bills a customer or donor (unless payment is made by debit or credit card) must include an accurate description, clearly and conspicuously stated, of the goods or services or charitable contribution for which the payment authorization is sought.&lt;/li&gt;
&lt;/ol&gt;&lt;p&gt;The FTC has also proposed to prohibit sellers or telemarketers from requesting or receiving payment for recovery services for losses incurred in any prior transaction, regardless of whether that loss occurred via telemarketing, the Internet, or another means or medium, until seven business days after the consumer received the recovered money or merchandise. The prohibition currently is limited to services for the recovery of money lost through telemarketing fraud only. However, the Commission notes that consumer complaints and the FTC&amp;rsquo;s regulatory efforts reveal that consumers are susceptible to the same type of fraud over the Internet, and are therefore equally susceptible to pitches for telemarketing services promising to recover, in exchange for an advance fee, the money or merchandise lost as a result of such Internet fraud.&lt;/p&gt;
&lt;p&gt;Finally, the FTC has also proposed to bar sellers and telemarketers from accepting remotely created checks, remotely created payment orders, cash-to-cash money transfers, and cash reload mechanisms (collectively defined as &amp;ldquo;novel payment methods&amp;rdquo;) as payment during inbound or outbound telemarketing transactions. The Commission&amp;rsquo;s rationale for the proposed changes is, in part, that the consumer protections typically associated with traditional payment methods, such as credit cards, debit cards, and electronic fund transfers are not present with novel payment methods. Further, the Commission expresses concern that the &amp;ldquo;express verifiable authorization&amp;rdquo; provision currently in the TSR, which requires telemarketers to obtain a consumer&amp;rsquo;s express verifiable authorization for all telemarketing transactions where payment is made by a method other than a credit or debit card, does not adequately protect consumers against fraud, as evidenced by the law enforcement actions discussed in the NPRM.&lt;/p&gt;
&lt;p&gt;The comment period will remain open until July 29, 2013.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Associate &lt;a href="http://www.kelleydrye.com/attorneys/katherine_riley"&gt;Katherine E. Riley&lt;/a&gt; contributed to this post.  Ms. Riley is admitted only in Massachusetts.  She is practicing under the supervision of principals of the firm who are members of the D.C. Bar.&lt;/em&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AdLawAccess/~4/X0eWG7NMV0A" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AdLawAccess/~3/X0eWG7NMV0A/</link>
         <guid isPermaLink="false">http://www.adlawaccess.com/2013/05/articles/telemarketing-and-call-center/ftc-seeks-public-comment-on-proposed-amendments-to-the-telemarketing-sales-rule/</guid>
         <category domain="http://www.adlawaccess.com/articles">Advertising</category><category domain="http://www.adlawaccess.com/articles">Federal Trade Commission</category><category domain="http://www.adlawaccess.com/articles">Privacy and Information Security</category><category domain="http://www.adlawaccess.com/articles">Telemarketing and Call Center Operations</category>
         <pubDate>Tue, 28 May 2013 10:06:16 -0500</pubDate>
         <dc:creator>Daniel S. Blynn</dc:creator>
      
      <feedburner:origLink>http://www.adlawaccess.com/2013/05/articles/telemarketing-and-call-center/ftc-seeks-public-comment-on-proposed-amendments-to-the-telemarketing-sales-rule/</feedburner:origLink></item>
            <item>
         <title>FTC Issues Latest Update to COPPA FAQs</title>
         <description>&lt;p&gt;Earlier this week, the Federal Trade Commission announced an update to its &lt;a href="http://business.ftc.gov/documents/Complying-with-COPPA-Frequently-Asked-Questions#parentalconsent"&gt;frequently asked questions&lt;/a&gt; (&amp;ldquo;FAQs&amp;rdquo;) document to assist online operators as they prepare for changes to the Children&amp;rsquo;s Online Privacy Protection (&amp;ldquo;COPPA&amp;rdquo;) Rule, which go into effect on July 1, 2013.  The updated FAQs clarify parental notice and consent obligations for child-directed apps that collect information from a child in order to send push notifications to users.  The new question (No. 80) and answer read as follows:&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;80.    I have a child-directed app and want to send push notifications.  Do I need to get parental consent?&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;The information you collect from the child&amp;rsquo;s device used to send push notifications is online contact information &amp;ndash; it permits you to contact the user outside the confines of your app &amp;ndash; and is therefore personal information under the Rule.  To the extent the child has specifically requested push notifications, however, you may be able to rely on the &amp;ldquo;multiple-contact&amp;rdquo; exception to verifiable parental consent, for which you must also collect a parent&amp;rsquo;s online contact information and provide parents with direct notice of your information practices and an opportunity to opt-out.  See FAQ 58.   Importantly, in order to fit within this exception, your push notifications must be reasonably related to the content of your app.  If you want to combine this online contact information with other personal information collected from the child, you cannot rely on this exception and must provide parents with direct notice and obtain verifiable parental consent prior to sending push notifications to the child.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The FTC&amp;rsquo;s latest update to the COPPA FAQs follows other recent efforts to educate operators of websites and online services directed to children about their obligations under the amended Rule.  As we described last week, the FTC recently &lt;a href="http://www.adlawaccess.com/2013/05/articles/privacy-and-information-securi/ftc-reaches-out-to-businesses-on-coppa/"&gt;sent letters to more than 90 U.S. and foreign-based companies&lt;/a&gt; to highlight the significant Rule changes relating to the definition of &amp;ldquo;personal information.&amp;rdquo;&lt;br /&gt;
&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AdLawAccess/~4/E2xWmrf44Rk" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AdLawAccess/~3/E2xWmrf44Rk/</link>
         <guid isPermaLink="false">http://www.adlawaccess.com/2013/05/articles/privacy-and-information-securi/ftc-issues-latest-update-to-coppa-faqs/</guid>
         <category domain="http://www.adlawaccess.com/articles">Privacy and Information Security</category>
         <pubDate>Fri, 24 May 2013 10:23:06 -0500</pubDate>
         <dc:creator>Matthew Sullivan</dc:creator>
      
      <feedburner:origLink>http://www.adlawaccess.com/2013/05/articles/privacy-and-information-securi/ftc-issues-latest-update-to-coppa-faqs/</feedburner:origLink></item>
            <item>
         <title>NAI Releases Updated Code of Conduct for Online Behavioral Advertising</title>
         <description>&lt;p&gt;The Network Advertising Initiative (&amp;ldquo;NAI&amp;rdquo;) &lt;a href="http://www.networkadvertising.org/sites/default/files/2013_nai_code_pr.pdf"&gt;recently announced&lt;/a&gt; final updates to its&lt;a href="http://www.networkadvertising.org/2013_Principles.pdf"&gt; 2013 Code of Conduct&lt;/a&gt; (&amp;ldquo;NAI Code&amp;rdquo;).  The NAI Code is one of the leading industry self-regulatory codes of conduct governing online behavioral advertising (&amp;ldquo;OBA&amp;rdquo;) for third party digital advertising companies.  While prior versions of the NAI Code were focused on advertising networks, the 2013 NAI Code keeps pace with developments in the online advertising ecosystem and also governs the actions of participating demand side platforms (&amp;ldquo;DSPs&amp;rdquo;), supply side platforms (&amp;ldquo;SSPs&amp;rdquo;), and ad exchanges, among others.&lt;/p&gt;
&lt;p&gt;The 2013 NAI Code reinforces the requirements for participants to provide education, notice, and choice regarding OBA, stating that industry&amp;rsquo;s approach must not remain stagnant, but rather adapt to ensure that the self-regulatory framework remains relevant and effective.  It was also updated to reflect regulatory guidance including the FTC Final Privacy Report and White House Privacy Report.  Additionally, the 2013 NAI Code harmonizes requirements with the Digital Advertising Alliance (&amp;ldquo;DAA&amp;rdquo;) Self-Regulatory Principles for Online Behavioral Advertising.  [&lt;em&gt;The NAI is one of the members of the DAA&lt;/em&gt;.]&lt;/p&gt;
&lt;p&gt;The 2013 NAI Code introduces a new framework of data &amp;ldquo;identifiability&amp;rdquo; that splits the difference between the FTC and industry&amp;rsquo;s definitions of what is PII:&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;PII = Used or intended to be used to identify an &lt;em&gt;individual&lt;/em&gt;&lt;/li&gt;
    &lt;li&gt;Non-PII = Linked or reasonably linkable to a specific &lt;em&gt;computer &lt;/em&gt;or &lt;em&gt;device&lt;/em&gt;&lt;/li&gt;
    &lt;li&gt;De-Identified Data = Not linked or reasonably linkable to either an individual or a specific computer or device&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The online advertising industry continues to face &lt;a href="http://www.adweek.com/news/technology/ftc-chair-stuns-advertisers-148644"&gt;scrutiny from regulators&lt;/a&gt; and &lt;a href="http://adage.com/article/digital/sen-jay-rockefeller-blasts-ad-industry-track/241078/"&gt;Congress &lt;/a&gt;regarding its approach to OBA, with a specific focus on a Do Not Track standard.  Companies engaged in any OBA, interest-based advertising, or online remarketing / retargeting activities should stay tuned as the self-regulatory and regulatory framework continues to evolve.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AdLawAccess/~4/74NJxwycqT8" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AdLawAccess/~3/74NJxwycqT8/</link>
         <guid isPermaLink="false">http://www.adlawaccess.com/2013/05/articles/advertising-1/nai-releases-updated-code-of-conduct-for-online-behavioral-advertising/</guid>
         <category domain="http://www.adlawaccess.com/articles">Advertising</category><category domain="http://www.adlawaccess.com/articles">Federal Trade Commission</category><category domain="http://www.adlawaccess.com/tags">OBA</category><category domain="http://www.adlawaccess.com/articles">Privacy and Information Security</category>
         <pubDate>Wed, 22 May 2013 16:07:36 -0500</pubDate>
         <dc:creator>Christopher M. Loeffler</dc:creator>
      
      <feedburner:origLink>http://www.adlawaccess.com/2013/05/articles/advertising-1/nai-releases-updated-code-of-conduct-for-online-behavioral-advertising/</feedburner:origLink></item>
            <item>
         <title>Kansas AG Action Offers Reminder That States Monitor Do-Not-Call Compliance</title>
         <description>&lt;p&gt;A few days ago, a Kansas state court entered a default judgment against Bullseye Target Marketing, a Missouri telemarketing company that solicited roofing business in Kansas, in an &lt;a href="http://ag.ks.gov/search-results-detail/2013/05/10/ag-schmidt-missouri-storm-chasing-company-fined-for-no-call-act-violations"&gt;action brought by the Kansas Attorney General &lt;/a&gt;alleging violations of the Kansas No-Call Act (the state analogue to the federal Telemarketing Sales Rule).  The court ordered the company to pay $600,000 in penalties.  The action was filed after the Attorney General received complaints from Kansas consumers that they received unsolicited calls offering to schedule roof inspections in areas that had experienced storm damage, despite their numbers being registered on the state do-not-call list.  The Kansas No-Call Act generally prohibits businesses from placing telemarketing calls to consumers registered on the state do-not-call list.&lt;/p&gt;
&lt;p&gt;This Attorney General action should serve as a reminder that do-not-call compliance is not only being monitored and enforced by the Federal Trade Commission, but states, too, are active in the area. &lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AdLawAccess/~4/MFD7j-1q6xc" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AdLawAccess/~3/MFD7j-1q6xc/</link>
         <guid isPermaLink="false">http://www.adlawaccess.com/2013/05/articles/telemarketing-and-call-center/kansas-ag-action-offers-reminder-that-states-monitor-donotcall-compliance/</guid>
         <category domain="http://www.adlawaccess.com/articles">Advertising</category><category domain="http://www.adlawaccess.com/articles">Federal Trade Commission</category><category domain="http://www.adlawaccess.com/articles">Telemarketing and Call Center Operations</category>
         <pubDate>Sat, 18 May 2013 07:40:14 -0500</pubDate>
         <dc:creator>Daniel S. Blynn</dc:creator>
      
      <feedburner:origLink>http://www.adlawaccess.com/2013/05/articles/telemarketing-and-call-center/kansas-ag-action-offers-reminder-that-states-monitor-donotcall-compliance/</feedburner:origLink></item>
            <item>
         <title>Vermont Changes Law on Skill Contests</title>
         <description>&lt;p&gt;All states prohibit companies from requiring people to pay money or make a purchase to enter a sweepstakes. Although most states allow companies more flexibility to require a payment or purchase in a skill contest, some states prohibit those requirements, too. Up until now, Vermont was in the latter category.&lt;/p&gt;
&lt;p&gt;Effective April 26, 2013, nothing in the Vermont &lt;a href="http://www.leg.state.vt.us/docs/2014/Acts/ACT009.pdf"&gt;statute&lt;/a&gt;&amp;nbsp;&amp;ldquo;shall be construed to prohibit a person from requiring or paying any kind of entry fee, service charge, purchase, or similar consideration in order to enter, or continue to remain eligible for, a game of skill or other promotion that is not based on chance.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;The line between chance and skill isn&amp;rsquo;t always clear, but if companies can get on the right side of that line, they&amp;rsquo;ll soon have more options for running promotions in Vermont.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AdLawAccess/~4/qY4dlmQ5nj8" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AdLawAccess/~3/qY4dlmQ5nj8/</link>
         <guid isPermaLink="false">http://www.adlawaccess.com/2013/05/articles/promotions-marketing/vermont-changes-law-on-skill-contests/</guid>
         <category domain="http://www.adlawaccess.com/articles">Promotions Marketing</category>
         <pubDate>Fri, 17 May 2013 07:45:19 -0500</pubDate>
         <dc:creator>Gonzalo E. Mon</dc:creator>
      
      <feedburner:origLink>http://www.adlawaccess.com/2013/05/articles/promotions-marketing/vermont-changes-law-on-skill-contests/</feedburner:origLink></item>
            <item>
         <title>FTC Reaches Out to Businesses on COPPA</title>
         <description>&lt;p&gt;On May 15, 2013, the Federal Trade Commission &lt;a href="http://www.ftc.gov/opa/2013/05/coppa_education.shtm"&gt;sent letters&lt;/a&gt; to more than 90 U.S. and foreign-based companies that may be affected by &lt;a href="http://www.ftc.gov/os/2012/12/121219copparulefrn.pdf"&gt;amendments&lt;/a&gt; to the Children&amp;rsquo;s Online Privacy Protection Rule (&amp;ldquo;COPPA&amp;rdquo; or the &amp;ldquo;Rule&amp;rdquo;), which go into effect on &lt;a href="http://www.ftc.gov/opa/2013/05/coppa.shtm"&gt;July 1, 2013&lt;/a&gt;.  The letters, which do not reflect an official evaluation of the recipients&amp;rsquo; privacy practices, were targeted to online services and mobile applications that collect &amp;ldquo;personal information&amp;rdquo; from children under age 13, as defined by the Rule.&lt;/p&gt;
&lt;p&gt;The primary purpose of the letters was to highlight the significant changes to the COPPA Rule definition of personal information, which, under the current Rule, includes user names, a home or physical address, contact information (e-mail address or telephone number), and social security numbers.  As described in the letters, the amended Rule expands the definition of personal information to include persistent identifiers, such as cookies, IP addresses, and mobile device IDs, that can recognize users over time and across different websites or online services.  Online operators that collect such information must provide notice and obtain parental consent, unless they use the identifiers to support internal operations, such as for user authentication or network analysis.  Under the revised Rule, personal information also includes photographs or video with a child&amp;rsquo;s image, or an audio file with a child&amp;rsquo;s voice.&lt;/p&gt;
&lt;p&gt;In addition to describing changes to the definition of personal information, the letters also highlighted the following &amp;ldquo;musts&amp;rdquo; for developers of child-directed online or mobile apps:&lt;/p&gt;
&lt;p&gt;&amp;bull;	Notice and parental consent for personal information collected on applications from third parties, such as ad networks;&lt;br /&gt;
&amp;bull;	Reasonable steps to release children&amp;rsquo;s personal information only to companies that will keep it secure and confidential;&lt;br /&gt;
&amp;bull;	New data retention and deletion requirements.&lt;/p&gt;
&lt;p&gt;The letters are the latest step by the Commission to generate awareness about how the COPPA Rule changes may affect online operators&amp;rsquo; current business practices.  As we described last month, FTC Staff also issued an updated Frequently Asked Questions (&amp;ldquo;FAQ&amp;rdquo;) document, &lt;a href="http://www.adlawaccess.com/2013/04/articles/privacy-and-information-securi/ftc-issues-updated-coppa-faqs/"&gt;Complying with COPPA: Frequently Asked Questions&lt;/a&gt;, that includes a number of questions (and answers) that directly address how the amended COPPA Rule differs from the current Rule.&lt;br /&gt;
&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AdLawAccess/~4/PRZy9H86958" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AdLawAccess/~3/PRZy9H86958/</link>
         <guid isPermaLink="false">http://www.adlawaccess.com/2013/05/articles/privacy-and-information-securi/ftc-reaches-out-to-businesses-on-coppa/</guid>
         <category domain="http://www.adlawaccess.com/articles">Privacy and Information Security</category>
         <pubDate>Thu, 16 May 2013 09:33:30 -0500</pubDate>
         <dc:creator>Matthew Sullivan</dc:creator>
      
      <feedburner:origLink>http://www.adlawaccess.com/2013/05/articles/privacy-and-information-securi/ftc-reaches-out-to-businesses-on-coppa/</feedburner:origLink></item>
            <item>
         <title>FCC Opens the Door to Vicarious Liability for Third-Party Telemarketing Under Certain Conditions</title>
         <description>&lt;p&gt;On May 9, 2013, the Federal Communications Commission  ruled that sellers may be held vicariously liable under the Telephone Consumer Protection Act (&amp;ldquo;TCPA&amp;rdquo;) for unlawful telemarketing by third parties under certain circumstances.  The FCC&amp;rsquo;s Declaratory Ruling addresses third-party liability for violations of the Do Not Call  and prerecorded message restrictions of the Communications Act.  The Commission ruled that, under both provisions, a seller may be held vicariously liable for violative calls placed by third-party marketing agents under principles of the federal common law of agency.&lt;/p&gt;
&lt;p&gt;The Declaratory Ruling thus resolves a central question that is raised in a number of TCPA lawsuits: sellers may only be held liable for actions of those third party telemarketers that are determined to be agents, applying the federal common law of agency.  Moreover, a manufacturer that simply puts a product in the chain of commerce that is later resold by a seller is not likely to be affected by this Ruling, provided that it does not otherwise trigger the TCPA&amp;rsquo;s seller definition.&lt;/p&gt;
&lt;p&gt;With respect to how and under what circumstances the federal common law of agency will be applied to find a seller vicariously liable for the acts of third parties, the future is unclear &amp;ndash; particularly with respect to claims based on alleged apparent authority and whether the FCC&amp;rsquo;s &amp;ldquo;illustrative examples&amp;rdquo; of such apparent authority set forth in the Ruling will influence courts in interpreting how the federal common law of agency should apply to the specific facts of a particular case.&lt;/p&gt;
&lt;p&gt;For more on this decision, please reference the &lt;a href="http://www.kelleydrye.com/publications/client_advisories/0817"&gt;Kelley Drye client advisory&lt;/a&gt;.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AdLawAccess/~4/XTKrAU9HxjY" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AdLawAccess/~3/XTKrAU9HxjY/</link>
         <guid isPermaLink="false">http://www.adlawaccess.com/2013/05/articles/advertising-1/fcc-opens-the-door-to-vicarious-liability-for-thirdparty-telemarketing-under-certain-conditions/</guid>
         <category domain="http://www.adlawaccess.com/articles">Advertising</category><category domain="http://www.adlawaccess.com/articles">Federal Communications Commission</category><category domain="http://www.adlawaccess.com/articles">Telemarketing and Call Center Operations</category>
         <pubDate>Wed, 15 May 2013 16:28:24 -0500</pubDate>
         <dc:creator>Alysa Zeltzer Hutnik</dc:creator>
      
      <feedburner:origLink>http://www.adlawaccess.com/2013/05/articles/advertising-1/fcc-opens-the-door-to-vicarious-liability-for-thirdparty-telemarketing-under-certain-conditions/</feedburner:origLink></item>
            <item>
         <title>House Lawmakers Introduce New Bill to Address Mobile App Privacy</title>
         <description>&lt;p&gt;On Thursday, May 9, Rep. Hank Johnson (D-GA), and co-sponsor Rep. Steve Chabot (R-OH) introduced the &amp;ldquo;&lt;a href="http://hankjohnson.house.gov/sites/hankjohnson.house.gov/files/documents/APPS_Act_2013.pdf"&gt;Application Privacy, Protection, and Security (APPS) Act of 2013&lt;/a&gt;,&amp;rdquo; (H.R. 1913). The bill, which is aimed at increasing consumer privacy within applications (&amp;ldquo;apps&amp;rdquo;) available through smartphones and other mobile devices, retains the provisions included in the discussion draft of the legislation circulated by Rep. Johnson in January 2013.&lt;/p&gt;
&lt;p&gt;Among its key provisions, the APPS Act would require app developers to make a privacy statement available to consumers before they purchase an app, obtain consent from consumers before collecting data, and securely maintain the data that they collect.  A developer&amp;rsquo;s privacy statement would have to disclose the categories of personal information collected by the app, and how such information is used, including whether it is shared with any third parties.  App developers also would be required to include within their privacy statement a data retention policy that describes how long information is retained, and how consumers can access and seek the removal of such information.  Under the bill, the Federal Trade Commission would be tasked with drafting regulations to implement the law, including defining the term &amp;ldquo;personal data,&amp;rdquo; as well as enforcing such regulations.&lt;/p&gt;
&lt;p&gt;The APPS Act is the product of Rep. Johnson&amp;rsquo;s &lt;a href="https://apprights-hankjohnson.house.gov/"&gt;AppRights&lt;/a&gt; initiative, which is a web-based legislative project launched in July 2012 to address the privacy and security of mobile device users, and follows other recent federal and state efforts to enhance privacy protections for mobile app users. For example,&lt;a href="http://www.adlawaccess.com/2013/05/articles/privacy-and-information-securi/delta-cleared-for-takeoff-wins-dismissal-of-california-ag-mobile-app-privacy-action/"&gt; we posted last week&lt;/a&gt; about the latest developments regarding the California Attorney General&amp;rsquo;s efforts to require all app developers to include a privacy policy in their mobile app. &lt;br /&gt;
&amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AdLawAccess/~4/3jpMJeCjj0Q" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AdLawAccess/~3/3jpMJeCjj0Q/</link>
         <guid isPermaLink="false">http://www.adlawaccess.com/2013/05/articles/privacy-and-information-securi/house-lawmakers-introduce-new-bill-to-address-mobile-app-privacy/</guid>
         <category domain="http://www.adlawaccess.com/articles">Privacy and Information Security</category>
         <pubDate>Mon, 13 May 2013 10:08:37 -0500</pubDate>
         <dc:creator>Matthew Sullivan</dc:creator>
      
      <feedburner:origLink>http://www.adlawaccess.com/2013/05/articles/privacy-and-information-securi/house-lawmakers-introduce-new-bill-to-address-mobile-app-privacy/</feedburner:origLink></item>
            <item>
         <title>Delta Cleared for Takeoff: Wins Dismissal of California AG Mobile App Privacy Action</title>
         <description>&lt;p&gt;In December 2012, the California Attorney General filed a lawsuit against Delta Airlines, Inc. (&amp;ldquo;Delta&amp;rdquo;) alleging that Delta violated California&amp;rsquo;s Online Privacy Protection Act by failing to post a privacy policy within its &lt;i&gt;Fly Delta&lt;/i&gt; mobile app. &amp;nbsp;It was the first mobile app enforcement action brought by the California Attorney General and closely followed the Attorney General&amp;rsquo;s warning campaign in which it sent out letters to approximately 100 app developers and companies notifying them that they were not in compliance with California&amp;rsquo;s law.&amp;nbsp; Our previous coverage of the complaint is &lt;a href="http://www.adlawaccess.com/2012/12/articles/privacy-and-information-securi/california-ag-files-lawsuit-against-delta-airlines-for-noncompliance-with-californias-online-privacy-law/"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Yesterday, the California Superior Court dismissed the claim, holding that the state action is pre-empted by the federal Airline Deregulation Act, which prohibits states from applying regulations on airlines related to price, routes, or services.&amp;nbsp; Judge Miller stated: &amp;ldquo;In this instances it&amp;rsquo;s services. . . . I think that this case is, in effect, an attempt to apply a state law designed to prevent unfair competition, which regulates an airline&amp;rsquo;s communications with consumers, and I think it&amp;rsquo;s pre-empted.&amp;rdquo;&amp;nbsp; Press coverage is available &lt;a href="http://www.businessweek.com/news/2013-05-09/delta-wins-dismissal-of-california-mobile-app-privacy-suit-1"&gt;here&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;This is an interesting result for the first Attorney General app enforcement action and it&amp;rsquo;s too soon to tell whether the Attorney General will appeal the decision.&amp;nbsp; Unfortunately, the ruling doesn&amp;rsquo;t provide any substantive guidance, or give much comfort, to companies that can&amp;rsquo;t make similar federal pre-emption arguments.&amp;nbsp; Companies with mobile apps will want to keep their seatbacks and tray tables in their upright and locked positions as we watch for the Attorney General&amp;rsquo;s next activities in the mobile privacy space.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AdLawAccess/~4/-LT2K2fznoM" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AdLawAccess/~3/-LT2K2fznoM/</link>
         <guid isPermaLink="false">http://www.adlawaccess.com/2013/05/articles/privacy-and-information-securi/delta-cleared-for-takeoff-wins-dismissal-of-california-ag-mobile-app-privacy-action/</guid>
         <category domain="http://www.adlawaccess.com/articles">Mobile Marketing</category><category domain="http://www.adlawaccess.com/articles">Privacy and Information Security</category>
         <pubDate>Fri, 10 May 2013 11:24:52 -0500</pubDate>
         <dc:creator>Christopher M. Loeffler</dc:creator>
      
      <feedburner:origLink>http://www.adlawaccess.com/2013/05/articles/privacy-and-information-securi/delta-cleared-for-takeoff-wins-dismissal-of-california-ag-mobile-app-privacy-action/</feedburner:origLink></item>
            <item>
         <title>Common Sense Rules in LA Lakers Text Message Suit</title>
         <description>&lt;p&gt;Most marketers know they are legally required to get permission before sending text messages to consumers. Despite this, the number of lawsuits involving (allegedly) unsolicited text messages keeps growing, as does the cost of settling these suits. Although the first cases in this area involved practices that were clearly unlawful &amp;mdash; such as sending text messages to people who hadn&amp;rsquo;t signed up &amp;mdash; now, companies are getting sued over much less. Fortunately, many courts have taken a common sense approach to these cases.&lt;/p&gt;
&lt;p&gt;During a Lakers game last year, the team invited fans to text a message for a chance to have it appear on the scoreboard. A fan texted a message, and received the following confirmation from the Lakers in return: &amp;ldquo;Thnx! Txt as many times as u like. Not all msgs go on screen. Txt ALERTS for Lakers News alerts  Msg&amp;amp;Data Rates May Apply. Txt STOP to quit. Txt INFO for info.&amp;rdquo; Shortly thereafter, the plaintiff filed a lawsuit against the Lakers arguing that the team had sent that message without consent, in violation of the Telephone Consumer Protection Act.&lt;/p&gt;
&lt;p&gt;Applying a &amp;ldquo;common sense&amp;rdquo; reading of the TCPA, a California court determined that, by sending his original message, the plaintiff &amp;ldquo;expressly consented&amp;rdquo; to receiving a confirmatory text message from the Lakers. Indeed, the court noted that when the plaintiff sought to display his message on the scoreboard, &amp;ldquo;it is difficult to imagine how he could have been certain that the Lakers received his message without a confirmative response.&amp;rdquo; Accordingly, the court granted the Laker&amp;rsquo;s motion to dismiss the case.&lt;/p&gt;
&lt;p&gt;There are still a number of legal risks associated with text message campaigns, but this decision &amp;mdash; &lt;a href="http://www.adlawaccess.com/2012/12/articles/mobile-marketing/fcc-permits-confirmatory-optout-texts-under-tcpa/"&gt;as well as other recent developments&lt;/a&gt; &amp;mdash; suggests that companies now have a better shot at prevailing in these types of nuisance suits.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AdLawAccess/~4/Y8U8D0n9drI" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AdLawAccess/~3/Y8U8D0n9drI/</link>
         <guid isPermaLink="false">http://www.adlawaccess.com/2013/05/articles/mobile-marketing/common-sense-rules-in-la-lakers-text-message-suit/</guid>
         <category domain="http://www.adlawaccess.com/articles">Mobile Marketing</category>
         <pubDate>Fri, 10 May 2013 09:50:05 -0500</pubDate>
         <dc:creator>Gonzalo E. Mon</dc:creator>
      
      <feedburner:origLink>http://www.adlawaccess.com/2013/05/articles/mobile-marketing/common-sense-rules-in-la-lakers-text-message-suit/</feedburner:origLink></item>
            <item>
         <title>Mandated Compliance Programs as the New Normal? Williams-Sonoma Agrees to $987,000 CPSC Civil Penalty &amp; Comprehensive Compliance Program</title>
         <description>&lt;p&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
&lt;w:WordDocument&gt;
&lt;w:View&gt;Normal&lt;/w:View&gt;
&lt;w:Zoom&gt;0&lt;/w:Zoom&gt;
&lt;w:TrackMoves /&gt;
&lt;w:TrackFormatting /&gt;
&lt;w:PunctuationKerning /&gt;
&lt;w:ValidateAgainstSchemas /&gt;
&lt;w:SaveIfXMLInvalid&gt;false&lt;/w:SaveIfXMLInvalid&gt;
&lt;w:IgnoreMixedContent&gt;false&lt;/w:IgnoreMixedContent&gt;
&lt;w:AlwaysShowPlaceholderText&gt;false&lt;/w:AlwaysShowPlaceholderText&gt;
&lt;w:DoNotPromoteQF /&gt;
&lt;w:LidThemeOther&gt;EN-US&lt;/w:LidThemeOther&gt;
&lt;w:LidThemeAsian&gt;X-NONE&lt;/w:LidThemeAsian&gt;
&lt;w:LidThemeComplexScript&gt;X-NONE&lt;/w:LidThemeComplexScript&gt;
&lt;w:Compatibility&gt;
&lt;w:BreakWrappedTables /&gt;
&lt;w:SnapToGridInCell /&gt;
&lt;w:WrapTextWithPunct /&gt;
&lt;w:UseAsianBreakRules /&gt;
&lt;w:DontGrowAutofit /&gt;
&lt;w:SplitPgBreakAndParaMark /&gt;
&lt;w:EnableOpenTypeKerning /&gt;
&lt;w:DontFlipMirrorIndents /&gt;
&lt;w:OverrideTableStyleHps /&gt;
&lt;/w:Compatibility&gt;
&lt;w:BrowserLevel&gt;MicrosoftInternetExplorer4&lt;/w:BrowserLevel&gt;
&lt;m:mathPr&gt;
&lt;m:mathFont m:val="Cambria Math" /&gt;
&lt;m:brkBin m:val="before" /&gt;
&lt;m:brkBinSub m:val="&amp;#45;-" /&gt;
&lt;m:smallFrac m:val="off" /&gt;
&lt;m:dispDef /&gt;
&lt;m:lMargin m:val="0" /&gt;
&lt;m:rMargin m:val="0" /&gt;
&lt;m:defJc m:val="centerGroup" /&gt;
&lt;m:wrapIndent m:val="1440" /&gt;
&lt;m:intLim m:val="subSup" /&gt;
&lt;m:naryLim m:val="undOvr" /&gt;
&lt;/m:mathPr&gt;&lt;/w:WordDocument&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 9]&gt;&lt;xml&gt;
&lt;w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="true"
DefSemiHidden="true" DefQFormat="false" DefPriority="99"
LatentStyleCount="267"&gt;
&lt;w:LsdException Locked="false" Priority="0" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Normal" /&gt;
&lt;w:LsdException Locked="false" Priority="9" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="heading 1" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 2" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 3" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 4" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 5" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 6" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 7" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 8" /&gt;
&lt;w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 9" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 1" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 2" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 3" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 4" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 5" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 6" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 7" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 8" /&gt;
&lt;w:LsdException Locked="false" Priority="39" Name="toc 9" /&gt;
&lt;w:LsdException Locked="false" Priority="35" QFormat="true" Name="caption" /&gt;
&lt;w:LsdException Locked="false" Priority="10" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Title" /&gt;
&lt;w:LsdException Locked="false" Priority="1" Name="Default Paragraph Font" /&gt;
&lt;w:LsdException Locked="false" Priority="11" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtitle" /&gt;
&lt;w:LsdException Locked="false" Priority="22" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Strong" /&gt;
&lt;w:LsdException Locked="false" Priority="20" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Emphasis" /&gt;
&lt;w:LsdException Locked="false" Priority="59" SemiHidden="false"
UnhideWhenUsed="false" Name="Table Grid" /&gt;
&lt;w:LsdException Locked="false" UnhideWhenUsed="false" Name="Placeholder Text" /&gt;
&lt;w:LsdException Locked="false" Priority="1" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="No Spacing" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 1" /&gt;
&lt;w:LsdException Locked="false" UnhideWhenUsed="false" Name="Revision" /&gt;
&lt;w:LsdException Locked="false" Priority="34" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="List Paragraph" /&gt;
&lt;w:LsdException Locked="false" Priority="29" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Quote" /&gt;
&lt;w:LsdException Locked="false" Priority="30" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Quote" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 1" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 2" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 3" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 4" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 5" /&gt;
&lt;w:LsdException Locked="false" Priority="60" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Shading Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="61" SemiHidden="false"
UnhideWhenUsed="false" Name="Light List Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="62" SemiHidden="false"
UnhideWhenUsed="false" Name="Light Grid Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="63" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 1 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="64" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Shading 2 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="65" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 1 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="66" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium List 2 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="67" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 1 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="68" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 2 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="69" SemiHidden="false"
UnhideWhenUsed="false" Name="Medium Grid 3 Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="70" SemiHidden="false"
UnhideWhenUsed="false" Name="Dark List Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="71" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Shading Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="72" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful List Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="73" SemiHidden="false"
UnhideWhenUsed="false" Name="Colorful Grid Accent 6" /&gt;
&lt;w:LsdException Locked="false" Priority="19" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtle Emphasis" /&gt;
&lt;w:LsdException Locked="false" Priority="21" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Emphasis" /&gt;
&lt;w:LsdException Locked="false" Priority="31" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Subtle Reference" /&gt;
&lt;w:LsdException Locked="false" Priority="32" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Intense Reference" /&gt;
&lt;w:LsdException Locked="false" Priority="33" SemiHidden="false"
UnhideWhenUsed="false" QFormat="true" Name="Book Title" /&gt;
&lt;w:LsdException Locked="false" Priority="37" Name="Bibliography" /&gt;
&lt;w:LsdException Locked="false" Priority="39" QFormat="true" Name="TOC Heading" /&gt;
&lt;/w:LatentStyles&gt;
&lt;/xml&gt;&lt;![endif]--&gt;&lt;!--[if gte mso 10]&gt;
&lt;style&gt;
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman","serif";}
&lt;/style&gt;
&lt;![endif]--&gt;The tide continues to rise for Consumer Product Safety Commission (&amp;ldquo;CPSC&amp;rdquo;) civil penalties as the Commission announces a $987,000 penalty against Williams-Sonoma, Inc. and the company&amp;rsquo;s agreement to implement an extensive compliance program.  On Monday, the CPSC announced that Williams-Sonoma has agreed to pay the civil penalty to resolve allegations that the company knowingly failed to report a defect in its Pottery Barn wooden hammocks.  Williams-Sonoma also agreed to implement a comprehensive compliance program that arguably encompasses far more than the company&amp;rsquo;s alleged failure to report in a timely manner.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;According to the &lt;a href="https://www.cpsc.gov/Global/Business-and-Manufacturing/Civil%20Penalties/2013/Williams-SonomaCivilPenalty.pdf"&gt;settlement agreement&lt;/a&gt;, the wood in the hammock stands allegedly deteriorated over time, and Williams-Sonoma had received notice of a consumer injury resulting from the failure of the hammock as early as November 2004 and had received its eighth incident report by the end of October 2006.  The company, however, did not report to the Commission until September 2008, when it knew of 45 incidents.  In October 2008, Williams-Sonoma and the CPSC announced the recall of 30,000 hammock stands.  Because the alleged failure to report occurred prior to September 2008, it was subject to the CPSC&amp;rsquo;s previous civil penalty cap of $1.825 million instead of the current cap of $15 million.&lt;/p&gt;
&lt;p&gt;In addition to the civil penalty, Williams-Sonoma agreed: (1) to implement and maintain a comprehensive compliance program designed to ensure compliance with all safety statutes and regulations enforced by the Commission (not just the Consumer Product Safety Act, which was the subject of the penalty); and (2) to maintain and enforce a system of internal controls and procedures designed to ensure timely and accurate reporting to the CPSC.  The comprehensive compliance program is the same as that imposed in the &lt;a href="http://www.cpsc.gov/Global/Newsroom/News-Releases/2013/13136.pdf"&gt;settlement agreement&lt;/a&gt; entered with Kolcraft Enterprises, Inc. earlier this year.  In a &lt;a href="https://www.cpsc.gov/Global/About-CPSC/Commissioners/Nord/NordWilliams-SonomaSettlement.pdf"&gt;statement &lt;/a&gt;issued in connection with the Williams-Sonoma settlement, Commissioner Nord expressed concern that, for a second time, the CPSC had insisted on a comprehensive compliance program absent evidence of widespread noncompliance and that &amp;ldquo;the compliance program language in [the] settlement is another step toward just such a de facto rule.&amp;rdquo;  She also noted that using recalls to justify imposing mandates unrelated to the problem (in this case, timely reporting) discourages participation in the voluntary recall process.&lt;/p&gt;
&lt;p&gt;Companies with products subject to the CPSC&amp;rsquo;s jurisdiction should note that mandated compliance programs appear to be the new normal for civil penalty agreements, regardless of a company's history with the Commission as civil penalty demands continue to increase.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Associate &lt;a href="http://www.kelleydrye.com/attorneys/katherine_riley"&gt;Katherine E. Riley&lt;/a&gt;  contributed to this post.&amp;nbsp; Ms. Riley is admitted only in  Massachusetts.&amp;nbsp; She is practicing under the supervision of principals of  the firm who are members of the D.C. Bar.&lt;/em&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AdLawAccess/~4/hAHeAqrgPcs" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AdLawAccess/~3/hAHeAqrgPcs/</link>
         <guid isPermaLink="false">http://www.adlawaccess.com/2013/05/articles/consumer-product-safety/mandated-compliance-programs-as-the-new-normal-williamssonoma-agrees-to-987000-cpsc-civil-penalty-comprehensive-compliance-program/</guid>
         <category domain="http://www.adlawaccess.com/articles">Consumer Product Safety</category>
         <pubDate>Wed, 08 May 2013 09:44:22 -0500</pubDate>
         <dc:creator>Christie Grymes Thompson</dc:creator>
      
      <feedburner:origLink>http://www.adlawaccess.com/2013/05/articles/consumer-product-safety/mandated-compliance-programs-as-the-new-normal-williamssonoma-agrees-to-987000-cpsc-civil-penalty-comprehensive-compliance-program/</feedburner:origLink></item>
            <item>
         <title>FTC Continues FCRA Enforcement Activities: Warning Letters to 10 Data Brokers</title>
         <description>&lt;p&gt;Today, the Federal Trade Commission (&amp;ldquo;FTC&amp;rdquo;) &lt;a href="http://www.ftc.gov/opa/2013/05/databroker.shtm"&gt;announced&lt;/a&gt;&amp;nbsp;that it sent letters to 10 data brokers warning them that their practices may be subject to the Fair Credit Reporting Act (&amp;ldquo;FCRA&amp;rdquo;).&amp;nbsp; A sample letter is available &lt;a href="http://www.ftc.gov/os/2013/05/130507databrokersusinfo.pdf"&gt;here&lt;/a&gt;.&amp;nbsp; Among other things, the FCRA governs the sale and use of consumer information which may be used to make decisions about consumers&amp;rsquo; creditworthiness, eligibility for insurance, or suitability for employment.&lt;/p&gt;
&lt;p&gt;As part of&amp;nbsp; a global privacy sweep conducted by the Global Privacy Enforcement Network (&amp;ldquo;GPEN&amp;rdquo;), the FTC conducted test-shopping with 45 data brokers.&amp;nbsp; Based on the sweep, 10 data brokers indicated a willingness to sell consumer information in a manner that &lt;i&gt;may&lt;/i&gt; violate the FCRA.&lt;/p&gt;
&lt;p&gt;As we&amp;rsquo;ve previously noted &lt;a href="http://www.adlawaccess.com/2012/02/articles/privacy-and-information-securi/ftc-warns-6-mobile-apps-about-possible-fcra-violations/"&gt;here&lt;/a&gt; and &lt;a href="http://www.adlawaccess.com/2012/06/articles/federal-trade-commission/spokeo-agrees-to-pay-800000-to-settle-charges-of-fcra-violations/"&gt;here&lt;/a&gt;, the FTC continues to use its authority under FCRA through enforcement actions&amp;mdash;which include civil penalties&amp;mdash;and warning letters.&amp;nbsp; Last month, the &lt;a href="http://www.ftc.gov/opa/2013/04/tenant.shtm"&gt;FTC warned 6 websites&lt;/a&gt; that their sharing of consumers&amp;rsquo; rental history information with landlords &lt;i&gt;may&lt;/i&gt; be subject to the FCRA.&lt;/p&gt;
&lt;p&gt;While the warning letters are not a formal complaint alleging FCRA violations, they are an important reminder for all companies that sell consumer information to closely examine whether these practices fall under the FCRA and, if so, to ensure proper compliance.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AdLawAccess/~4/8TeZYXeN7dY" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AdLawAccess/~3/8TeZYXeN7dY/</link>
         <guid isPermaLink="false">http://www.adlawaccess.com/2013/05/articles/federal-trade-commission/ftc-continues-fcra-enforcement-activities-warning-letters-to-10-data-brokers/</guid>
         <category domain="http://www.adlawaccess.com/articles">Federal Trade Commission</category><category domain="http://www.adlawaccess.com/tags">International</category><category domain="http://www.adlawaccess.com/articles">Privacy and Information Security</category>
         <pubDate>Tue, 07 May 2013 14:43:38 -0500</pubDate>
         <dc:creator>Christopher M. Loeffler</dc:creator>
      
      <feedburner:origLink>http://www.adlawaccess.com/2013/05/articles/federal-trade-commission/ftc-continues-fcra-enforcement-activities-warning-letters-to-10-data-brokers/</feedburner:origLink></item>
            <item>
         <title>Washington Attorney General Settles with T-Mobile Over Ad Claims</title>
         <description>&lt;p&gt;The Washington Attorney General recently announced a court-ordered agreement with T-Mobile over the company&amp;rsquo;s new advertising campaign. T-Mobile has been promoting a new service plan that offers &amp;ldquo;no restrictions,&amp;rdquo; &amp;ldquo;no annual contract,&amp;rdquo; and no requirement that customers &amp;ldquo;serve a two-year sentence.&amp;rdquo; The plan, however, does not include a phone. Instead, T-Mobile offers consumers an option to purchase a phone at a monthly rate over a two-year term. (They also offer other phone options.) Consumers who purchase a phone must pay the full cost of the phone if they cancel before the end of the two-year period.&lt;/p&gt;
&lt;p&gt;The Attorney General alleged that T-Mobile misled consumers by advertising the absence of restrictions, an &amp;ldquo;annual contract,&amp;rdquo; and a &amp;ldquo;two-year sentence,&amp;rdquo; without adequately disclosing that customers who terminate their service before a device is paid off will have to pay the balance due on the phone upon cancellation. In some cases, the cost is higher than the early termination fee charged by other carriers. According to the press release: &amp;ldquo;Instead of a &amp;lsquo;two-year sentence&amp;rsquo; for wireless service, consumers face a different two-year &amp;lsquo;sentence&amp;rsquo; to avoid a lump-sum balloon payment for the phone.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;As part of the settlement, T-Mobile agreed to change the way it advertises the plan, to contact customers who purchased phones under the plan and advise them of their right to cancel and get a refund, and to pay attorney&amp;rsquo;s fees and costs.&lt;/p&gt;
&lt;p&gt;This settlement serves another reminder that companies need to clearly and conspicuously disclose the material terms of their offers. You can&amp;rsquo;t just highlight the benefits of a product or service, and bury the costs and restrictions in the fine print. &amp;nbsp;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/AdLawAccess/~4/qw1mjbRGr1k" height="1" width="1"/&gt;</description>
         <link>http://feeds.lexblog.com/~r/AdLawAccess/~3/qw1mjbRGr1k/</link>
         <guid isPermaLink="false">http://www.adlawaccess.com/2013/05/articles/advertising-1/washington-attorney-general-settles-with-tmobile-over-ad-claims/</guid>
         <category domain="http://www.adlawaccess.com/articles">Advertising</category>
         <pubDate>Mon, 06 May 2013 13:20:22 -0500</pubDate>
         <dc:creator>Gonzalo E. Mon</dc:creator>
      
      <feedburner:origLink>http://www.adlawaccess.com/2013/05/articles/advertising-1/washington-attorney-general-settles-with-tmobile-over-ad-claims/</feedburner:origLink></item>
      
   </channel>
</rss>
