Why "Optional" Data Types Still Need a Data Safety Row
If a feature in your app is optional — say, an email signup for a newsletter — the data it collects still needs a Data Safety row. Developers frequently skip these because the feature isn't core to the app, reasoning that most users won't use it.
Google's form doesn't have a frequency threshold. If the code path exists and can collect the data, it counts, whether it fires for 100% of users or 2%.
The fix
Fix: map every optional feature in your app, not just the primary flow, before filling out the form.
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.