@pheonix When I got a domain, I started giving a new mailbox for each new membership.
Oddly, the omly one that never got spammed is facebook-sold-me@(my domain) and you could have knocked me down with a feather, when I checked :-)
(I was on FB before it went toxic)
@RupertReynolds @pheonix This too. Years ago I would tell smaller orgs if I started getting stuff on an address only they had, but it was dissappointingly ineffective.
I never got a "that's concerning, we'll look into it" response, always "it can't have come from us, it must be you." In most cases I think they were honest and it was a bad actor on staff or an outside intruder - most likely poor data handling and a single hacked device.
These days, it's:
1. Small-to-medium-sized orgs ignoring your "don't spam me" flag. I can't forgive this - there's no excuse for internal mailing services "accidentally" forgetting to filter mailing lists, nor for marketing folk to have direct access to PII.
2. Mostly larger orgs that have been hacked with data released or sold publically. That's a persistent risk so I'll sometimes accept this, depending how they handle it.
Unfortunately, the personal address I give to friends and family is longstanding and gets spread to a lot of personal devices, and I don't like to filter it, so I end up getting a load of spam on that one.
@GerardThornley @RupertReynolds @pheonix For me it was never about telling a company something they either don’t want to hear or aren’t equipped to understand. It’s about killing that address after the transaction is done.
Especially nowadays where you don’t even have to wait for them to get hacked but they spam you to death with review requests and other needy bullshit.