<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>Kalium</author><text>I am not an attorney. This is not legal advice.&lt;p&gt;Based on a plain reading of the law, several things about CalOPPA stand out to me. For one, it&amp;#x27;s not clear to me that the mouse movements in question qualify as &amp;quot;personally identifiable information&amp;quot;. Mouse movements are not a first or last name, physical or email address, SSN, telephone number, or any contact method I am familiar with (maybe you know a way?).&lt;p&gt;Second, it seems to me that opt-out, right to inspect and update, and more are all contingent upon the data being PII within the scope of CalOPPA. Perhaps you can help me with something I&amp;#x27;ve overlooked that would show me where I&amp;#x27;ve erred?&lt;p&gt;Further, what do you think the correct legal and ethical way for Stripe to use mouse movement data would be? From your comment I can guess that you believe it should be treated as PII. Is that correct?</text><parent_chain><item><author>threepio</author><text>Stripe customer here. The question raised is, more broadly, &amp;quot;Is Stripe collecting this data in a legal and ethical way?&amp;quot; This too can be readily answered in the negative.&lt;p&gt;It doesn&amp;#x27;t matter whether &amp;quot;Stripe.js collects this data only for fraud prevention&amp;quot; or if it works in practice. Under CalOPPA [1], Stripe still has to disclose the collection of the data, and (among other things) allow customers to opt out of collection of this data, and allow customers to inspect the data collected. Stripe&amp;#x27;s privacy policy refers to opt-out and inspection rights about certain data, but AFAICT not this.&lt;p&gt;[This is not legal advice]&lt;p&gt;[1] &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;leginfo.legislature.ca.gov&amp;#x2F;faces&amp;#x2F;codes_displayText.xhtml?lawCode=BPC&amp;amp;division=8.&amp;amp;title=&amp;amp;part=&amp;amp;chapter=22.&amp;amp;article=&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;leginfo.legislature.ca.gov&amp;#x2F;faces&amp;#x2F;codes_displayText.xh...&lt;/a&gt;&lt;p&gt;[2] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;stripe.com&amp;#x2F;privacy#your-rights-and-choices&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;stripe.com&amp;#x2F;privacy#your-rights-and-choices&lt;/a&gt;</text></item><item><author>pc</author><text>Stripe cofounder here. The question raised (&amp;quot;Is Stripe collecting this data for advertising?&amp;quot;) can be readily answered in the negative. This data has never been, would never be, and will never be sold&amp;#x2F;rented&amp;#x2F;etc. to advertisers.&lt;p&gt;Stripe.js collects this data only for fraud prevention -- it helps us detect bots who try to defraud businesses that use Stripe. (CAPTCHAs use similar techniques but result in more UI friction.) Stripe.js is part of the ML stack that helps us stop literally millions of fraudulent payments per day and techniques like this help us block fraud more effectively than almost anything else on the market. Businesses that use Stripe would lose a lot more money if it didn&amp;#x27;t exist. We see this directly: some businesses don&amp;#x27;t use Stripe.js and they are often suddenly and unpleasantly surprised when attacked by sophisticated fraud rings.&lt;p&gt;If you don&amp;#x27;t want to use Stripe.js, you definitely don&amp;#x27;t have to (or you can include it only on a minimal checkout page) -- it just depends how much PCI burden and fraud risk you&amp;#x27;d like to take on.&lt;p&gt;We will immediately clarify the ToS language that makes this ambiguous. We&amp;#x27;ll also put up a clearer page about Stripe.js&amp;#x27;s fraud prevention.&lt;p&gt;(Updated to add: further down in this thread, fillskills writes[1]: &lt;i&gt;&amp;quot;As someone who saw this first hand, Stripe’s fraud detection really works. Fraudulent transactions went down from ~2% to under 0.5% on hundreds of thousands of transactions per month. And it very likely saved our business at a very critical phase.&amp;quot;&lt;/i&gt; This is what we&amp;#x27;re aiming for (and up against) with Stripe Radar and Stripe.js, and why we work on these technologies.)&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=22938141&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=22938141&lt;/a&gt;</text></item></parent_chain></comment><story><title>Stripe records user movements on its customers&apos; websites</title><url>https://mtlynch.io/stripe-recording-its-customers/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>pc</author><text>&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;stripe.com&amp;#x2F;privacy&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;stripe.com&amp;#x2F;privacy&lt;/a&gt; describes what we do in some detail (including disclosing that we use this kind of browsing data).&lt;p&gt;More broadly, I assure you that Stripe.js and our fraud prevention technologies are very carefully designed with full compliance with the relevant California (and other) statutes in mind. I’d be happy to connect you with our legal team if you’d like to discuss this in more detail. (I&amp;#x27;m patrick@stripe.com.)</text><parent_chain><item><author>threepio</author><text>Stripe customer here. The question raised is, more broadly, &amp;quot;Is Stripe collecting this data in a legal and ethical way?&amp;quot; This too can be readily answered in the negative.&lt;p&gt;It doesn&amp;#x27;t matter whether &amp;quot;Stripe.js collects this data only for fraud prevention&amp;quot; or if it works in practice. Under CalOPPA [1], Stripe still has to disclose the collection of the data, and (among other things) allow customers to opt out of collection of this data, and allow customers to inspect the data collected. Stripe&amp;#x27;s privacy policy refers to opt-out and inspection rights about certain data, but AFAICT not this.&lt;p&gt;[This is not legal advice]&lt;p&gt;[1] &lt;a href=&quot;http:&amp;#x2F;&amp;#x2F;leginfo.legislature.ca.gov&amp;#x2F;faces&amp;#x2F;codes_displayText.xhtml?lawCode=BPC&amp;amp;division=8.&amp;amp;title=&amp;amp;part=&amp;amp;chapter=22.&amp;amp;article=&quot; rel=&quot;nofollow&quot;&gt;http:&amp;#x2F;&amp;#x2F;leginfo.legislature.ca.gov&amp;#x2F;faces&amp;#x2F;codes_displayText.xh...&lt;/a&gt;&lt;p&gt;[2] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;stripe.com&amp;#x2F;privacy#your-rights-and-choices&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;stripe.com&amp;#x2F;privacy#your-rights-and-choices&lt;/a&gt;</text></item><item><author>pc</author><text>Stripe cofounder here. The question raised (&amp;quot;Is Stripe collecting this data for advertising?&amp;quot;) can be readily answered in the negative. This data has never been, would never be, and will never be sold&amp;#x2F;rented&amp;#x2F;etc. to advertisers.&lt;p&gt;Stripe.js collects this data only for fraud prevention -- it helps us detect bots who try to defraud businesses that use Stripe. (CAPTCHAs use similar techniques but result in more UI friction.) Stripe.js is part of the ML stack that helps us stop literally millions of fraudulent payments per day and techniques like this help us block fraud more effectively than almost anything else on the market. Businesses that use Stripe would lose a lot more money if it didn&amp;#x27;t exist. We see this directly: some businesses don&amp;#x27;t use Stripe.js and they are often suddenly and unpleasantly surprised when attacked by sophisticated fraud rings.&lt;p&gt;If you don&amp;#x27;t want to use Stripe.js, you definitely don&amp;#x27;t have to (or you can include it only on a minimal checkout page) -- it just depends how much PCI burden and fraud risk you&amp;#x27;d like to take on.&lt;p&gt;We will immediately clarify the ToS language that makes this ambiguous. We&amp;#x27;ll also put up a clearer page about Stripe.js&amp;#x27;s fraud prevention.&lt;p&gt;(Updated to add: further down in this thread, fillskills writes[1]: &lt;i&gt;&amp;quot;As someone who saw this first hand, Stripe’s fraud detection really works. Fraudulent transactions went down from ~2% to under 0.5% on hundreds of thousands of transactions per month. And it very likely saved our business at a very critical phase.&amp;quot;&lt;/i&gt; This is what we&amp;#x27;re aiming for (and up against) with Stripe Radar and Stripe.js, and why we work on these technologies.)&lt;p&gt;[1] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=22938141&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=22938141&lt;/a&gt;</text></item></parent_chain></comment><story><title>Stripe records user movements on its customers&apos; websites</title><url>https://mtlynch.io/stripe-recording-its-customers/</url></story>