The company should be sued into the ground. This is horrendous
Both the company, for failing to protect its users; and a large majority of its users, for doxxing and libel.
Its unfortunate that it happened this way, but now the people who are being libeled against and doxxed have the ability to find out about it where they didn’t before.
I mean, it’s on brand. The doxxing app is successfully doxxing people…
You get 89 cents in the settlement. Do you prefer to get a direct deposit or a check?
Nah, they just go bankrupt.
1 week free access to the service that did it in the first place is my favorite class action outcome.
It sucks for those people, but everyone should expect anything they say online to be possibly tied back to them. Secrets and identification information don’t mix. Especially online. The good news is that there is no evidence any of it is real, anyone can lie on the site saying whatever they want, so if doxed someone can just say they were bored and wanted to fit in and see what others were discussing or such. Hopefully for them it doesn’t turn into people getting hurt for talking behind someone’s back like it often does offline.
Everyone is talking about the poor security practices, which is fair. Or they are talking about the appropriateness of such an app existing, which is also fair.
But the immediate take away should be, especially in today’s political environment, that we cannot and should not trust sensitive data that leaves our device, particularly if you are of any kind of non privileged group.
the entire UK government disliked this comment
The UK government can shove it up their fucking arse.
Sincerely, A UK citizen.
This has been the case for a long time, so suddenly you have apps like Tea that encourage you to upload info of other people. So now even the few that take care not to upload their info can be nicely monitored. And the Gestapo does not even need to pay their informants for it.
And also men are vicious trash goblins.
You’re not adding much to the “this app is appropriate” argument.
Well the point of the app was to identify the small percentage of men who do most raoe Nd stuff, and even if the law wouldnt stop them, help potential victims avoid them, so as to not have to be guarded around every man one meets like hes a potential vicious rape monster, because some just are.
Im saying all men are garbage, and the fundamental oremise that you can under any conditions act like any number of men are human is foolish and likely to get you hurt. Which i think this situation show.
I don’t think anyone questions the “point” of the app. But the devil, as they say, is in the details.
Yeah. That all men are trash; avoiding the bad ones just leaves you with fred rogers and probably a second one at some point idk.
No no, you can’t walk that back now, Fred Rogers is trash too. You can’t even have one.
What gender do you identify as btw? Because from now on I’m going to assume all of that gender is just as garbage as your dumb ass.
This sounds like victim-blaming. This website didn’t even secure their database with a password. Come on. I’m sure their privacy policy gave the standard promises about storing their private data in a secure way, which they did not do.
Encouraging people to be safe and care about their privacy on the internet is not victim blaming.
I’m sure their privacy policy gave the standard promises about storing their private data in a secure way, which _they did not do. _
This is what people want to warn others of. The developers of Tea are hardly the only offenders. Definitely not an example of victim blaming.
In the current environment, at-risk people (women, immigrants, etc) who might have “at-risk” activities (abortion, immigration, etc) don’t have the luxury of relying on a privacy policy. I am not blaming them, I am simply stating how it must be if they are to avoid adverse actions.
This particular instance involved poorly secured data; what happens when warrantless demands are made by the government?
The Tea debacle proves that sensitive data cannot be trusted once out of your hands.
I agree. The reality is that nobody should be trusting these platforms with such sensitive data. As demonstrated, there is so much that can go wrong when you trust these companies. This is a LOT of risk for very little reward.
Whatever you put online you should think “what if this were made public and attributed to me” before you post it.
I’m sure their privacy policy gave the standard promises about storing their private data in a secure way, which they did not do.
Their ToS can be found here. Section G of their Limitation of Liability tries to shield them from liability against data breaches. But if they were criminally negligent, the ToS won’t protect them. The Data Protection section basically just says “check our Privacy Policy for info on what we collect”, which is pretty standard fare for a ToS.
The Security section of their Privacy Policy is also extremely boilerplate. Here’s the entire thing:
Security of Your Personal Information
The security of your Personal Information is important to us. When you enter sensitive information (such as credit card number) on our Services, we encrypt that information using secure socket layer technology (SSL).Tea Dating Advice takes reasonable security measures to protect your Personal Information to prevent loss, misuse, unauthorized access, disclosure, alteration, and destruction. Please be aware, however, that despite our efforts, no security measures are impenetrable.If you use a password on the Services, you are responsible for keeping it confidential. Do not share it with any other person. If you believe your password has been misused, please notify us immediately.This one particular sentence may end up burning them though:
Tea Dating Advice takes reasonable security measures to protect your Personal Information to prevent loss, misuse, unauthorized access, disclosure, alteration, and destruction.
I think most people (and the courts) would agree that putting a password on your database is a reasonable security measure that would be expected per this Privacy Policy. Especially since their next sentence goes on to elucidate that users should keep their passwords confidential.
This is why you don’t vibe code a webservice
This wasn’t vibe coding, it’s incompetant devops.
You have to go out of your way to make these buckets public like this. Several giant “Everyone will have access to this” warnings, re-authentication, a permanent warning symbol on the dashboard AND regular e-mails reminding you that you have a public bucket. I don’t even think you can do this via the API, it requires a human to manually make this setting.
I’m guessing that they couldn’t figure out how to configure the Access Control Lists and just made it public so that it would work. That’s fine in a test environment, without any user data but it’s pure incompetence to have a production system setup this way.
I’d say it’s not fine in a test environment, because then your test env S3 bucket is publicly available.
It’s not great, but it’s an acceptable kludge if you’re the one holding everyone back and you can’t figure out the problem immediately. Set it to public, let the devs get to work and research the problem until you find a real solution.
The test environment data should be generic so if someone were to discover the bucket they’ll get some pictures of cats and a bunch of people who live at 12345 anywhere street.
It’s a bad idea to leave your S3 perms wide open, because then anyone can use your S3 bucket for whatever reason they want, and it’ll hit your wallet. And if they can’t figure out basic IAM and ACLs, I’m also betting they can’t figure out “requester pays”
What? No, this is a horrible practice.
If you can’t figure out how to set identity-based ACLs you shouldn’t be working in technology! Oh I’ll just set this shit to any/any and figure out later. FUCK ANYONE WHO DOES THIS IN THEIR LEFT EAR.
They hired an investigator? Any investigator worth a shit is gonna say that they’re liable for failing to secure private data they collected,
as well as for retaining data they were apparently legally obligated to deleteEdit: Misread that segment, they actually presented it as if they were deleted to users, but apparently retained them to comply with vague “law enforcement requirements.”
On the one hand, sucks that a leak like this even happens anymore, no one deserves to be doxxed like that. On the other hand, I struggle to feel bad for the users of the doxxing app getting doxxed in return…
This is why age verification is dangerous. If a company can just forget to delete you ID picture, it will happen…
“Stop attacking us guys we just want to do a little misandry” -Tea app
What do you think is misandrist about this?
It’s an app about doxing people without their consent
To be fair, that alone wouldn’t be misandrist, if it weren’t exclusively for woman perpetrators targeting exclusively men as their victims.
I agree, a machine for doxing people in general is misanthropist, a machine for doxing men specifically is misandrist.
How are you defining “doxing” here?
At least they’re honest, they did spill tea.
A whole lot of tea.
Don’t want your information on the internet? don’t upload it to anyone on or over the internet, it really is a fucking simple concept.
Fucking simple concept which major businesses are economically compelled to gaslight you out of.
So the problem is in economics.
Each such business provides all of their infrastructure, expensive, good and well-maintained (Google has its own Internet cables), which is not separated from their application services.
So one provider of infrastructure (in the wide sense, solving all the problems) usually serves many users of their own application and many application providers (I’m inventing terms) without their own infrastructure.
While user of an application generally can’t switch infrastructure providers as they want. It’s kinda technically fine and normal (there are NTP server pools, one could in the olden days search many FTP servers for the needed file, and so on), but doesn’t happen IRL. Because there’s no standard way for pooling resources and tracking them, and there’s no applications using it.
So - the data model (cryptographic global person identities, globally identified by some derived hash posts (a post is, say, datetime, author, some tags, content, hash of it all, signatures, I dunno) (creation of a group or a vote or a changing of privileges or moderation can be a post too), for forming a representation for the user a group is “replayed” in the right order to know which user had a privilege to, say, moderate posts etc ; one can also generate group snapshots from time to time when replaying thus, by the group owner identity, to make it faster) is orthogonal to the service model. That’s important so that it were fit for alternative service models, like sneakernet or offline-enabled mesh or anything delay-tolerant. Or at least a p2p kademlia DHT-based service model.
The service model - the core of it all is a tracker service. It works like a tracker in BitTorrent (or maybe Hotline, but that’s old), except with signed announces, and it tracks search and storage and relay and maybe even computation services (which announce themselves to it). A search service gets storage services from trackers and indexes their contents (one can even announce objects to a search service similarly to trackers, might be better) to search by tags. A storage service just stores objects and yields them. A relay service must be harder, you the user must somehow announce (to trackers too?) which relay service you are registered on at this moment, a bit like SIP or like SMTP (only very temporary), so that messages to that relay service would reach you.
The client would just request a bunch of trackers for all things they need - to search for stuff for services, then request these services and merge their results. Forming a group representation is “searching for stuff” too, and then getting the objects referenced by index service responses from a bunch of storage services. To notify another user that you’ve sent them a message one can use a relay service.
I think it’s easy to see that it’s kinda primitive other than requiring proper cryptography. And it’s a global system working over the Internet (except no, it doesn’t exist). Similar to NOSTR, but I think better due to separation of data model and service model.
The advantages of this - one still can make any kinds of applications using such common infrastructure, but the resource-based feudalism we have this might hurt. Similar to how BitTorrent keeps working despite quite a few people not liking it.
The disadvantages - well, stuff will get lost, there are paid BT trackers but no paid BT peers, while in such a system paid storage and other services would be a thing (still much better than Facebook).
don’t upload it to the internet!
or use a smart phone
or corporate searches that track you
or go to any website with ads - they track you
hell don’t even search the internet! your ISP tracks dns requests
or use a modern tv that tracks what is on your screen
or you can do custom phone from - just unlock the bootloader, root it, and install! then just setup pihole/adguard/self-host everything
it’s simple, for privacy just go live in a yurt in the woods to not be tracked 24/7
Posted on an article about an app encouraging different users to upload info about you without your consent. Yes, really simple.
I strangle anyone who sees my face.
If you’re out of the loop, I found this article fairly helpful for a primer on the issues. It’s CNN, but I can’t be arsed to find a more kosher source.
https://www.cnn.com/2025/07/25/us/tea-app-dating-privacy-cec
404media did a great piece about what happened. available as podcast too. https://www.404media.co/a-second-tea-breach-reveals-users-dms-about-abortions-and-cheating/
Requires account
their podcast is freely available on spotify and such
I never thought there would be a dating intel war going on and this the second time too.
