In a privacy disaster that absolutely should not have happened, Amazon pushed an update to its wishlist feature that accidentally exposed users' home addresses to anyone viewing their public wishlists.
The issue, first spotted by users on social media, meant that people sharing wishlists publicly - a common practice for creators, streamers, and people celebrating birthdays - were inadvertently broadcasting their physical addresses to the internet. Not their city or general area. Their actual street addresses.
Let me be clear: this is Programming 101 level stuff. Personal identifiable information should have multiple layers of protection and review before any feature ships. The fact that Amazon, with all its resources and supposed technical excellence, shipped this to production is embarrassing.
What makes this particularly frustrating is that wishlists are inherently meant to be shared. Content creators use them so fans can send gifts. People share them for weddings, baby showers, birthdays. Amazon created a feature designed for public sharing, then failed to properly sanitize the data being exposed.
Amazon has since fixed the issue, but that doesn't help users whose addresses were already scraped by bad actors. And make no mistake, the moment this went live, people were absolutely harvesting that data. Address information is valuable to scammers, stalkers, and anyone else with ill intent.
The most infuriating part? This was completely preventable. Amazon has an address system that already knows how to hide your exact location while still allowing delivery. They use it for Amazon Locker, for gift shipping, for all sorts of features. The infrastructure was already there.
This incident is a reminder that even the biggest tech companies ship code that hasn't been properly reviewed for privacy implications. In the rush to iterate and update features, basic security considerations get overlooked.
For users, the lesson is unfortunately familiar: assume any data you put into a platform could become public, because eventually, through negligence or breach, it probably will. And for Amazon? Maybe slow down and audit your privacy protections before pushing updates to features used by millions.
The technology is mature enough to protect user privacy. The question is whether companies care enough to implement it correctly.
