There are no "trackers" in the app. We use Crashlytics — now owned by Google and part of Firebase — for crash reporting because it's the first-party crash-reporting solution for Android, the same way that crash reports get sent to Apple on iOS. Crashlytics seems to reuse some of Firebase's analytics machinery for crash reporting, but that's not the same as our using Google Analytics. Nowhere in our code do we ever initialize Google Analytics, nor do we do things like call "setUserId" to distinguish crash reports between users. We even specifically disable Firebase analytics collection in the app manifest for good measure.

No. Again, we use the first-party crash-reporting solution, which is integrated into the Google tools with which we manage and distribute the app. We have no reason to think that Google uses Crashlytics data for advertising purposes.

https://firebase.google.com/support/privacy#examples-end-user-data-processed-by-firebase

We use very few third-party services and wouldn't do so here.

I mean, I linked to the specific privacy policy for the service. They obviously offer countless technical services to support their platforms that aren't directly monetized. Their having strategic reasons for creating Android doesn't mean they're using Android crash data to sell you targeted ads.

You are using Google Crashlytics, which is a third-party service, as it would be any of the others.

As I've said, it's the first-party crash-reporting solution for Android, just as Apple's built-in crash-reporting service is the first-party solution for iOS. It's the first party to you as an Android or iOS user and to us as Android/iOS developers. We're not going to start sending crash data from users to some other, unrelated company.