Type in an address that Google has flagged as a phishing or malware site and Chrome will send an obfuscated version of the address to Google to get more information about the risk.
Type anything at all into the address bar and Chrome will send the keystrokes to Google for help suggesting what you may be looking for.
And that doesn't include the usage statistics and other information that Chrome sends home for Google to use "in order to operate and improve Google Chrome and other Google services," according to Google's privacy notice for Chrome.
You can turn much of that phoning-home off, or at least reduce it. But it's clear that Google doesn't see Chrome as just another browser. It's more like the front end for a Web-browsing software-as-a-service offering.
Relax. Right now, Chrome is a beta with significant security problems yet to be addressed. By definition, it's not ready -- that's what beta means.
Bugs and security holes will be fixed. But Chrome's basic business model won't change.
So when you start evaluating it -- and you should -- don't just test how well it serves up Web applications, how robust it is or whether it really is a better browser.
Think about this: Are you ready to trust a software-as-a-service model for just about everything your users do?
Because that's Google Chrome.