• 1 Post
  • 43 Comments
Joined 2 months ago
cake
Cake day: July 8th, 2024

help-circle



















  • Okay, what does a sweepstake or a contest have to do with a browser extension, made to spot fake reviews. Trade shows? What?

    I did take a look at this privacy policy before to check if the extension was worth installing, but holy fuck I didn’t see that.

    And they collect a lot of things, supposedly “automatically”. I have never developed a browser extension, but does the browser force this information on the extension? Do they just look at their data collection and find the geolocation of their users, how they accessed the extension download page, browser specifics etc.?

    They also sell your “automatically collected” geolocation data, “internet or other electronic network activity”, “inferences drawn from other personal information to create a profile about a consumer”, and “commercial information”. I’ve quoted the three data selling points I really don’t understand, since their “descriptions” aren’t very descriptive. But if we are to fully trust the lawful descriptions they provided, I hope the extension stays at 40,000 users really.

    FakeSpot’s privacy policy


  • Yeah, no problem at all. This is a lot better than people downvoting and not actually talking about what they disagree on. Felt like r/apple.

    Reading it again, Pocket’s privacy policy is actually not that bad. Thankfully it was not one of those 100 page ones that are made to confuse the shit out of consumers, but I have a slight problem with it.

    Personalized Advertising: Some Pocket web pages have ads. With your consent, Pocket’s ad partners will place advertising cookies on your device to personalize the ads you see here and on other websites.

    How does this consent exactly work? Is it just a simple check you have to tick in your account settings, or is it one of those cookie banners that require you to untick 800 advertising partners to “not give consent”? I’m not exactly a Pocket user so I’m a bit ignorant about it.

    Though there doesn’t seem to be another privacy concern with Pocket. It seems I had misconceptions about their practices.

    The one other problem I have with Pocket though is, it’s not a feature that should be in a browser, it should be an extension. They have already made a lot of extensions for features that not all of the userbase might need, even FakeSpot is currently an extension (approximately 40,000 users). I guess this is a whole another argument though.

    I will write my thoughts about FakeSpot in another reply.