> You can always use Chromium (premade build or make your own build), get the benefits of Chrome's security without the potential tracking. My understanding is

> You can always use Chromium (premade build or make your own build), get the benefits of Chrome's security without the potential tracking. My understanding is that statement is false; let's be careful not to mislead people about these issues. And in that spirit, I should make clear that my understanding is based only on the following, not on direct knowledge: * The ungoogled-chromium project, which aims to remove from Chromium the privacy threats from Google: https://github.com/Eloston/ungoogled-chromium https://github.com/Eloston/ungoogled-chromium A number of features or background services communicate with Google servers despite the absence of an associated Google account or compiled-in Google API keys. Furthermore, the normal build process for Chromium involves running Google's own high-level commands that invoke many scripts and utilities, some of which download and use pre-built binaries provided by Google. Even the final build output includes some pre-built binaries. * There's also the Inox patchset, with similar aims: https://github.com/gcarq/inox-patchset https://github.com/gcarq/inox-patchset Inox patchset is applied on the chromium source code and tries to prevent data transmission to Google to get a minimal Chromium based browser * And finally, Iridium, a browser based on Chromium: https://iridiumbrowser.de/ https://iridiumbrowser.de/ Chromium (which Iridium is based on) is a very secure browser, yes. But it does call home to Google and we did even more to enhance security to the maximum extent possible.