And then said browser extension, which promised to never ever sell your data to a third party, got bought out by PayPal for 4 billion USD.
Really makes you think.
I guess selling the whole company owning the data isn't technically selling data to third parties...
Law enforcement.. What do you want them to do? Turn down a legal court order and say "naaa"?
Why not? The alternative is to allow a business model, in which you start a company with the sole purpose of vacuuming up data and delivering it to highest bidder by getting acquired.
Have a transition window (say 3 months) before the sale goes into effect where users get to choose to either keep the account and allow the new owner access to the data, or to have their data destroyed. After that window, data from anyone who didn't respond gets deleted.
Go to jail or shutdown the site, like the Lavabit guy.
>We know how important your personal data is to you, so we will never sell it. We'll only share it with your consent or in ways you'd expect (as we explain here). That means we will share your data if needed to complete your purchase, with businesses who help us operate Honey, or if we are legally required to do so.
>We may also share information in the following cases:...with our parent company, PayPal, Inc. and affiliates and subsidiaries it controls, but only for purposes allowed by this Privacy Policy;
So that sounds like commercial use of personal data is specifically protected with regards to the new parent. The policy does specify they can share your data in an "aggregate or anonymized format" without any caveats, though.
Sure does still raise the question of what PayPal spent $4bn on. From what I can read online, online retailers see a lot of benefit from the way Honey incentivizes users to complete a purchase instead of abandon the cart.
I think the weasel is this nibble here:
> but only for purposes allowed by this Privacy Policy;
The privacy policy is between the user and Honey, not the user and PayPal, which implies they are still legally separate entities ("parent company"). Unless Honey has an agreement with Paypal that it can audit and enforce - which as a subsidiary, why would it want to - then once PayPal has the data, its actual use of it is governed by the privacy policy between the user and PayPal if there is an existing relationship or ???
It sounds like all Honey and Paypal need to do is find a half plausible justification from the PP for the data transfer; once it's handed over, Paypal is basically free to do whatever it wants.
As the affiliate, the insights are invaluable. Imagine you hosted a sleep blog and directed people to a particular memory foam pillow. If you saw they ended up purchasing a different pillow, you could change the link to better serve your readers.
Or if you saw that they ended up purchasing essential oils, perhaps you’d want to write a post about using oil diffusers to fall asleep.
The affiliate link tracking is supposed to give you a better picture of your audience. Usually it works, but getting 50M views from every source on the internet is obviously a case where there’s no common “audience”.
The site owner only sees that 35 people bought book X while 24 people bought book Y.
If someone runs a tiny blog that they attempt to monetize with affiliate links, and one of their only readers at the moment is their mother, I don't think they'd be happy seeing that one of their readers purchased a sex toy.
[1] By "honest", I mean like a pop-up with a question or two and a clear "Not now" button. Not another cookie banners or passive collection.
If I buy a memory foam pillow from company B instead of company A then I don't want company A to know at all. If I wanted company A to know then I would tell company A why I didn't purchase its product.
Maybe it was that I didn't see company A's product. Or maybe it's because company A is a piece of garbage. Maybe it's because company A employs deceptive practices and I don't want to give company A my money.
Also, imagine it's not Amazon but a much smaller website. Just bringing a client (someone who actually paid) is already a good deal.
So, I believe it's a totally fair commission rule.
> To be clear, I have no problem with affiliates getting commission on random stuff.
The problem is disclosing random purchases. You can pay a commission without that disclosure.
Luckily, Amazon scrubs any identifying info from their affiliate reports. So say I post an affiliate link to a book and then look in Google Analytics to see 50 readers clicked the link. The next day, I can log into Amazon's report and see I had 50 clicks and 30 sales of the book along with an addition sale of 40 toys, 10 movies, and 3 dildos.
However, I can't actually see which of my 50 readers bought what, if anything. Those 3 dildo purchases are completely anonymized, along with everything else. However, being told I also sold 40 toys really helps me because it lets me know I should probably start writing more about toys since that's what my readers are buying.
I'm also limited to 200 unique Amazon "tags", so I can't assign a unique tag to each of my readers to track them individually.
Works anywhere else where the audience can be identified, and click frequency is low.
/s
Anyone else find this a pretty gross violation of privacy on Amazon’s part? Why should your unrelated purchases be disclosed to affiliates just because you clicked an affiliate link for whatever reason? Let’s say the affiliate website use accounts or know the identities of users through another channel, and track outbound clicks. With few enough clicks, they can exactly correlate your unrelated purchases with you, if I understand this correctly. In fact it seems you can easily prank unsuspecting acquaintances this way.
To be clear, I have no problem with affiliates getting commission on random stuff.
Edit: I can also see why the data could be valuable to marketers.