DO NOT TRACK

Most popular Internet browsers, such as Firefox and Internet Explorer, now have an option called “do not track.”  The function of “do not track,” is, if selected, to supposedly allow users to opt out of tracking by websites they haven’t visited.  The sites that would typically be tracking web users, without their knowledge, include analytics services, advertising networks, and social platforms.  
The way it works is when the web browser requests or sends content using a HTTP, a header is included either (DNT: 1) meaning do not track, or (DNT: 0) which means the user has consented to being tracked.  A third option occurs when a user has not chosen to either opt in or opt out, then the request is null and no header is added.   


The implementation of “do not track” works solely on the honor system, and since websites are not required by law to comply with DNT requests, few actually honor these requests.   Still some websites respond to the DNT indication, Twitter being one of the major companies that chooses to recognize the signal.  Out of 211 third party trackers investigated, only one honored a “do not track” request, concluded a Keynote Systems study. 

What can be seen as a downside to the absence of advertisers tracking web users is that the user will still see ads, but they will continue to see the same irrelevant ads repeated.  To avoid this, the World Wide Web Consortium has supported “frequency capping”, which will allow advertisers to track even those with an activated DNT enough to prevent the users from seeing repeated ads. 

Microsoft initially announced that the new Internet Explorer 10, which will be shipped with Windows 8, would have the “do not track” header turned on by default.  Microsoft’s announcement infuriated many online advertisement companies and groups, who use tracking as a way to better target their customers with ads that would be most likely to appeal to them. 

However, this new default setting on IE 10 would not be compliant with Do Not Track’s specification that requires the explicit consent of each individual user of the service, meaning that the users would have to enable the anti-tracking feature in their browsers themselves. The specifications suggest that the user be prompted to set their tracking preference on first launch of the browser. The specification proposal has not yet been accepted fully by the W3C Tracking Protection Working Group, but it is likely to be approved.

VISIT:- REDZONE DIGITAL SECURITIES

Comments

Popular posts from this blog

AntiCloud Trojan Reverse Engineering Analysis

SQL Injection: The Equal Opportunity Vulnerability

Secure Sockets Layer (SSL)