Ads SDKs and the Data Safety Rows You Might Be Missing
Beyond the obvious "Advertising or marketing" data type, many ad SDKs also collect device identifiers, approximate location for geo-targeted ads, and app interaction data for frequency capping — each of which may need its own Data Safety row depending on the specific SDK's documented behavior.
The compounding issue: mediation setups (where one ad SDK serves ads from multiple networks) mean you're responsible for declaring the collection behavior of every network in the mediation stack, not just your primary SDK.
The fix
Fix: pull the Data Safety disclosure documentation for every network in your mediation waterfall, not just your top-level ad SDK.
The same check runs automatically when you upload your bundle to the AAB analyzer — permissions, SDK fingerprints, and version info in one pass, free.
Keep going
Run this check on your own AAB
Free analysis, exports when you need them.