This might not be deliberate, but a result of chrome hitting various google services automatically. You could clear all your cookies and have them actually delete, and then a few seconds later it might do a browser or extension update check, hitting a google URL, which results in cookies getting set. Not that this is necessarily better if true (speculation on my part), because it would mean that google's tracking is built into the browser itself, and it wouldn't need you to ever visit a google website - or even a site that uses a google service or hosted script.
Or depending on how they tested this, they might have had gmail or some other google website open and one of its automatic ajax requests resulted in cookies getting set. If so, they're dumb and don't know how this stuff works.
view the rest of the comments →
absurdlyobfuscated ago
This might not be deliberate, but a result of chrome hitting various google services automatically. You could clear all your cookies and have them actually delete, and then a few seconds later it might do a browser or extension update check, hitting a google URL, which results in cookies getting set. Not that this is necessarily better if true (speculation on my part), because it would mean that google's tracking is built into the browser itself, and it wouldn't need you to ever visit a google website - or even a site that uses a google service or hosted script.
Or depending on how they tested this, they might have had gmail or some other google website open and one of its automatic ajax requests resulted in cookies getting set. If so, they're dumb and don't know how this stuff works.