Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

admin
Pinned August 25, 2019

<> Embed

@  Email

Report

Uploaded by user
Some robocall blockers sent private data without permission
<> Embed @  Email Report

Some robocall blockers sent private data without permission

Jon Fingas, @jonfingas

August 10, 2019
 
Some robocall blockers sent private data without permission | DeviceDaily.com
 

As helpful as robocall blocking tools can be, they can sometimes create their own problems. NCC Group security researcher Dan Hastings has found that some of the more popular robocall blocking apps have been sending data to outside analytics firms without explicitly notifying you, if at all. Hiya and Truecaller sent device data before you could even accept their privacy policies, while TrapCall sent phone numbers without any mention in the privacy policy. Other apps sent info directly to Facebook the moment they loaded.

Some companies have responded. Truecaller told TechCrunch that it fixed data transmissions through an app update, while the TrapCall team changed its privacy policy after Hastings got in touch with Apple. Hiya said it didn’t transmit personal info, but was “strengthening our privacy even further” by ensuring that it didn’t send device data without your permission.

The data collection is frequently meant to monetize info, and that was (or for some, still is) part of the problem — the companies were profiting from privacy violations at the same time as they were protecting against intrusions into your life. Hastings also chastised Apple, accusing it of failing to review privacy policies and catch misuses like those from Hiya and Truecaller. This doesn’t mean that you should necessarily avoid robocall blockers (US carriers will increasingly do it themselves), but it could be important to review the policy before you trust the app with your call screening.

Engadget RSS Feed

(23)