Skip to main content

AVG TO SELL YOUR BROWSER HISTORY

Most of us use AVG, the third most popular antivirus product in the world according to expert market analysis. The antivirus company boasts about 9 percent share of the global market, 6 percent behind Avast and 13 percent behind Microsoft which stakes 23 percent of the market.[Source: OPSWAT]
Recently, the company has announced a change in its privacy policy in which it boldly and openly admits that it will collect user details and sell them to online advertisers for the purpose of continuing to fund its free antivirus products. This new privacy policy is expected to come into effect as from 15th October 2015.
Information expected to be collected includes:
§  ID associated with user device
§  Browsing and search history, including metadata; data that describes other data
§  User internet service provider and/or mobile network
§  Information regarding other user installed applications and how they are used
The antivirus company stated that it would not sell personal data like name, email addresses, addresses, or credit card details, but this sensitive information might sometimes leak inside the browsing history.
AVG’s previous privacy policy had stated that it could only collect data on "the words you search", but did not specify that browser history data could be collected and furthermore sold to third parties.
Security experts argue that this change places AVG antivirus squarely into the category of spyware. Users have been urged to uninstall the software as soon as they can because it is utterly unethical and an absolute abuse of the trust given to the security software.
As much as this is not too different from data mining conducted by Facebook or Google, the only difference is that AVG provides antivirus software with unrestricted access to our computers, with ability to spy into every file.


Whether users uninstall this antivirus or take AVG for their word is up to the end users themselves. It is however, cardinal to note that there are plenty of other alternative anti-virus programs out there to choose from that don’t sell user data to third parties.

Comments

Popular posts from this blog

OBIEE 11g Error "Selected item is not of valid selection type" In Agent When Select Dashboard Page For Content

OBIEE 11g Error"Selected item is not of valid selection type" This error applies to OBIEE - version 11.1.1.7.0 and later . When you try to choose a dashboard page for delivery content in an agent, it constantly fails with the error message " Selected item is not of valid selection type ”.  Solution: This error may happen, when there is an added extra space after the end of the name of the dashboard page. For example, instead of "PAGE", it is "PAGE   "  It may happen with a space at the beginning of the name also. Removal of the extra space by renaming the dashboard page will correct the error.

Setting User Defined JVM Memory Arguments in JDeveloper 11g Integrated WebLogic Server

Setting User Defined JVM Memory Arguments in JDeveloper 11g Integrated WebLogic Server This guide explains how to set your own predefined JVM memory arguments for the JDeveloper WebLogic container at startup for the integrated WebLogic server.   This will help avoid java.lang.OutOfMemoryError s experienced on heavy java processes and also improve on the integrated JDeveloper WebLogic server’s performance overall. Steps Locate the file: setDomainEnv.cmd which should be at: [JDeveloper Working Directory]\jdeveloper\system.xxx.xx.xx\DefaultDomain\bin                                 i.             Note: [JDeveloper Working Directory] will be "C:\Documents and Settings\<username>\Application...

DATAPUMP IMPORT HANGS AT INDEXES

  I initiated a  Datapump Import job at 11am.It took almost 30minutes to load all the tables but 8 hours later, the import log file shows that it's doing " Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX ",  so it means the import job has been hanging for almost 7.5 hours. Check dba_resumable view to see when the suspension happened SQL>select user_id,session_id, status, start_time, suspend_time,resume_time, error_msg from dba_resumable;  Check the error message. My error message was; ORA-01691: unable to extend lob segment XXXXXXXX by value in tablespace XXX   Solution:   SQL> alter tablespace XXX add datafile '/YOUR_PATH/XXX02.dbf' size 20M AUTOEXTEND ON NEXT 10M MAXSIZE UNLIMITED; You are good to go.