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

<channel>
	<title>Privacy Risk Report &#187; Privacy Law</title>
	<atom:link href="https://privacyriskreport.com/tag/privacy-law/feed/" rel="self" type="application/rss+xml" />
	<link>https://privacyriskreport.com</link>
	<description></description>
	<lastBuildDate>Fri, 03 Feb 2023 16:49:49 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>New Decision Provides Reminder Of Privacy Law Before The Pandemic</title>
		<link>https://privacyriskreport.com/new-decision-provides-reminder-of-privacy-law-before-the-pandemic/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=new-decision-provides-reminder-of-privacy-law-before-the-pandemic</link>
		<comments>https://privacyriskreport.com/new-decision-provides-reminder-of-privacy-law-before-the-pandemic/#comments</comments>
		<pubDate>Tue, 26 May 2020 15:13:06 +0000</pubDate>
		<dc:creator><![CDATA[Todd Rowe]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[cyber security]]></category>
		<category><![CDATA[Pandemic]]></category>
		<category><![CDATA[Privacy Law]]></category>

		<guid isPermaLink="false">https://privacyriskreport.com/?p=2137</guid>
		<description><![CDATA[<div class="e-mailit_top_toolbox">
<div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/new-decision-provides-reminder-of-privacy-law-before-the-pandemic/' data-emailit-title='New Decision Provides Reminder Of Privacy Law Before The Pandemic'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div>
</div>
</div>
<p>Over the last few months, cyber security issues may have taken a backseat to health and economic issues. Thankfully, there has not been a major cyber incident during the coronavirus pandemic. To pick up where we were before the pandemic, we... <a class="more-link" href="https://privacyriskreport.com/new-decision-provides-reminder-of-privacy-law-before-the-pandemic/">Continue Reading &#8594;</a>
<div class="e-mailit_bottom_toolbox">
<div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/new-decision-provides-reminder-of-privacy-law-before-the-pandemic/' data-emailit-title='New Decision Provides Reminder Of Privacy Law Before The Pandemic'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div>
</div>
</div>
<p>The post <a rel="nofollow" href="https://privacyriskreport.com/new-decision-provides-reminder-of-privacy-law-before-the-pandemic/">New Decision Provides Reminder Of Privacy Law Before The Pandemic</a> appeared first on <a rel="nofollow" href="https://privacyriskreport.com">Privacy Risk Report</a>.</p>
]]></description>
				<content:encoded><![CDATA[<div class="e-mailit_top_toolbox"><div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/new-decision-provides-reminder-of-privacy-law-before-the-pandemic/' data-emailit-title='New Decision Provides Reminder Of Privacy Law Before The Pandemic'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div></div>
</div><div>
<p lang="EN-US"><span lang="EN-US">Over the last few months, cyber security issues may have taken a backseat to health and economic issues. T</span><span lang="EN-US">hankfully, there has not been a major cyber incident during the coronavirus pandemic.</span><span lang="EN-US"> <a href="https://privacyriskreport.com/p-f-changs-leftovers-district-court-refuses-to-address-motion-to-dismiss-again-after-seventh-circuit-finds-plaintiffs-have-standing-in-data-breach-case/" target="_blank">To pick up where we were before the pandemic, we were closely analyzing the number of court decisions where it was found that a litigant could not establish standing to bring a lawsuit for a data breach</a>. However,<span lang="EN-US"> it is only a matter of time until we are agai</span><span lang="EN-US">n</span><span lang="EN-US"> analyzing privacy cases</span><span lang="EN-US">. </span>The recent decision in </span><em><span lang="EN-US">J</span><span lang="EN-US">antzer</span></em><span lang="EN-US"><em> v. Elizabethtown Community Hosp</em>.</span><span lang="EN-US">, </span><span lang="EN-US">2020 WL 2404764 (N.D. New York May 12, 2020), provides the perfect opportunity to get re</span><span lang="EN-US">acquainted with the fundamentals of data breach cases. </span></p>
</div>
<div>
<p lang="EN-US"><span lang="EN-US">In </span><em><span lang="EN-US">Jantzer</span></em><span lang="EN-US">, t</span><span lang="EN-US">he lead class action plaintiff claim</span><span lang="EN-US">ed</span><span lang="EN-US"> that </span><span lang="EN-US">an employee of Elizabethtown Community Hospital (“ECH”) fell prey to a phishing attack which resulted in the disclosure of patient personal information</span><span lang="EN-US">. The information exposed included “</span><span lang="EN-US">names, addresses, social security numbers, dates of birth, driver’s license numbers and medical information such as medical record numbers, dates of service and summaries of medical services provided.” (</span><span lang="EN-US">Id.</span><span lang="EN-US"> ¶ 16).</span><span lang="EN-US"> The Plaintiffs claim this breach resulted from ECH’s failure to adopt proper security measures including the following </span><span lang="EN-US">alleged </span><span lang="EN-US">failures:</span></p>
</div>
<ul>
<li>
<p lang="EN-US"><span lang="EN-US">To </span><span lang="EN-US">“take adequate and reasonable measures to ensure its data systems were protected,” </span></p>
</li>
<li>
<p lang="EN-US"><span lang="EN-US">To</span><span lang="EN-US"> “disclose that it did not have adequately robust computer systems and security practices,”</span></p>
</li>
<li>
<p lang="EN-US"><span lang="EN-US">To</span><span lang="EN-US"> “take standard and reasonable available steps to prevent the Data Bre</span><span lang="EN-US">a</span><span lang="EN-US">ch,” </span></p>
</li>
<li>
<p lang="EN-US"><span lang="EN-US">To </span><span lang="EN-US">“monitor and timely detect the Data Breach,” and </span></p>
</li>
<li>
<p lang="EN-US"><span lang="EN-US">To </span><span lang="EN-US">“provide Plaintiff &#8230; prompt and accurate notice of the Data Breach.”</span></p>
</li>
</ul>
<div>
<p lang="EN-US"><span lang="EN-US">Ronald Jantzer, the lead class action plaintiff, received notice that his personal information taken when he was a patient of the hosp</span><span lang="EN-US">ital, was exposed. In particular, ECH&#8217;s notice stated that while his name and “limited medical information” was compromised, his social security</span><span lang="EN-US"> number was not involved in the incident, and therefore, ECH </span><span lang="EN-US">acknowledged that it </span><span lang="EN-US">did not see any “financial risk”</span><span lang="EN-US"> related to the phishing incident.</span><span lang="EN-US"> ECH claimed that while the potential for harm was limited, the information </span><span lang="EN-US">“</span><span lang="EN-US">‘</span><span lang="EN-US">did contain limited information associated primarily with billing</span><span lang="EN-US">’</span><span lang="EN-US"> including </span><span lang="EN-US">‘</span><span lang="EN-US">information relating to the processing of payment from insurers: date of treatment, information identifying the insurer that provided reimbursement and payment dates and amounts.</span><span lang="EN-US">’</span><span lang="EN-US">”</span></p>
</div>
<div>
<p lang="EN-US"><span lang="EN-US">As commonly seen in breach cases, Jantzer claimed he </span><span lang="EN-US">“has spent time monitoring and protecting his financial well-being by, among other things, corresponding with the major credit bureaus.”</span><span lang="EN-US"> Jantzer further alleged that he expects to spend </span><span lang="EN-US">“significant amounts of time and money in an effort to protect [himself] from the adverse ramifications of the Data Breach and will forever be at a </span><span lang="EN-US">heightened risk of identity theft and fraud.”</span></p>
</div>
<div>
<p lang="EN-US"><span lang="EN-US">The initial step in </span><span lang="EN-US">this case involving the ECH breach</span><span lang="EN-US">—</span><span lang="EN-US">as with </span><span lang="EN-US">most breach cases</span><span lang="EN-US">—</span><span lang="EN-US">focuses on whether a plaintiff has “standing” to </span><span lang="EN-US">bring an action.</span><span lang="EN-US"> The ECH court first stated “[t]</span><span lang="EN-US">he Second Circuit has not yet addressed the issue of standing for a plaintiff alleging injury based on a data breach.”  Nevertheless, i</span><span lang="EN-US">t is well settled under cases such as <em>Lujan v. Defs. of Wildlife,</em> 504 U.S. 555, 560, 112 S. Ct. 2130, 119 L.Ed 2d 351 (1992)</span><span lang="EN-US">, </span><span lang="EN-US">to establish standing, (1) “the plaintiff must have suffered an ‘injury in fact’–an invasion of a legally protected interest,” (2) “there must be a causal connection between the injury and the conduct complained of,” and (3) “it must be likely, as opposed to merely speculative, that the injury will be redressed by a favorable decision.” </span><span lang="EN-US"> </span></p>
<p lang="EN-US"><span lang="EN-US">Here</span><span lang="EN-US">, Jantzer </span><span lang="EN-US">claimed </span><span lang="EN-US">he had </span><span lang="EN-US">standing </span><span lang="EN-US">to bring an action against ECH </span><span lang="EN-US">for at least two reasons</span><span lang="EN-US">: “</span><span lang="EN-US">(1) “the </span><span lang="EN-US">threa</span><span lang="EN-US">[t] of future harm is sufficiently imminent” and (2) he “has suffered an injury by time spent protecting himself.”</span><span lang="EN-US"> On the other hand, ECH argued Jantzer did not have standing since he </span><span lang="EN-US">“</span><span lang="EN-US">‘</span><span lang="EN-US">is unable to demonstrate any injury-in-fact” because [Jantzer] did not have sufficiently sensitive information stolen in the Data Breach and thus does not face </span><span lang="EN-US">‘</span><span lang="EN-US">a risk that is substantial or imminent.</span><span lang="EN-US">’</span><span lang="EN-US">”</span></p>
</div>
<div>
<p lang="EN-US"><span lang="EN-US">Based on the above, the <em>Jantzer</em> court first stated that, to resolve this matter, it “must determine whether the theft of Plaintiff’s personal information related to the date and amount of his treatment and his insurer, creates an imminent risk of identity theft.” </span><span lang="EN-US">In short, the <em>Jantzer</em> court held that plaintiff could not meet this standard, and, therefore, Jantzer could not allege the requisite injury, in fact, necessary for standing.</span><span lang="EN-US"> In particular, Jantzer was not able to pinpoint the exact injury he suffered related to the breach and “the harm of increased risk of future identity fraud too speculative to support standing in this case.” Consequ</span><span lang="EN-US">ently, the <em>Jantzer</em> court held Jantzer lacke</span><span lang="EN-US">d standing and granted ECH’s motions to dis</span><span lang="EN-US">m</span><span lang="EN-US">iss.  </span></p>
</div>
<div>
<p lang="EN-US"><span lang="EN-US">Finally, under the heading “Mitigation Efforts,” the <em>Jantzer</em> court also rejected Plaintiff’s “alternative basis for standing” where Plaintiff argues </span><span lang="EN-US">“</span><span lang="EN-US">that he has </span><span lang="EN-US">‘</span><span lang="EN-US">suffered an injury by time spent protecting himself.</span><span lang="EN-US">’</span><span lang="EN-US">”</span><span lang="EN-US">  The <em>Jantzer</em> court held these “expenses do not qualify as actual injuries where the harm is not imminent.”  </span></p>
<p lang="EN-US">It will be important to remember that breach incidents will not give rise to viable lawsuits unless litigants show precisely how they were damaged <a href="https://privacyriskreport.com/cyber-security-during-coronavirus-pandemic/" target="_blank">as privacy incidents grow with more people working from home</a> during the pandemic. While the <em>Jantzer</em> decision may not be a seminal privacy decision, this case serves as a reminder of where the law was prior to the pandemic and the fundamental concepts that control this area of law during and after the pandemic.</p>
<p lang="EN-US" style="text-align: center;">For more information, contact Tressler attorney <a href="https://www.tresslerllp.com/attorneys/attorney-details/todd-rowe" target="_blank">Todd Rowe</a> at <a href="mailto:trowe@tresslerllp.com" target="_blank">trowe@tresslerllp.com</a>.</p>
</div>
<div class="e-mailit_bottom_toolbox"><div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/new-decision-provides-reminder-of-privacy-law-before-the-pandemic/' data-emailit-title='New Decision Provides Reminder Of Privacy Law Before The Pandemic'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div></div>
</div><p>The post <a rel="nofollow" href="https://privacyriskreport.com/new-decision-provides-reminder-of-privacy-law-before-the-pandemic/">New Decision Provides Reminder Of Privacy Law Before The Pandemic</a> appeared first on <a rel="nofollow" href="https://privacyriskreport.com">Privacy Risk Report</a>.</p>
]]></content:encoded>
			<wfw:commentRss>https://privacyriskreport.com/new-decision-provides-reminder-of-privacy-law-before-the-pandemic/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Home On The Range: Recent Decision Addresses Range Of Data Breach Cases</title>
		<link>https://privacyriskreport.com/home-on-the-range-recent-decision-addresses-range-of-data-breach-cases/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=home-on-the-range-recent-decision-addresses-range-of-data-breach-cases</link>
		<comments>https://privacyriskreport.com/home-on-the-range-recent-decision-addresses-range-of-data-breach-cases/#comments</comments>
		<pubDate>Mon, 07 Oct 2019 16:45:48 +0000</pubDate>
		<dc:creator><![CDATA[Todd Rowe]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[data breach]]></category>
		<category><![CDATA[Privacy Law]]></category>
		<category><![CDATA[Privacy Risk Report]]></category>

		<guid isPermaLink="false">https://privacyriskreport.com/?p=1944</guid>
		<description><![CDATA[<div class="e-mailit_top_toolbox">
<div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/home-on-the-range-recent-decision-addresses-range-of-data-breach-cases/' data-emailit-title='Home On The Range: Recent Decision Addresses Range Of Data Breach Cases'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div>
</div>
</div>
<p>The recent decision in Kimbriel v. Abb, Inc.,19-CV-215 (October 1, 2019), provides insight into how far privacy law has developed in a short time. A couple of years ago there was little guidance as to what a plaintiff needed to... <a class="more-link" href="https://privacyriskreport.com/home-on-the-range-recent-decision-addresses-range-of-data-breach-cases/">Continue Reading &#8594;</a>
<div class="e-mailit_bottom_toolbox">
<div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/home-on-the-range-recent-decision-addresses-range-of-data-breach-cases/' data-emailit-title='Home On The Range: Recent Decision Addresses Range Of Data Breach Cases'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div>
</div>
</div>
<p>The post <a rel="nofollow" href="https://privacyriskreport.com/home-on-the-range-recent-decision-addresses-range-of-data-breach-cases/">Home On The Range: Recent Decision Addresses Range Of Data Breach Cases</a> appeared first on <a rel="nofollow" href="https://privacyriskreport.com">Privacy Risk Report</a>.</p>
]]></description>
				<content:encoded><![CDATA[<div class="e-mailit_top_toolbox"><div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/home-on-the-range-recent-decision-addresses-range-of-data-breach-cases/' data-emailit-title='Home On The Range: Recent Decision Addresses Range Of Data Breach Cases'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div></div>
</div><p>The recent decision in <em>Kimbriel v. Abb, Inc</em>.,19-CV-215 (October 1, 2019), provides insight into how far privacy law has developed in a short time. A couple of years ago there was little guidance as to what a plaintiff needed to establish standing in a data breach case. <a href="https://privacyriskreport.com/p-f-changs-leftovers-district-court-refuses-to-address-motion-to-dismiss-again-after-seventh-circuit-finds-plaintiffs-have-standing-in-data-breach-case/" target="_blank">Many data breach lawsuits were dismissed as courts found the nexus between the breach and the alleged damages to be too weak or speculative to support a viable cause of action</a>. The <em>Kimbriel</em> decision provides a “range” for plaintiffs to show they have standing to bring a lawsuit after a breach. First, the <em>Kimbriel</em> court finds plaintiffs cannot meet their burden to establish standing if they cannot show breached data was used or reasonably could be used after the breach. For example, credit inquiries using breached data is not sufficient to establish standing under the <em>Kimbriel </em>court’s reasoning. On the other end of the range, to meet their burden, plaintiffs will need to show they suffered an injury-in-fact and have standing when they can show criminals used their data. For example, plaintiffs that can show fraudulent credit cards were open with the breached information have a better chance of establishing standing to sue.</p>
<p><strong>The Plaintiffs’ Allegations Related To The Breach Of Personal Information </strong></p>
<p>In <em>Kimbriel</em>, the Defendant, the Plaintiffs’ employer, filed a motion to dismiss the Plaintiffs’ complaint asserting the Defendant breached employee data. Plaintiffs claimed the breach involved a database that housed employees’ sensitive information including full names, addresses, birth dates and social security numbers plaintiffs provided to Defendant in order to participate in an employee health plan. After the breach, the Defendant agreed to pay for identity credit monitoring services for the employees. On February 13, 2019, a credit-monitoring service notified the lead plaintiff, Paula Kimbriel, of five unauthorized credit inquiries with banking institutions.</p>
<p><strong>The Defendant’s Argument That Plaintiffs Lack Standing For This Action</strong></p>
<p>On the other hand, the Defendant argued in its motion to dismiss that Plaintiffs lack standing under Article III of the U.S. Constitution to bring this action because they have not alleged an injury-in-fact. That is, it is well settled by the U.S. Supreme Court that “[t]o establish standing, plaintiffs must show they have suffered an injury-in-fact-an injury that is “concrete, particularized, and actual or imminent[.]” <a href="https://lawfare.s3-us-west-2.amazonaws.com/staging/s3fs-public/uploads/2013/02/11-1025_ihdj.pdf">See, </a><em><a href="https://lawfare.s3-us-west-2.amazonaws.com/staging/s3fs-public/uploads/2013/02/11-1025_ihdj.pdf" target="_blank">Clapper v. Amnesty Int’l USA</a>.</em> The<em> Clapper</em> court held the injury-in-fact must be “fairly traceable to the challenged action[,] and redressable by a favorable ruling.” <em>Id.</em> Threatened injuries cannot be speculative, but “must be certainly impending.” <em>Id.”</em> Questions related to standing have plagued many data breach plaintiffs to the extent it is difficult to show damage (such as credit card fraud) is directly related to a particular breach. The <em>Kimbriel</em> court address this question by creating a range that examines the damage from a breach.</p>
<p><strong>The District Court’s Dismissal Of The Complaint </strong></p>
<p>The District Court dismissed the Plaintiffs’ complaint finding the District Court lacked subject-matter jurisdiction over the plaintiffs’ claims.  In particular, the District Court held that without any allegations the hacked personal information had or will be used, in identity theft or fraud, the employees are not capable of demonstrating a concrete injury.</p>
<p>The District Court found this case fell in the middle of two recent decisions that “address injury-in-fact in the data privacy context.”  First, <em>Beck v. McDonald, 848 F.3d 262 (4th Cir. 2017)</em>, provides an example where “the plaintiffs did not have standing because, critically, they could neither show that their data was actually used nor allege enough plausible facts to show that threatened future harms were “certainly impending.”   The plaintiff’s allegations in the <em>Beck</em> case were fatally defective since the “mere compromise of personal information, without more, fails to satisfy the injury-in-fact element in the absence of an identity theft.”</p>
<p>On the other end of the range, the court in <em>Hutton v. Nat&#8217;l Bd. of Examiners in Optometry, Inc. </em><a href="https://casetext.com/case/hutton-v-natl-bd-of-examiners-in-optometry-inc-1" target="_blank"><em>Hutton v</em>. <em>Nat’l Bd. of Examiners in Optometry, Inc.,</em> 892 F.3d 613 (4th Cir. 2018)</a>, found “plaintiffs had suffered an injury-in-fact because their data had actually been used to open fraudulent credit card accounts.</p>
<p>Here, the District Court found the Plaintiffs’ allegations in the <em>Kimbriel </em>case were closer to the allegations brought by the plaintiffs in <em>Beck</em> rather than the allegations in <em>Hutton</em>  That is, Plaintiffs’ complaint in <em>Kimbriel </em>did not establish the District Court had standing since, “[b]y plaintiffs’ own admission, the credit inquiries do not, by themselves, constitute an independent injury-in-fact.”  Further, the District Court rejected the argument that the credit inquiry coupled with allegations that the breach was a result of a targeted phishing scheme, “constitute a sufficient factual basis to conclude there is a certainly impending risk of identity theft.”</p>
<p>While the District Court found the Plaintiffs in <em>Kimbriel </em>presented a stronger case for an injury-in-fact than the plaintiffs in <em>Beck,</em> “their asserted injuries are still too speculative to meet the ‘certainly impending’ threshold” necessary to support their claim.</p>
<p><strong>What The <em>Kimbriel</em> Decision Tells Us About Privacy Law</strong></p>
<p>We can expect other courts to adopt a similar analysis to that seen in <em>Kimbriel</em> as data breach cases continue to reach the courts.  Thankfully, not every data breach results in damage to the individuals that had their information compromised. This decision provides an important reminder that not every data breach results in damages.</p>
<p>For more information, contact Tressler attorney <a href="https://www.tresslerllp.com/attorneys/attorney-details/todd-rowe" target="_blank">Todd Rowe</a> at <a href="mailto:trowe@tresslerllp.com" target="_blank">trowe@tresslerllp.com</a>.</p>
<div class="e-mailit_bottom_toolbox"><div class="e-mailit_toolbox square size32 " data-emailit-url='https://privacyriskreport.com/home-on-the-range-recent-decision-addresses-range-of-data-breach-cases/' data-emailit-title='Home On The Range: Recent Decision Addresses Range Of Data Breach Cases'>
<div class="e-mailit_btn_Facebook"></div>
<div class="e-mailit_btn_Twitter"></div>
<div class="e-mailit_btn_Send_via_Email"></div>
<div class="e-mailit_btn_Pinterest"></div>
<div class="e-mailit_btn_LinkedIn"></div>
<div class="e-mailit_btn_EMAILiT"></div></div>
</div><p>The post <a rel="nofollow" href="https://privacyriskreport.com/home-on-the-range-recent-decision-addresses-range-of-data-breach-cases/">Home On The Range: Recent Decision Addresses Range Of Data Breach Cases</a> appeared first on <a rel="nofollow" href="https://privacyriskreport.com">Privacy Risk Report</a>.</p>
]]></content:encoded>
			<wfw:commentRss>https://privacyriskreport.com/home-on-the-range-recent-decision-addresses-range-of-data-breach-cases/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
