zlacker

[parent] [thread] 3 comments
1. pc+(OP)[view] [source] 2020-04-21 19:55:53
https://stripe.com/privacy describes what we do in some detail (including disclosing that we use this kind of browsing data).

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'm patrick@stripe.com.)

replies(2): >>jonny_+Q >>ThePhy+Oh1
2. jonny_+Q[view] [source] 2020-04-21 20:02:32
>>pc+(OP)
Why not address it here publicly? I don't think you want/expect everyone observing this discussion on HN to reach out to you.
replies(1): >>pc+J1
◧◩
3. pc+J1[view] [source] [discussion] 2020-04-21 20:09:08
>>jonny_+Q
Oh, offer was made in case GP wants to have a deeper discussion/back-and-forth than is readily achievable with an online forum. Timing constraints notwithstanding, we work hard to answer questions on HN too.
4. ThePhy+Oh1[view] [source] 2020-04-22 09:18:47
>>pc+(OP)
For your European customers you should likely make it more clear what stripe.js does before urging them to install it on every page of their website. Using it as soon as a user has a probable interest to purchase a product (e.g. when he/she clicks on “Register” and chooses a plan) would very likely be acceptable as a legitimate interest under GDPR, tracking all users even if they don’t have a clear intent of purchasing something and e.g. only want to get information about the product will definitely not be acceptable as a legitimate interest and would therefore require clear consent first.
[go to top]