4 ms·
I worked at WhatsApp between 2011 and 2019. This FAQ had very specific instructions for how to opt out of sharing that were only available for a limited amount
by toast0 5y ago
I worked at WhatsApp between 2011 and 2019. This FAQ had very specific instructions for how to opt out of sharing that were only available for a limited amount of time. The FAQ serves as documentation of the product and there's no need to keep online specific instructions that can no longer be followed.
In order to opt out, you needed to have an existing account and take specific actions around the time you agreed to the 2016 new terms of service. Based on the internet archive, this article was removed after April 20, 2018, and before May 5, 2018. When it was most likely obsolete (I don't recall the specific deadlines for accepting the 2016 TOS)
On the plus side, the various terms of services are all available without digging in the internet archive https://www.whatsapp.com/legal/terms-of-service/revisions https://www.whatsapp.com/legal/terms-of-service/revisions
- nextaccountic 5y agoThe news here is that you can't choose to not share data with Facebook anymore.
- warkdarrior 5y ago... as of 2018.
- Someone 5y agoIt’s not practical for most, but I think you can, by moving to the European Region. Comparing https://www.whatsapp.com/legal/updates/terms-of-service/?lang=en https://www.whatsapp.com/legal/updates/terms-of-service/?lan... to https://www.whatsapp.com/legal/terms-of-service-eea/?lang=en https://www.whatsapp.com/legal/terms-of-service-eea/?lang=en, the EU version removes - “Ways To Improve Our Services. We analyze how you make use of WhatsApp, in order to improve our Services, including helping businesses who use WhatsApp measure the effectiveness and distribution of their services and messages. WhatsApp uses the information it has and also works with partners, service providers, and affiliated companies to do this” - “We offer specific features and services to businesses and other organisations such as providing them with statistics regarding their use of our Services.” - “Affiliated Companies. We are part of the Facebook Companies. As part of the Facebook Companies, WhatsApp receives information from, and shares information with, the Facebook Companies as described in WhatsApp's Privacy Policy, including to provide integrations which enable you to connect your WhatsApp experience with other Facebook Company Products; to ensure security, safety, and integrity across the Facebook Company Products; and to improve your ads and products experience across the Facebook Company Products. Learn more about the Facebook Companies and their terms and policies here.”
- zwaps 5y agoIt is utterly naive to think that Facebook does not plainly ignore the regulations here. They have done it everywhere else. And once the data is in the model, the Goose is cooked. Who cares about a few million fine? In fact, Facebook would be irrational not to train their algorithms on every single data point, regulations and opt outs be damned. And that people itt have found that their data says opt in no matter what they pressed in 2016 is believable evidence for that. As always: Don’t forget what Facebook has done in terms of data leaks, political skew, impact on the pandemic and damage of teenagers on instagram. Do not forget how well they kept this under wraps and how little remorse they have, except in proportion to the fine. Given the past years, we know that people working at Facebook are literally mustache-twirling cartoon villains, and I wish this was exaggerated.
- jeltz 5y agoIt would be a couple of hundred million fine, but otherwise you are right. The issue with GDPR fines is that while they stop companies from continuing to do the exakt same thing (because they would be fined every year until they stop) it can still be worth the fine if you gain enough market share from violating regulations.
- helloworld11 5y agoThese kinds of behaviors won't really change until governments finally pull their heads out of their asses and ensure that regulatory violations above a certain threshold are aimed squarely at imprisoning or personally fining certain key decision makers inside a company. You know, actual people inside its structure, not just the monstrosity as a bloated, extremely wealthy business entity that can and will absorb fines as nothing more than a cost of doing business.. That they fine the corporate entity as well, sure, why not but that they also explicitly make it known that they will seek criminal charges against actual human beings who made specific choices and decisions to ignore certain major rules. Even if the top brass cover their asses with lawyers under such a regime, asking any subordinate to break rules will always be weighed with the question of "and will I be one of the ones who gets literally jailed for this being uncovered in court?" That wholly new chain of consequence-weighing might at least make blatant disregard for legal limitations more problematic for everyone at a company like FB and so many others. It might also make the leadership hesitate more because they'll rarely be sure if an employee they asked to do something illegal isn't also gathering evidence against them as he or she violates the rules under their orders. Punishing malfeasance by applying nothing more than fines to multi-billion dollar corporate entities as abstractions is absurd nonsense. And it's funny in its hypocrisy, considering how "tough on big corporations" is a popular politician's theme that gets votes, only to be forgotten by both politicians, and apparently, voters as well once someone is in a position to make rules with real weight.
- ourdramadotnet 5y agoI hope the salary was worth it
- duskwuff 5y ago> I don't recall specific deadlines for accepting the 2016 TOS Based on what I see in the archived article, it looks like accepting the TOS was a "roadblock" popup in the app -- you couldn't continue using the app without accepting the terms. Any accounts which hadn't accepted the terms after two years could have simply been closed for inactivity.
- toast0 5y agoThere was a process, you had to have a new enough client to get prompted, and once prompted there was a later option available for some amount of time before you were roadblocked. So if you were running an older version, the question becomes when did that version expire, forcing an upgrade to a version with the prompt, and then how long did you have from there to accept the terms. And, if you had an eligible account, you had 30 days after accepting the terms to opt out of the sharing. You could probably look at the many news articles that were written back then to get some idea of the timelines. Although, most news articles weren't written with the perspective of delaying terms acceptance as much as possible. (Also, I had meant to say I didn't recall the specific deadlines... There certainly were deadlines given specific circustances of each account)
- crossroadsguy 5y agoIs there a way to check what option is enabled on my account? Sharing or not sharing?
- toast0 5y agoAFAIK, it's in the GDPR report, but was never visible otherwise (including when the opt out was offered; once you opted out, you couldn't opt in or confirm that you opted out)
- mPReDiToR 5y agoI never accepted the ToS and still get the popup ~20% of the times I open the client. Everything is still working. I just hit "<" when it pops up.
- p49k 5y agoI specifically and carefully made sure I opted out of this sharing in 2016, and when I requested my data years later, I was marked as "opted in". I don't trust that Facebook honestly honored or correctly tracked this option for anyone.
- tailspin2019 5y agoThis matches my experience with Facebook “opt outs”.
- endofreach 5y agoI wonder: what did you and your team do most of the time? I mean there haven‘t been too many crazy new features. How was privacy handled in the first few years?
- toast0 5y agoMy official work was server side verification. Sending codes to people via SMS and Voice. So that's evaluating new SMS/voice providers, checking that the current ones are working, tracking down issues, working with carriers to setup direct SMPP connections for SMS (which thankfully got offloaded to the FB Mobile Partner team), supporting carrier deals. Figuring out how to make it as easy as possible for users to input codes (including working to make the messages readable for platform APIs that allow automatic/assisted code entry) But even though that's a lot of things and is super important, most days there wasn't urgent work on that, and I'm pretty good at debugging weird stuff, so I debugged a lot of weird stuff. When you have millions (or billions) of users, 'one in a million' stuff happens a lot. Diagnosing bugs in FreeBSD and fixing them (or convincing upstream to fix them), diagnosing bugs in client platforms and finding workarounds (also trying to get them fixed, but it's hard to get a lot of movement even when bugs are general and just nobody else diagnosed it), diagnosing bugs in ISP networks and finding workarounds (almost nobody follows through on email to whois contacts, even if you're sending from @whatsapp.com), diagnosing issues in our hosting provider's network and convincing them to fix it, etc. If I had stayed longer, I'd have probably started diagnosing bugs in the FB infra and Linux, but I more or less left when we were almost done with our FreeBSD hosts and it took a while to wind down everything, so it was a good transition point to more or less not touch the service where it was running on FB. In terms of privacy, I'm not going to say much. I think it's fair to say our goal was to only have the necessary private information to provide service. Messages aren't kept on the server beyond delivery, have a limited time frame waiting for delivery, address book is numbers only, no names, etc. Signal certainly stores less information on the server than WhatsApp. You can certainly read about our many failures (no client to server encryption, then poor encryption, and eventually good encryption) among other well reported issues. End to End Encryption took a long time to develop and deploy, but it sets a bar that hopefully other providers will meet (or exceed).