Google analytics /telemetry/ data collection

[nasimul-hasan]

Could you be able to remove all Google tracking codes? Or there maybe still hidden tracking codes?

i read a article there someone says not to use chromium based browser. Because it's hard to remove all Google tracking codes. They says to use firefox based browser. The says its best for privacy

@uazo please answer this questions. Could you able to remove all kind of google telemetry?

[nasimul-hasan]

[rywz]

Please stop spamming, I'm sure he'll answer whenever he's free. It would be just irritating for him to see getting mentioned over & over.

[uazo]

Could you be able to remove all Google tracking codes?

I can tell you what cromite patches do in this regard.
related cromite patches can be divided into some types

• those that remove access to google apps (play services) in android.
  the fundamental problem is that the google API sends telemetry to developers, as indicated in "How to use the information on this page" of https://developers.google.com/android/guides/play-data-disclosure. some do not send any data but cromite does not need them and they are removed anyway.
  • Remove-binary-blob-integrations.patch
    kill-Vision.patch
    kill-Location-fall-back-to-system.patch
    kill-Auth.patch
    Remove-voice-recognition-integration.patch
    Disable-Read-Aloud-by-default.patch

on the windows side, however, it is allowed. let's be clear, it is the entire operating system that is put under constant control. there other, non-browser-specific tools can be useful.
in linux I honestly don't know.

• patches that disable chromium features that require a google server or in general a non-local service.
  to work, these features need to send and receive data from the internet. some without the google api key would not work anyway, but the request is made anyway and thus the feature removed.
  • ungoogled-chromium-Disable-Gaia.patch
    Remove-GoogleAccountsPrivateApiHost.patch
    Keep-Manta-Service-Disabled.patch
    ungoogled-chromium-Disable-webRTC-log-uploader.patch
    ungoogled-chromium-Disable-Network-Time-Tracker.patch
    translate-disable-fetching-of-languages-from-server.patch
    ungoogled-chromium-Disable-translate-integration.patch
    Disable-NTP-remote-suggestions-by-default.patch

there is a patch (Internal-firewall.patch) that blocks all requests that I have not evaluated, so even future features that I am not aware of (the chromium code is huge).

• the one that removes what makes it clear that chromium was made by google

  • ungoogled-chromium-no-special-hosts-domains.patch
    Disable-references-to-fonts.googleapis.com.patch
    Keep-Side-Panel-Companion-disabled.patch
    Disable-Real-Box.patch
    Restore-Simplified-NTP-launch.patch

• the one that sends telemetry to google

  • add-browser-policy.patch
    Disable-various-metrics.patch
    Disable-third-party-origin-trials.patch

keep in mind that patches often act on several aspects at the same time, such as add-browser-policy.patch, so this division may not be correct. but the code is there, for those who know how to read it.
another thing: the patches are called "ungoogled-chromium" but have no reference other than the name to the same patches in ungoogled chromium.
it's just that the patches never changed their original names, but they are not related (if not originally) to ungoogled-chromium's patches. here it's my fault, i never checked ung's patches. honestly i don't know if carl did.

Or there maybe still hidden tracking codes?

chromium is made by google, it is imperative that it knows all its secrets. it even knows how to crack it and only says so when it solves it! so, there is no answer, except the code, it is there, only to be read.