Feeds

Google vows to delete Chrome's unique client ID

After it's installed on your PC

Choosing a cloud hosting partner with confidence

Google is changing the way it handles the unique identifier that accompanies each installation of its Chrome browser.

As noticed by H-Online, a Google white paper (pdf) says the company will now delete the unique ID after the browser updates itself for the first time.

Google has confirmed with The Reg that the change will be made with the upcoming Chrome 4.1. A 4.1 beta was released earlier this month.

Google's white paper says the token will now be used solely to verify a successful install. "In order to measure the success rate of Google Chrome downloads and installations, a randomly-generated token is included with Google Chrome's installer," it reads. "This token is sent to Google during the installation process to confirm the success of that particular installation."

As it stands, Google lays down the unique identifier in the Chrome installation folder, but it says this is not linked to personal data and that it is merely used to check for updates and report crashes back to the company. It is reassigned each time the browser is updated.

With Chrome 4.1 it will still appear on the user's machine, but it will then be deleted after the initial update. "It's about time," reads a blog post from Mozilla director of community development Asa Dotzler. But he questions why the identifier is laid down in the first place. "But why ship it at all. Is it really that important to track individual users through their first automatic (and silent) update?" he asks.

As Google's white paper explains, the company continues to gather user data through its so-called Omnibox address bar, which suggests urls as users type. You can disable Omnibox or tell it to use another search provider. But by default, it sends what you've typed, your IP address, and certain cookies back to Google - though the company says it logs only a random two per cent of the data.

Google also says that its logs drop the cookies and scrub the last octet of your IP "within at most 24 hours".

The white paper also discusses the data Google collects when the web address you request does not resolve and when the browser updates. The browser also collects various usage statistics and crash reports, but this is turned off by default. ®

Beginner's guide to SSL certificates

More from The Register

next story
Russian hackers exploit 'Sandworm' bug 'to spy on NATO, EU PCs'
Fix imminent from Microsoft for Vista, Server 2008, other stuff
Microsoft pulls another dodgy patch
Redmond makes a hash of hashing add-on
FYI: OS X Yosemite's Spotlight tells Apple EVERYTHING you're looking for
It's on by default – didn't you read the small print?
'LulzSec leader Aush0k' found to be naughty boy not worthy of jail
15 months home detention leaves egg on feds' faces as they grab for more power
Forget passwords, let's use SELFIES, says Obama's cyber tsar
Michael Daniel wants to kill passwords dead
FBI boss: We don't want a backdoor, we want the front door to phones
Claims it's what the Founding Fathers would have wanted – catching killers and pedos
Kill off SSL 3.0 NOW: HTTPS savaged by vicious POODLE
Pull it out ASAP, it is SWISS CHEESE
prev story

Whitepapers

Forging a new future with identity relationship management
Learn about ForgeRock's next generation IRM platform and how it is designed to empower CEOS's and enterprises to engage with consumers.
Cloud and hybrid-cloud data protection for VMware
Learn how quick and easy it is to configure backups and perform restores for VMware environments.
Three 1TB solid state scorchers up for grabs
Big SSDs can be expensive but think big and think free because you could be the lucky winner of one of three 1TB Samsung SSD 840 EVO drives that we’re giving away worth over £300 apiece.
Reg Reader Research: SaaS based Email and Office Productivity Tools
Read this Reg reader report which provides advice and guidance for SMBs towards the use of SaaS based email and Office productivity tools.
Security for virtualized datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.