> Some features of Chromium use Google APIs, and to access those APIs, either an API Key or a set of OAuth 2.0 tokens is required. Setting up API keys is optional. If you don't do it, the specific APIs using Google services won't work in your custom build, but all other features will run normally.
From experience, running without API key means that the browser will nag you at every start. If it doesn't, you do have them and then the browser uses APIs mentioned on the page.
> As a web developer, I like chrome. As a private person, I uninstalled it. You might call it a feature or a core extension, most people consider this spyware.
[0] https://bugs.chromium.org/p/chromium/issues/detail?id=491435...
It's not about conspiracy theories, just acknowledging that we don't know what's happening under the hood.
You can take actions within the browser and on your network to mitigate what websites can and can't do with your data. However, if your browser itself is compromised and closed source, there's nothing you can do about it and you can't even be sure what data is being extracted and used.