Zombie cookie

Web analytics collecting companies use cookies to track Internet usage and pages visited for marketing research.[1] Sites that want to collect user statistics will install a cookie from a traffic tracking site that will collect data on the user. As that user surfs around the web the cookie will add more information for each site that uses the traffic tracking cookie and sends it back to the main tracking server.

Zombie cookies allow the web traffic tracking companies to retrieve information such as previous unique user ID and continue tracking personal browsing habits. When the user ID is stored outside of a single browser's cookie storage, such as in a header injected by the network into HTTP requests, zombie cookies can track users across browsers on the same machine.[2]

Zombie cookies are also used to remember unique IDs used for logging into websites. This means that for a user that deletes all their cookies regularly, a site using this would still be able to personalize to that specific user.

A user that doesn't want to be tracked may choose to decline 3rd party cookies or delete cookies after each browsing session.[3] Deleting all cookies will prevent some sites from tracking a user but it may also interfere with sites that users want to remember them. Removing tracking cookies is not the same as declining cookies. If cookies are deleted this causes the data collected by tracking companies to become fragmented. For example, counting the same person as two separate unique users would falsely increase this particular site's unique user statistic. This is why some tracking companies use a type of zombie cookie.

According to TRUSTe: "You can get valuable marketing insight by tracking individual users' movements on your site. But you must disclose your use of all personally identifiable information in order to comply with the Fair Information Practices guidelines".[4]

Possible places in which zombie cookies may be hidden include:

• Standard HTTP cookies
• Storing cookies in and reading out web history
• Storing cookies in HTTP ETags
• Internet Explorer userData storage (starting IE9, userData is no longer supported)
• HTML5 Session Storage
• HTML5 Local Storage
• HTML5 Global Storage
• HTML5 Database Storage via SQLite
• Storing cookies in RGB values of auto-generated, force-cached PNGs using HTML5 Canvas tag to read pixels (cookies) back out
• Local shared objects (Flash cookies)
• Silverlight Isolated Storage
• Cookie syncing scripts that function as a cache cookie and respawn the MUID cookie[5]
• TCP Fast Open
• TLS's Session ID

If a user is not able to remove the cookie from every one of these data stores then the cookie will be recreated to all of these stores on the next visit to the site that uses that particular cookie. Every company has their own implementation of zombie cookies and those are kept proprietary. An open-source implementation of zombie cookies, called Evercookie,[6] is available.

In 2015, TURN, an online advertising clearinghouse,[7] introduced zombie cookies based on Flash Local Shared objects.[8] Privacy advocates quickly denounced the technology.[9]

An academic study of zombie cookies was completed in 2009, by a team of researchers at UC Berkeley,[10] where they noticed that cookies which had been deleted, kept coming back, over and over again. They cited this as a serious privacy breach. Since most users are barely aware of the storage methods used, it's unlikely that users will ever delete them all. From the Berkeley report: "few websites disclose their use of Flash in privacy policies, and many companies using Flash are privacy certified by TRUSTe".[10]

Ringleader Digital made an effort to keep a persistent user ID even when the user deleted cookies and their HTML5 databases. The only way to opt-out of the tracking, was to use the company's opt-out link, which gives no confirmation.[11] This resulted in a lawsuit against Ringleader Digital.

The term "zombie cookie" was created by Attorney Joseph H. Malley who initiated the Super-Cookie Class Actions in 2010. The etiology of the phrase was derived from his prior research into Apple's third-party iPhone applications. Some of these which had been criticized as being "zombie-like" applications such as the "super-cookies" which "re-spawned" when deleted. Attorney Malley envisioned a cookie that seemed to come back from the "dead". Blending the two ideas, he first coined the phrase Zombie Cookies within his filed Class Actions, as a means to enable the court, jury, and public understand the basis of the litigation.^{[citation needed]}

The Zombie Cookie lawsuits were filed suit in the United States District Court for the Central District of California against Quantcast, Clearspring, VideoEgg, and affiliated sites owned by Walt Disney Internet Group, Warner Bros. and others. According to the charges, Adobe Flash cookies are planted to "track Plaintiffs and Class Members that visited non-Clearspring Flash Cookie Affiliates websites by having their online transmissions intercepted, without notice or consent".[12]

Two "supercookie" mechanisms were found on Microsoft websites in 2011, including cookie syncing that respawned MUID cookies.[5] Due to media attention, Microsoft later disabled this code.[13]

Consumer outrage related to Flash cookies and violation of consumers' privacy caused U.S. Congressional Hearings, led by Senators Al Franken and John Rockefeller. Reportedly, the "Zombie Cookie", aka Flash Cookie filings, forced Adobe Systems Inc. to stop processing flash cookies on 98% of all consumers' computing devices.[14]

The online advertising clearinghouse TURN implemented zombie cookies on Verizon mobile phones, using a hidden, unremovable number by which Verizon could track customers. After an article by ProPublica revealed this fact in January 2015, TURN claimed it had suspended usage of their zombie cookies.[7]

• Device Fingerprint - Site that demonstrates the way zombie cookies are restored