Auditing Your App's SDKs for Data Safety Before You Submit
The reliable way to catch missing Data Safety rows isn't reading your own code — it's reading your AAB's actual file list and dex references, because that reflects every dependency that made it into the final build, including transitive ones you didn't add directly.
A common surprise: a UI library pulls in an analytics SDK as a transitive dependency, and it ships in your bundle without ever appearing in your top-level build.gradle file.
The fix
Fix: decompile or inspect your release AAB directly rather than trusting your dependency list — transitive SDKs are invisible until you look at what actually got packaged.
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.