nandohyphen1 The labels about trackers in Exodus and Aurora Store are highly inaccurate. All it shows is whether an app has a small list of specific libraries they decided are bad and should be called trackers. Their definition of tracker makes little sense and misleads users about privacy. Some of those libraries are not actually particularly privacy invasive and most require the app to set them up and use them, so the app can make it opt-in or opt-out rather than mandatory. Portraying optional crash reporting, etc. as tracking is very strange. It also ignores that the most privacy invasive behavior done by apps is usually done via their own code and services which is never listed as a tracker by these apps. You're just being misled by these labels.
A similar thing applies to DNS-based filtering for supposedly blocking tracking. In reality, it's just the equivalent of these labels. It only blocks connections to a small list of domains they determined are only used for ads, tracking, etc. and are not needed for apps/sites to work. Those filters don't block anything that's dual use and needed for functionality since it would break apps. That means they do not block the vast majority of privacy invasive behavior by apps. Additionally, it's very easy for apps to evade that filtering by doing it server side (which also avoids leaking their API keys), doing their own DNS resolution via (potentially via DNS-over-HTTPS) or hard-wiring the IPs. Many apps do these things to bypass filtering.