Mobile

4/10/2018
10:07 AM
100%
0%

89% of Android Users Didn't Consent to Facebook Data Collection

A new survey shows most Android users did not give Facebook permission to collect their call and text data.

Facebook is in hot water as more users find out how much of their personal data the social media giant has collected. In a new study by anonymous social app Blind, 89% of 1,300 Android users claim they did not give Facebook permission to gather their call and text history.

Following news of the Cambridge Analytica scandal, Android users began investigating the extent of Facebook's data collection. They learned the company had been recording their call history records and SMS data, which the majority of them did not consent to. More than 30% of 2,600 users surveyed in March say they plan to delete their Facebook account, Blind reports.

Last week, Facebook shared several steps it's taking to cut back on the amount of data it pulls from Android. CTO Mike Schroepfer says call and text history is part of an opt-in feature for Messenger and Facebook Lite on Android devices. The purpose is so Facebook can surface frequent contacts, he says, and the content of message is not collected.

Read more details here.

Interop ITX 2018

Join Dark Reading LIVE for an intensive Security Pro Summit at Interop IT X and learn from the industry’s most knowledgeable IT security experts. Check out the agenda here. Register with Promo Code DR200 and save $200.

Dark Reading's Quick Hits delivers a brief synopsis and summary of the significance of breaking news events. For more information from the original source of the news item, please follow the link provided in this article. View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
BrianN060
50%
50%
BrianN060,
User Rank: Ninja
4/11/2018 | 12:15:19 PM
Informed consent
@Pyker42  Yes, ISVs are burdened with TOS and EULAs, as well.  Perhaps standardized agreement forms, at the  vetted distribution-store level, would help.  Part of the agreement would be that all permissions would be off by default - leaving the end user to enable each explicitly.  At the very least, the user would be made aware that all of the functionality they crave comes at a price; and that it's up to them to determine if it's worth it.  A benefit would be that while users would still have the responsibility to read the ToS/EULA/privacy notice, they'd only have to read ONE for any app they install from that store-vendor.  While that wouldn't cover the likes of Facebook, it could help the app publishers and end users.  
Pyker42
50%
50%
Pyker42,
User Rank: Strategist
4/11/2018 | 11:17:19 AM
Re: Comment
While I agree that TOS and EULA contracts are heavily weighted to favor the companies issuing them, that doesn't negate the fact that most users never read eaither before proceeding. Android is especially easy with permissions. Every new app gives you general categories with specific permissions granted to that app. There is blame to be put on companies like Facebook, Google, Apple, Microsoft, etc. But there is equal blame to be put on the people who use those services without realizing the implications of the data rights they are granting these companies. I agree that such services are ubiquitous and hard to eschew all together. That doesn't absolve people of their personal responibility to conciously think about what they are doing, what they are using, and what information they are sharing.
BrianN060
50%
50%
BrianN060,
User Rank: Ninja
4/10/2018 | 12:43:26 PM
Re: Comment
Important point.  In general, TOS have been very unfair to consumers.  It's not enough to include wording such as "Read the Terms of Service and Privacy Statements carefully before...".  For starters, how many consumers have the ability to evaluate what's written, as the contract law professionals who wrote it? Also, the more comprehensive the TOS agreement, the less likely consumers are inclined to read through it, or comprehend what of it pertains to them. 

 

Another factor is that a number of such services are, de facto, compulsory: events, webinars, conferences, etc., which are available exclusively through such services.  Does it matter what the TOS says, or if it's read, if there is no real choice but to accept? 
Pyker42
100%
0%
Pyker42,
User Rank: Strategist
4/10/2018 | 10:56:30 AM
Comment
I think that should read 89% of Android Users didn't know they consented to Facebook data collection.
Devastating Cyberattack on Email Provider Destroys 18 Years of Data
Jai Vijayan, Freelance writer,  2/12/2019
Up to 100,000 Reported Affected in Landmark White Data Breach
Kelly Sheridan, Staff Editor, Dark Reading,  2/12/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
5 Emerging Cyber Threats to Watch for in 2019
Online attackers are constantly developing new, innovative ways to break into the enterprise. This Dark Reading Tech Digest gives an in-depth look at five emerging attack trends and exploits your security team should look out for, along with helpful recommendations on how you can prevent your organization from falling victim.
Flash Poll
How Enterprises Are Attacking the Cybersecurity Problem
How Enterprises Are Attacking the Cybersecurity Problem
Data breach fears and the need to comply with regulations such as GDPR are two major drivers increased spending on security products and technologies. But other factors are contributing to the trend as well. Find out more about how enterprises are attacking the cybersecurity problem by reading our report today.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-8354
PUBLISHED: 2019-02-15
An issue was discovered in SoX 14.4.2. lsx_make_lpf in effect_i_dsp.c has an integer overflow on the result of multiplication fed into malloc. When the buffer is allocated, it is smaller than expected, leading to a heap-based buffer overflow.
CVE-2019-8355
PUBLISHED: 2019-02-15
An issue was discovered in SoX 14.4.2. In xmalloc.h, there is an integer overflow on the result of multiplication fed into the lsx_valloc macro that wraps malloc. When the buffer is allocated, it is smaller than expected, leading to a heap-based buffer overflow in channels_start in remix.c.
CVE-2019-8356
PUBLISHED: 2019-02-15
An issue was discovered in SoX 14.4.2. One of the arguments to bitrv2 in fft4g.c is not guarded, such that it can lead to write access outside of the statically declared array, aka a stack-based buffer overflow.
CVE-2019-8357
PUBLISHED: 2019-02-15
An issue was discovered in SoX 14.4.2. lsx_make_lpf in effect_i_dsp.c allows a NULL pointer dereference.
CVE-2013-2516
PUBLISHED: 2019-02-15
Vulnerability in FileUtils v0.7, Ruby Gem Fileutils <= v0.7 Command Injection vulnerability in user supplied url variable that is passed to the shell.