Zoom updates its iOS app to remove Facebook SDK after concerns were raised over Zoom's failure to disclose Facebook data sharing in privacy policy
or Facebook, for that matter. https://twitter.com/... @dhh : What's astounding about this privacy policy is just how transparent Zoom is about the nastiness of adtech. That data provided by Zoom to Google will be combined with other sources, and this stew of plundered data is then sold to the highest bidder for as targeting. Abeba Birhane / @abebab : Zoom Removes Code That Sends Data to Facebook. The change comes after Motherboard found the Zoom iOS app was sending analytics information to Facebook when users opened the app. https://www.vice.com/... via @vice Manu Kumar / @manukumar : Zoom announced today that it's removing @Facebook's SDK from it's app. When we were building the @HiHello app we consciously chose NOT to use the Facebook SDK, even though it would give better conversion tracking. Wish more app devs would boycott FB. https://blog.zoom.us/... Guilherme Rambo / @_inside : That's why you need to audit every SDK you add to your app. It's your app, it's your responsibility. https://www.vice.com/... https://twitter.com/... Ed Bott / @edbott : Zoom is a hot mess. Basically early Dropbox. https://twitter.com/... @brendaneich : @josephfcox Shadow profile created with fingerprint, if fingerprinting could not uniquely identify an FB user who has never logged into Zoom via FBID? Or bucketing to set of profiles if fingerprinting was close but not unique? Enquiring minds want to know. Cc: @robleathern in case he knows. Allison Keene / @keenetv : What is with everyone's sudden Zoom obsession? It's basically malware. Why not use something that already has all of your data, like Google Hangouts? https://www.vice.com/...
Context & Ripple Effects
The day before this update, Motherboard reported via VICE that the Zoom iOS app was sending analytics data to Facebook every time it opened — even for users with no linked Facebook account — and that Zoom's privacy policy never clearly disclosed the practice. The removal of the Facebook SDK is Zoom's direct response to that reporting.
It also fits a pattern: in July 2019, Zoom only shipped a fix for a flaw letting a malicious link activate the Mac camera after public backlash over its initial refusal, per Wired's coverage of that reversal. Privacy fixes at Zoom have consistently followed exposure rather than preceded it.
First-order effects
- iOS users opening Zoom no longer trigger analytics transmissions to Facebook, and Zoom must now reconcile its privacy policy with an app that shares nothing with Facebook rather than one that did so silently.
- Facebook loses a stream of device and usage data from one of the fastest-growing apps of the moment, since the SDK fed it information regardless of whether users had accounts there.
Second-order effects
- Every developer shipping the Facebook SDK faces the same question Motherboard put to Zoom — what leaves the device at app open — because the coverage stresses this behavior is common across apps using the SDK, not unique to Zoom.
- App-store and enterprise buyers evaluating video conferencing tools gain a concrete differentiator, pressuring rivals like Google Hangouts to document their own SDK data flows or risk the same exposé.
Third-order effects
- If backlash-driven patching keeps defining Zoom's privacy posture — from the Mac camera fix to this SDK removal — the company is pushed toward the kind of dedicated security-and-privacy release cycle it later adopted with its 5.0 update focused exclusively on encryption and call controls.
- The episode strengthens the case that undisclosed third-party SDK data sharing becomes a disclosure and governance problem for the whole app ecosystem, not a per-company embarrassment.
The trend: Consumer apps are being forced by investigative reporting and user backlash to strip third-party adtech SDKs and treat privacy disclosure as a product requirement rather than legal fine print.