Any kind of telemetry service inside of a program purporting to care about centralised avenues of control should be an indicator to never ever use it. Either the developers don't understand what they're talking about or they are disingenuous. It doesn't really matter to the end user, both will mean that your use-case is not being served :)
It tries to scrub passwords and secret keys based on some text filters by default, but it can be configured to scrub arbitrary data (via a hook in the sdk).
Crash reporter uses sentry. We don't want to know anything else about our users.
When Tribler crashes the core dump (e.g. Python TraceBack) can be inserted as a Github issue, using Sentry. Requires the user to opt-in by clicking "send" on crash reporter.