AppZapper seems devious to me
Sometimes, you really just need to bite the bullet and admit the truth. Unfortunately, AppZapper isn’t going to do that.
For many years, my practice has been to create a unique e-mail alias for every company with which I e-mail regularly or need an address for a registration. Presently, there are nearly 150 address aliases defined.
The result of this effort is that I get practically no spam to my personal e-mail address, and when I do, it’s a pretty sure guarantee that I know who instigated.
It’s been many months—probably more than a year—since I’ve received any spam at all to any of my e-mail aliases. Yesterday, one came to an alias I had created for AppZapper, a utility that aids in removing preferences, caches, libraries, and more when uninstalling an application. Giving AppZapper the benefit of the doubt, I e-mailed to inform them that I didn’t appreciate my address being sold off for spam lists, but that if that didn’t happen, they may need to investigate a compromise in their database security.
The reply I got was essentially, “We don’t do that,” as in, they claim to not sell off e-mail lists.
Continuing to give them the benefit of the doubt, I responded to say they should investigate the breach since they do not sell e-mail lists, and I provided the complete source code of the e-mail and header.
The next reply from AppZapper was advice to contact my ISP (more correctly, my domain host), suggesting that the compromise is there. BZZZT. Wrong answer.
Seriously, I ask you: Spam arrives to a single e-mail alias among nearly 150 that have gone spam-free for a number of years. If a compromise of access to the database is the reason, where do you think that compromise occurred?
No, AppZapper, if the compromise was with my domain host, it is quite certain I’d be receiving spam to many of my e-mail aliases—not just the one for your product. Because of this dodge, I no longer believe a compromise is the explanation. If it were, you’d be willing to investigate and resolve the breach. By dodging the issue and blindly claiming it’s the fault of my domain host, I’m simply convinced that you do, in fact, avail e-mail lists to spammers.
Consequently, AppZapper will no longer live on my computers and any relevant venue I’m part of will hear about the shenanigans.
Moreover, a trusted friend has further reason to believe AppZapper has limited ethical standards. Apparently, AppZapper chose the Camino web browser as a sample application in its demonstrations for application removal. As a result, many users who don’t quite understand what’s going on are following the example and, expectedly, losing all their web site bookmarks. My friend, who is on the Camino development team, says they have repeatedly asked AppZapper to stop using them as an example, especially since AppZapper never asked permission in the first place. The requests have essentially fallen on deaf ears, and Camino support is getting the fallout of distraught users who’ve lost their bookmarks, caused by activities suggested by AppZapper. My friend’s supposition: “They’re probably assuming that we don’t have the legal resources to put up a fight if it comes to that. ‘Hey, let’s pick on an open-source example.'”
AppZapper is an AppFailure.