<?xml version="1.0" encoding="utf-8"?>
	<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
	<title>An RSS Feed from melniklegal.com</title>
<description>melniklegal.com Blog</description>
<link>http://melniklegal.com/programs/weblog.cgi</link>
<category>e-commerce</category>
<copyright>Copyright melniklegal.com </copyright>
<language>en-us</language>
<lastBuildDate>Fri, 20 Nov 2026 15:55:18 EST</lastBuildDate>
<managingEditor>tatiana@melniklegal.com (Web Master)</managingEditor>
<pubDate>Fri, 20 Nov 2026 15:55:18 EST</pubDate>
<webMaster>tatiana@melniklegal.com (Tatiana)</webMaster>
<generator>e-commerce-inc.com sitebuilder blog press</generator>
<atom:link href="http://melniklegal.com/programs/blogrss.cgi" rel="self" type="application/rss+xml" />

			
<item>
<title><![CDATA[What is an FDA Guidance document and do Guidance documents bind the FDA?]]></title>
<description><![CDATA[
 
 
 
 
  <div align="left">  <font face="Arial" size="3">FDA Guidance sets forth the FDA's "</font><font face="Arial" size="3"><font face="Arial" size="3">current thinking on a topic and should be viewed only as recommendations, unless specific regulatory or statutory requirements are cited</font>." As the FDA explains,</font><br><blockquote><font face="Arial" size="3">[The guidance] does not create or confer any rights for or on any person and does not operate to bind FDA or the public. You can use an alternative approach if the approach satisfies the requirements of the applicable statutes and regulations...FDA's guidance documents, including this guidance, do not establish legally enforceable responsibilities.</font><br></blockquote></div><div align="left"><font face="Arial">But, guidance documents should not be ignored because the FDA does tend to follow its own guidance. <br></font></div><div align="left"><br></div><div align="left"><font face="Arial" size="3"><u><b>What is the difference between laws, regulations, and guidance documents?<br></b></u></font></div><div align="left"><br><font face="Arial" size="3">The FDA must follow a set of laws, which are passed by Congress, and the FDA routinely issues regulations and guidance documents.</font><br><br><font face="Arial" size="3"><i><u>Laws</u></i></font><br></div><div align="left"><font face="Arial" size="3">One of the primary laws establishing the framework within which the FDA operates is the Federal Food, Drug, and Cosmetic Act (FD&amp;C Act). The FD&amp;C Act is amended by Congress from time to time.</font><font face="Arial" size="3"> Some of the more significant amendments include the Orphan Drug Act of 1983, Food Quality Protection Act of 1996, and the FDA Food Safety Modernization Act of 2011.<br><br><i><u>Regulations</u></i><br></font></div><div align="left"><font face="Arial" size="3">The FDA develops regulations based on the laws that are set forth in the FD&amp;C Act as well as the other laws under which the FDA operates. <u>Regulations issued by the FDA are federal laws</u> and are codified in the Code of Federal Regulations.</font><br><br><font face="Arial" size="3">When issuing regulations, the FDA follows the procedures set forth in the Administrative Procedure Act (APA). Broadly speaking, the APA sets for a Notice and Comment Rule Making process, which requires that regulatory agencies issue a proposed regulation, allow time for public input, and then issue a final regulation. More information about this process is available</font><font face="Arial" size="3"><a href="https://www.federalregister.gov/uploads/2011/01/the_rulemaking_process.pdf"> here</a> (PDF, Federal Register FAQ), <a href="https://www.foreffectivegov.org/node/2578">here</a> (Center for Effective Government), and <a href="https://biotech.law.lsu.edu/map/Notice-and-CommentRuleMaking.html">here</a> (LSU Public Health Map).</font><br><br><font face="Arial" size="3"><i><u>Guidance Documents</u></i></font><br><br><font face="Arial" size="3">After a regulation is issued, the FDA may determine that it needs to provide industry, academia, and other stakeholders with more information on how the FDA intends to exert (or decline to exercise, as the case may be) its regulatory authority. The FDA does this through issuing what it has termed 'Guidance' documents. The FDA </font><font face="Arial" size="3">follows the procedures required by its "Good Guidance Practice" regulation to issue FDA guidance.</font><br><br><font face="Arial" size="3">Guidance documents must not set new legal standards or impose new requirements. Unlike regulations, guidance documents do not contain amendments to the Code of Federal Regulations and are not subject to the notice and comment process.</font><br><br><font face="Arial" size="3"><u><b>Are FDA Guidance Document Law?</b></u></font><br><br><font face="Arial" size="3"><b>No.</b> The FDA guidance documents are not legally binding on the public or the FDA. <b><u>BUT</u></b>, the FDA has come to rely on guidance documents as a means of informal policy making. By telling industries when it does and does not plan to act, the FDA is giving industry stakeholders notice of its position on certain issues (<i>e.g.</i>, how the FDA intends to treat mobile medical apps). As a result, impacted industries would be wise to take heed and pay attention to the guidance documents. <b>So, for practical purposes, FDA guidance documents are laws</b>.</font><br><br></div><div align="left"><font face="Arial" size="3"><u><b>Do Guidance documents bind the FDA?</b></u></font><br><br><font face="Arial" size="3">In other words, can the FDA base its legal action against a company on an FDA Guidance document or can a company use an FDA Guidance document in its own defense?</font><br><br><font face="Arial" size="3">This is a complicated question due to several cases that were decided by the U.S. Supreme Court: (1) <b><i>Christensen v. Harris County,</i></b> 529 U.S. 576 (2000); (2) <i><b>United States v. Mead Corporation</b></i>, 533 U.S. 218 (2001), and (3)<i> <b>Barnhart v. Walton</b></i>, 535 U.S. 212 (2002). For a good summary of these case and the current standing, see the article reference below by Kevin Michael Lewis.</font><br></div><div align="left"><br><br><font face="Arial" size="3">For more on the FDA and why it issues guidance documents, please see:</font><br><ul><li><font face="Arial" size="3">Erica Seiguer &amp; John J. Smith, <i><a href="https://www.cimit.org/news/regulatory/percep_process_fda.pdf">Perception and Process at the Food and Drug Administration: Obligations and Tradeoffs in Rules and Guidances</a></i>, Food and Drug Law Journal (2005)</font></li></ul><ul><li><font face="Arial" size="3">Kevin Michael Lewis, <i><a href="https://nrs.harvard.edu/urn-3:HUL.InstRepos:8592151">Informal Guidance and the FDA</a></i>, Harvard Law School Student Papers (2011)<br></font></li></ul></div><font face="Arial" size="3"><br></font>    
 
 
 
 
 
 ]]></description>
<link>http://melniklegal.com/weblog/1382574837_FAQ.html</link>
<guid>http://melniklegal.com/weblog/1382574837_FAQ.html</guid>
<pubDate>Wed, 23 Oct 2013 20:33:57 EST</pubDate>
</item>
			
			
			
<item>
<title><![CDATA[Florida Governor Signs New Data Breach Law Requiring All Businesses to Implement Security Controls]]></title>
<description><![CDATA[
 
 
 
 
     <font face="Arial">After being unanimously passed by the Florida legislature on April 30, 2014, on June 20, 2014, Florida's Governor Rick Scott signed the Florida Information Protection Act of 2014 (Act or FIPA). This Act repeals and wholly replaces Florida's existing data breach law (at Flat. Stat. Section 817.5681) with new Section 501.171. <b>FIPA takes effect on July 1, 2014.</b><br></font><br><table style="text-align: left; margin-left: auto; margin-right: auto;" border="0"><tbody><tr><td style="border: 1px solid #edad27; padding:3px;" color="#FFFFFF" size="3" bgcolor="#001c31" valign="top"><font face="Arial"><font face="Arial"><font color="#FFCC00"><b><i>A few preliminary comments....</i> </b></font><font color="#FFFFFF">This statute is a relatively sweeping change for Florida and raises the bar for other states. It applies to <u><i><b>every</b></i></u> business that handles "personal information" of Florida residents and requires these businesses to take proactive "reasonable measures" to secure data. But, like many other data breach and data security statutes, FIPA fails to define what it means to take "reasonable measures." In general, this means that companies need to follow industry best practices. As a starting point, businesses should conduct a risk analysis to better gauge their risks. FIPA also implements a records disposal requirement.<br><br>Given the increased liability brought about by this statute, Florida-based businesses that share data with other entities should review their contracts to ensure that data breach notification requirements are included together with appropriate cyberliability (<i>i.e.</i>, data breach) insurance requirements, damages caps, and indemnification language. Non-Florida based businesses that handle "personal information" of Florida residents should be aware that they too may be subject to the requirements can be pulled into court under the Florida Long-Arm Statute.<font size="2">[1]</font><br></font></font></font></td></tr></tbody></table><br><font face="Arial"><b>What Steps Should Companies Take?<br></b>Companies should consider taking a few proactive steps to gauge their risks and liabilities in light of the proactive requirement to take security measures, shortened deadline to provide data breach notification, and notification requirements for down-stream entities (e.g., business associates, vendors, contractors, etc.).</font><br><ul><li><font face="Arial">Under take a <font color="#993399"><u><b>risk analysis</b></u></font> to better assess potential risks and vulnerabilities to the confidentiality, integrity and availability of all personal information handled by the company</font></li></ul><ul><ul><li><font face="Arial">For a good starting point for a risk analysis, consider looking to the HIPAA materials and the NIST guidance documents</font></li></ul></ul><ul><li><font face="Arial">Review existing <font color="#993399"><u><b>privacy and security policies and procedures</b></u></font> and update as needed</font></li></ul><ul><ul><li><font face="Arial">Policies should reflect what the organization actually does and not what it would do in an ideal world. Policies that are in place but are not followed may demonstrate willful negligence and be the proverbial "smoking gun" in litigation</font></li></ul></ul><ul><li><font face="Arial">Develop an <font color="#993399"><u><b>incident response plan</b></u></font>, which should include a data breach notification plan</font></li></ul><ul><ul><li><font face="Arial" size="3">This plan should be called an "incident response plan" because <u><i>not</i></u> every incident is a breach. By calling something a "breach" your team may be attributing a legal meaning to an event that is merely a potential security incident. Keep in mind that the term "breach" is defined in the statue.</font><font face="Arial" size="3"> </font><br></li></ul></ul><ul><ul><li><font face="Arial">Any security incident is a stressful event. Having a plan in place, that at the very least contains important phone numbers for contacts who can assist you through the process will ease the stress a bit. Your attorney should be the first call because you never know what you are going to find.</font></li></ul></ul><ul><li><font face="Arial"><u><font color="#993399"><b>Encrypt personal information</b></font></u> to the extent possible and <b><i>definitely</i></b> <font color="#CC0000"><u><b>encrypt all mobile devices</b></u></font></font></li></ul><ul><ul><li><font face="Arial">The loss and theft of laptops is one of the leading causes of data breaches. Laptops should have hard drive encryption (as opposed to a separate drive that each employee should use to store personal information). If your company is using a Windows based product, check to see if BitLocker is available on the version you're using because it comes preinstalled in some Windows products and only needs to be enabled.</font></li></ul></ul><ul><ul><li><font face="Arial">Employee owned mobile devices that have access to "personal information" should be enrolled in a mobile device management system and the company should have <i>written authorization</i> from the employee to wipe the device, copy the device, seize it in the event of litigation, etc. <br></font></li></ul></ul><ul><ul><li><font face="Arial"><b>Encryption is particularly important because it pulls the information out of the definition of "personal information" and therefore also pulls it out of the breach notification requirement</b>.</font></li></ul></ul><ul><li><font face="Arial"><font color="#993399"><u><b>Identify all vendor and business relationship that impact "personal information" and review the existing contracts</b></u></font> to ensure that your business will receive timely notification in the event of an incident as well as cooperation during the investigation<br></font></li></ul><div align="left"><font face="Arial"><b>A Few Highlights from the New Law</b></font><br><ul><li><font face="Arial">Arguably, every organization is covered under the law because the definition of "covered entity" is quite broad: <br></font></li></ul><blockquote><blockquote><font face="Arial">“Covered entity” means a sole proprietorship, partnership, corporation, trust, estate, cooperative, association, or other commercial entity that <i><b>acquires</b></i>, <b><i>maintains</i></b>, <i><b>stores</b></i>, or <i><b>uses</b></i> personal information. For purposes of the notice requirements . . ., the term includes a governmental entity.</font><font face="Arial"><br></font></blockquote><font face="Arial">Those in the healthcare space will be familiar with the term "covered entity" but note that this provision covers every organization that </font><font face="Arial"><i><b>acquires</b></i>, <b><i>maintains</i></b>, <i><b>stores</b></i>, or <i><b>uses</b></i> personal information.</font></blockquote><ul><li><font face="Arial">The definition of personal information is quite broad and includes social security numbers, healthcare information, health insurance policy number, credit card numbers, and "a user name or e-mail address, in combination with a password or security question and answer that would permit access to an online account."</font></li></ul><ul><li><font face="Arial">There is a shorter timeline to notify affected Florida individuals - Under Florida's previous law, organizations were required to notify within 45 days. Now, it is "no later than 30 days after the determination of a breach or reason to believe a breach occurred" unless there is a law enforcement delay or "if, after an appropriate investigation and consultation with relevant federal, state, or local law enforcement agencies, the covered entity reasonably determines that the breach has not and will not likely result in identity theft or any other financial harm to the individuals whose personal information has been accessed.</font></li></ul><ul><li><font face="Arial">As noted above, covered entities must take proactive measures to protect the personal information. "Each covered entity, governmental entity, or third-party agent shall take reasonable measures to protect and secure data in electronic form containing personal information."</font></li></ul></div><ul><li><font face="Arial">There is no private right of action. But, a "violation of this section shall be treated as an unfair or deceptive trade practice in any action brought by the [Department of Legal Affairs (i.e., the Florida Attorney General)] under s. 501.207 against a covered entity or third-party agent." Civil penalties are not to exceed $500,000 and will go into the General Revenue Fund.</font></li></ul><ul><li><font face="Arial">FIPA includes a data records disposal provision. "Each covered entity or third-party agent shall take all reasonable measures to dispose, or arrange for the disposal, of customer records containing personal information within its custody or control when the records are no longer to be retained. Such disposal shall involve shredding, erasing, or otherwise modifying the personal information in the records to make it unreadable or undecipherable through any means." <br></font></li></ul><p><font face="Arial">The text of the new law is available here - <a href="https://laws.flrules.org/2014/189">https://laws.flrules.org/2014/189.</a></font></p><font face="Arial"><font size="2">---------------------<br>[1] Interestingly, the Florida legislature addressed the possibility of this in the "Bill Analysis and Fiscal Impact Statement" as follows:<br></font></font><blockquote><font face="Arial"><font size="2">Although the bill does not specifically provide that the covered entity must be conducting business in this state, the Florida Long-Arm statute may provide courts with the authority to assert personal jurisdiction over a nonresident covered entity. The statute enumerates a number of actions that a person or his or her representative may take that would submit that person to the jurisdiction of Florida courts. Those actions include, among other things, operating, conducting, engaging in, or carrying on a business venture in this state or having an office or agency in this state; committing a tortious act within this state; or breaching a contract in this state by failing to perform acts required by the contract to be performed in this state. A person may also become subject to the jurisdiction of a Florida court if the person is engaged in substantial and not isolated activity within Florida.</font></font><br></blockquote><font face="Arial"><font size="2">Florida Senate, </font></font><font face="Arial"><font size="2"><font face="Arial"><font size="2">Bill Analysis and Fiscal Impact Statement</font></font>: CS/SB 1524, April 1, 2014, <a href="https://www.flsenate.gov/Session/Bill/2014/1524/Analyses/2014s1524.pre.rc.PDF">https://www.flsenate.gov/Session/Bill/2014/1524/Analyses/2014s1524.pre.rc.PDF</a>.<br></font></font><font face="Arial"><font size="2"><br></font></font><font face="Arial"><font size="2"><font face="Arial"><font size="2">---------------------<br></font></font></font></font><br><font face="Arial"><font size="2"><font face="Arial"><font size="2"><font face="Arial"><font size="2">Posted by: Tatiana Melnik on June 27, 2014</font></font><br></font></font></font> </font>    
 
 
 
 
 
 ]]></description>
<link>http://melniklegal.com/weblog/1403923293_Data-Breach.html</link>
<guid>http://melniklegal.com/weblog/1403923293_Data-Breach.html</guid>
<pubDate>Fri, 27 Jun 2014 22:41:33 EST</pubDate>
</item>
			
			
			
<item>
<title><![CDATA[Florida Telemedicine - Status Update on SB 1646]]></title>
<description><![CDATA[
 
 
 
 
     <div align="left"><font face="Arial">The push for 
 telemedicine in Florida continues. The bill to create the Telemedicine 
 Act, SB 1646, is in appropriations as of April 11, 
 2014.<br><br>The bill would permit and thereby expand the 
 provision of healthcare services in Florida using telemedicine. 
 According to the bill summary, the bill 
 also:<br></font><ul><li><font face="Arial">creates s. s. 456.4503, F.S.; 
 <br></font></li></ul><blockquote><ul><li><font face="Arial">requiring specified practitioners providing 
 telemedicine services to patients in this state to be licensed in this 
 state; </font></li><li><font face="Arial">providing certain exceptions for emergency services and 
 consultations; authorizing non-Florida licensed physicians to meet 
 alternative requirements; </font></li><li><font face="Arial">requiring pertinent records to be made available upon 
 request; </font></li><li><font face="Arial">requiring other health care providers to be supervised 
 by a telemedicine provider; </font></li><li><font face="Arial">providing continuing education requirements for 
 telemedicine providers; </font></li><li><font face="Arial">establishing venue; providing applicability; 
 </font></li><li><font face="Arial">authorizing 
 the licensing boards to adopt rules; 
 </font></li></ul></blockquote><ul><li><font face="Arial"><font face="Arial">creates </font>s. 
 456.4504, F.S.; 
 <br></font></li></ul><blockquote><ul><li><font face="Arial">providing standards and prohibitions for the provision 
 of telemedicine services; 
 <br></font></li><li><font face="Arial">prohibiting nonemergency prescribing of a legend drug 
 without a physical 
 examination;</font></li><li><font face="Arial">prohibiting the prescription of a controlled substance 
 for chronic nonmalignant pain using telemedicine; 
 <br></font></li></ul></blockquote><ul><li><font face="Arial"><font face="Arial">creates </font>s. 
 456.4505, F.S.; 
 <br></font></li></ul><blockquote><ul><li><font face="Arial">authorizing the use of telemedicine services in the 
 diagnosis and treatment of the human eye; 
 <br></font></li><li><font face="Arial">providing requirements for the use of automated 
 equipment; <br></font></li><li><font face="Arial">requiring the owner or lessee of the automated equipment
  to maintain specified liability insurance under certain circumstances; 
 <br></font></li><li><font face="Arial">prohibiting prescriptions for spectacles or contact lens
  based solely on the use of an autorefractor; 
 <br></font></li></ul></blockquote><ul><li><font face="Arial"><font face="Arial">creates </font>s. 
 456.4506, F.S.; 
 <br></font></li></ul><blockquote><ul><li><font face="Arial"><b>providing requirements for reimbursement of 
 telemedicine services under the Medicaid program</b>; 
 </font></li><li><font face="Arial">requiring a 
 report to the Legislature on the usage and costs of telemedicine in 
 Medicaid by a certain date; </font></li><li><font face="Arial">providing for future repeal; 
 </font></li></ul></blockquote><ul><li><font face="Arial">amends s. 409.967, F.S.; 
 <br></font></li></ul><blockquote><ul><li><font face="Arial"><b>prohibiting a managed care plan under Medicaid
  from using telemedicine providers that are not physicians</b>; 
 </font></li></ul></blockquote><ul><li><font face="Arial">amends ss. 627.645 and 641.185, F.S.; 
 <br></font></li></ul><blockquote><ul><li><font face="Arial"><b>prohibiting the denial of a claim for payment 
 for medical services based on a medical necessity determination 
 conducted via telemedicine unless the determination is made by a 
 physician</b>; </font></li><li><font face="Arial">providing an effective 
 date.</font></li></ul></blockquote><div align="center"><font face="Arial"><img src="https://melniklegal.com/images/1398052667.jpg" height="420" width="623"></font><br></div><font face="Arial"><br>The full text of the bill is available here - 
 <a href="https://www.flsenate.gov/Session/Bill/2014/1646">https://www.flsenate.gov/Session/Bill/2014/1646</a>.<br><br><br><br><br><br><font size="2">Posted by Tatiana Melnik April 21, 
 2014.</font><br></font></div>    
 
 
   
 
 
 
 
 
 ]]></description>
<link>http://melniklegal.com/weblog/1398052813_Telemedicine.html</link>
<guid>http://melniklegal.com/weblog/1398052813_Telemedicine.html</guid>
<pubDate>Mon, 21 Apr 2014 00:00:13 EST</pubDate>
</item>
			
			
			
<item>
<title><![CDATA[Under the Florida Telemedicine Rule, Can a Physical be Conducted by Telemedicine?]]></title>
<description><![CDATA[
 
 
 
 
    <font face="Arial" size="3">Yes, a physical can be conducted via telemedicine under the Florida Standards for Telemedicine Practice (64B8-9.0141) provided that certain requirements are met. As the <a href="https://melniklegal.com/av/2014_10_09-FLBoM_Rules_Meeting_Report.pdf">Florida Board of Medicine conveyed in its Rules/Legislative Committee Meeting - Meeting Report</a> from its October 9, 2014 meeting:<br></font><blockquote><font face="Arial">At the August meeting, the Committee approved draft language for <font size="3">[the </font></font><font face="Arial"><font size="3"><font face="Arial" size="3">Florida Standards for Telemedicine Practice] </font></font>rule. Subsequently, the Board received additional comments which were presented for discussion by the Committee.<br><br>Mr. Tellechea referred to a letter from the Crystal Stickle with the Florida Hospital Association indicating concerns about a physical being conducted via telemedicine. He said he told her <b>a physical could be conducted via telemedicine if the patient already had a recent examination or if there is a licensed health care practitioner with the patient on one end who conducts the physical examination with the physician watching</b>. <br><br>After discussion, <b>the members agreed a physical could be conducted via telemedicine, but the standard of care is still the standard of care even if the examination is done via telemedicine</b>.<br><br>A motion was made, seconded and carried unanimously to recommend authorizing Mr. Tellechea to communicate the Committee’s comments to Ms. Sickle.<br><br>Mr. Tellechea then summarized the letter from JAPC. Afterwards, he suggested sending a letter to JAPC thanking them for the comments but leaving the language as currently written.<br><br>A motion was made, seconded and carried unanimously to recommend authorizing Mr. Tellechea to send a letter to JAPC thanking them for the comments but the Board does not want to change the language.</font><br></blockquote><font face="Arial"><font size="2"><br><br><br>Posted by Tatiana Melnik November 29, 2014.</font></font><br><br><font face="Arial" size="3"></font><font face="Arial">  </font>  
 
 
 
 
 
 ]]></description>
<link>http://melniklegal.com/weblog/1417321940_FAQ.html</link>
<guid>http://melniklegal.com/weblog/1417321940_FAQ.html</guid>
<pubDate>Sat, 29 Nov 2014 23:32:20 EST</pubDate>
</item>
			
			
			
<item>
<title><![CDATA[Another Day, Another App Development Company - and its Founder! - Settle with the FTC]]></title>
<description><![CDATA[
 
 
 
 
     <div align="left"><font face="Arial">The FTC announced today another settlement with a mobile app development company involving allegations of consumer deception. Interestingly, the complaint was against the company, Goldenshores Technologies, LLC, as well as the company's founder, Erik M. Geidl, individually. Additionally, the Consent Agreement, requires Mr. Geidl, individually, to notify the FTC in respect to any changes to his employment <u>during the next 10 years</u>. Clearly, the FTC is becoming much more serious about privacy compliance and consumer disclosures.</font><br><br><div align="left"><font face="Arial"><a href="#take">[Jump to Take-a-Ways]</a></font><br></div><br><table style="border: 0px solid red;"><tbody><tr><td><table border="0"><tbody><tr style="font-family: Arial;" align="center"><td><font size="3"><font size="2"></font></font><table style="text-align: left; margin-left: auto; margin-right: auto;" border="0"><tbody><tr><td valign="top"><font size="3">This action involves a popular mobile app called the "Brightest Flashlight Free" app, which consumers can use to turn their phone into a flashlight.&nbsp; (According to the FTC Complaint, the app was ranked as one of the top free apps on Google Play as of May 2013.)<br><br>The FTC alleged that the app transmitted various data from a user's mobile device to third parties, including advertising networks. "The types of data transmitted include, among other things, the device's precise geolocation along with persistent device identifiers that can be used to track a user's location over time."[1]<br><br></font><font face="Arial"><b>The FTC found the following disclosures or lack of disclosures problematic</b>:</font><br><ul><li><font face="Arial">While Goldenshores did include Google Play's general permission statements in pages promoting the app, it failed to explain "whether the application shares any information with third parties" [2]</font></li></ul><ul><li><font face="Arial">The Privacy Policy failed to disclose that the app "transmits or allows the transmission of device data, including precise geolocation along with persistent device identifiers, to third parties, including advertising networks" [3]</font></li></ul><ul><li><font face="Arial">Consumers are misled as to their choice to accept or decline the terms.</font></li></ul><ul><ul><li><font face="Arial">The app begins to transmit a user's precise geolocation and device identifiers immediately after it is installed.</font></li></ul></ul><ul><ul><li><font face="Arial">But, the EULA appears after app installation. While users can "Refuse" to accept the EULA, the app is already operating and sharing their information.</font></li></ul></ul></td><td style="border: 1px solid #edad27; padding:3px;" bgcolor="#001c31" valign="top" width="300px"><font color="#FFFFFF" size="3"><u><b>A Few Highlights<br></b></u></font><font color="#FFFFFF"><br><font size="3">- Action</font> is against the the mobile app development company <u>and</u> the majority owner <i>individually</i><br><br>- <i>Information shared</i>: geolocation of user and the user's device identifiers<br><br>- <i>Information shared with</i>: advertising network<br><br>- Problems: </font><br><blockquote><font color="#FFFFFF">1. Privacy Policy and EULA failed to fully disclose&nbsp; that the consumer's geolocation and device identifiers were shared with an advertising network;</font><font color="#FFFFFF"><br><br>2. While the EULA suggested that consumers could opt-out of the data sharing, the software was installed <i>prior to</i> users having the ability to opt-out, which resulted in their information being shared regardless of whether or not they agreed to the terms<br></font></blockquote><p><font color="#FFFFFF">- The consent order was with the company and the owner, where the owner must report his job and responsibilities to the FTC for 10 years.</font><br></p></td></tr></tbody></table></td></tr></tbody></table></td></tr></tbody></table><font face="Arial">The FTC acknowledged that the Privacy Policy and the EULA together advised consumers that the app "may periodically collect, maintain, process, and use information from users' mobile devices to provide software updates, product support, and other services to users related to the Brightest Flashlight App, and to verify users' compliance with [the] EULA."[4] <b>But</b>, the failure to notify customers that their precise geolocation and device identifiers would be shared with third parties was "in light of the representation made, was, and is, a deceptive practice."[5] </font><br><br><font face="Arial">Additionally, the representation that consumers could refuse to share their information "was, and is, false or misleading" because the app transmits the "device data as soon as the consumer launches the application and before they have chosen to accept or refuse the terms of the Brightest Flashlight EULA."[6]</font><br><br><font face="Arial"><i><b>The Problematic Privacy Policy Language</b></i>:</font><br><blockquote><font face="Arial">Consent to Use of Data. Goldenshores Technologies and its subsidiaries and agents may collect, maintain, process and use diagnostic, technical and related information, including but not limited to information about your computer, system and application software, and peripherals, that is gathered periodically to facilitate the provision of software updates, product support and other services to you (if any) related to the Goldenshores Technologies Software, and to verify compliance with the terms of the License. Goldenshores Technologies may use this information, as long as it is in a form that does not personally identify you, to improve our products or to provide services or technologies to you.<br></font></blockquote><font face="Arial">(For complete terms of the Privacy Policy, see Exhibit B-1). This language was also incorporated into the EULA.</font><br><br><b><font face="Arial">Excerpts from the Consent Order</font></b><br><br><font face="Arial">In the Consent Order, the FTC explicitly stated the steps that Goldenshores and Geidl must take to remedy the deceptive behavior:</font><br><blockquote><font face="Arial">[Goldenshores and&nbsp; Geidl] in connection with the advertising, promotion, offering for sale, sale, or dissemination of any mobile application that collects, transmits, or allows the transmission of geolocation information, in or affecting commerce, shall not collect, transmit, or allow the transmission of such information unless such application:</font><br></blockquote><blockquote><blockquote><font face="Arial">Clearly and prominently, immediately prior to the initial collection of or transmission of such information, and on a separate screen from, any final "end user license agreement," "privacy policy," "terms of use" page, or similar document, discloses to the consumer the following:</font><font face="Arial"><br></font><blockquote><font face="Arial">1. That such application collects, transmits, or allows the transmission of, geolocation information;</font><font face="Arial"><br><br>2. How geolocation information may be used;</font><font face="Arial"><br><br>3. Why such application is accessing geolocation information; and</font><font face="Arial"><br><br>4. The identity or specific categories of third parties that receive geolocation information directly or indirectly from such application; and</font><br></blockquote></blockquote><blockquote><font face="Arial">Obtains affirmative express consent from the consumer to the transmission of such information.</font> <br></blockquote></blockquote><blockquote><font face="Arial"></font><font face="Arial">[W]ithin ten (10) days from the date of entry of this Order, shall delete all Covered Information relating to Affected Consumers that is within their possession, custody, or control and was collected at any time prior to the date of entry of this Order. [The FTC specifically defined Covered Information mean everything:]</font><br></blockquote><blockquote><blockquote><font face="Arial">"Covered Information" shall mean information from or about an individual consumer, including but not limited to:<br></font><blockquote><font face="Arial"> <b>(a)</b> a first and last name; <br><br><b>(b)</b> a home or other physical address, including street name and name of city or town; <br><br><b>(c)</b> an email address or other online contact information, such as an instant messaging user identifier or a screen name; (d) a telephone number; <br><br><b>(e)</b> a Social Security number; <br><br><b>(f)</b> a driver's license or other state-issued identification number; <br><br><b>(g)</b> a financial institution account number; <br><br><b>(h)</b> credit or debit card information; <br><br><b>(i) </b>a persistent identifier, such as a customer number held in a "cookie," a static Internet Protocol ("IP") address, a mobile device ID, or processor serial number; <br><br><b>(j)</b> precise geolocation data of an individual or mobile device, including but not limited to GPS-based, WiFi-based, or cell-based location information ("geolocation information"); <br><br><b>(k)</b> an authentication credential, such as a username and password; or <br><br><b>(l) </b>any other communications or content stored on a consumer's mobile device.</font><br></blockquote></blockquote></blockquote><font face="Arial">Along with the relatively standard notification language the FTC has agreed to in previous consent agreements (i.e., company must notify is successors of this agreement, company must deliver a copy of this order to management, etc.), the document retention requirements, and the&nbsp; 20 year compliance period, this Consent Agreement also included the following:</font><br><blockquote><font face="Arial">IT IS FURTHER ORDERED that <b>respondent Erik M. Geidl, <font color="#990000">for a period of ten (10) years</font> after the date of issuance of this order, shall notify the Commission of the discontinuance of his current business or employment, or of his affiliation with any new business or employment</b>. The notice shall include respondent's new business address and telephone number and a description of the nature of the business or employment and his duties and responsibilities. Unless otherwise directed by a representative of the Commission in writing, all notices required by this Part shall be emailed to Debrief@ftc.gov or sent by overnight courier (not the U.S. Postal Service) to: Associate Director for Enforcement, Bureau of Consumer Protection, Federal Trade Commission, 600 Pennsylvania Avenue NW, Washington, DC 20580. The subject line must begin: In the Matter of Goldenshores Technologies, LLC, File No. 132-3087.</font><br></blockquote><b><font face="Arial"><a name="take"> Take-a-Ways</a></font></b><br><br><font face="Arial">There are a number of legal take-a-ways from the FTC's latest action. </font><br><ul><li><font face="Arial">Software developers and vendors must review their privacy policies. The FTC is serious about its enforcement efforts. These enforcement and consumer deception issues can be avoided with proper disclosures.</font></li></ul><ul><li><font face="Arial">Err on the side of more disclosure over less disclosure. Yes, it is true that sometimes this makes the design of user interfaces more complicated and delays the install process. This is particularly true for mobile apps where the screen size adds additional limitations. But, it is better to err on the side of giving more information to consumers, unless, of course, your desire is to enter into a consent agreement with the FTC.</font></li></ul><ul><li><font face="Arial">The consumer's choice to accept or reject the EULA or data sharing must be a 'true' choice. As such, disclosures need to be presented to the consumer either before the app is installed on the device</font></li></ul><font face="Arial">The Consent Agreement is subject to public comment for 30 days, beginning December 5, 2013 and continuing through January 6, 2014, after which the FTC Commission will decide whether to make the proposed consent order final.</font><br><br>-----------------<font face="Arial" size="2"><br>[1] <i>In the Matter of</i> Goldenshores Technologies, LLC, and Erik M. Geidl, FTC Complaint, FTC File No. 132 3087,&nbsp; 5 (Dec. 2013) [hereinafter FTC Complaint]. Documents available at <a href="https://www.ftc.gov/os/caselist/1323087/index.shtm">https://www.ftc.gov/os/caselist/1323087/index.shtm</a>.</font><font face="Arial" size="2"><br><br>[2] Id. at&nbsp; 7.<br><br>[3] Id. at&nbsp; 10.<br><br>[4] Id. at&nbsp; 15.<br><br>[5] Id.<br><br>[6] Id. at&nbsp; 17.<br><br>FTC's Press Release - <a href="https://www.ftc.gov/opa/2013/12/goldenshores.shtm">https://www.ftc.gov/opa/2013/12/goldenshores.shtm</a>. <br></font></div><div align="left"><br><br><br></div><font face="Arial"> </font>    
 
 
 
 
 
 ]]></description>
<link>http://melniklegal.com/weblog/1386269658_Mobile-Apps.html</link>
<guid>http://melniklegal.com/weblog/1386269658_Mobile-Apps.html</guid>
<pubDate>Thu, 05 Dec 2013 13:54:18 EST</pubDate>
</item>
			
			
</channel>
</rss>