Data Safety must match your SDK inventory
Selecting “no data collected” while ad or analytics SDKs are in the AAB is a common paperwork mismatch. List SDKs and what they actually read, then complete Data Safety.
SDK disclosure checklist · Ad SDKs and Data Safety · Google Play materials · Telegram @hagee66
Data Safety is not marketing copy. It must align with third-party code in this AAB version.
Build an SDK table before you fill the form
| Column | What to write |
|---|---|
| SDK name | One row each for ads, analytics, login, crash, push |
| Provider | Company or product name |
| What it reads | Advertising ID, device info, coarse location, account email, etc.—based on actual integration |
| Form choices | Collected, shared, optional—same facts as the prior column |
If an ad SDK is in the package but the form says “no data collected,” that is a paperwork problem, not a wording preference. Apple’s nutrition labels use a different form—do not paste Play answers there. For both stores see One story, two forms.
Goee cross-checks the SDK list and package you provide. We do not turn off ads you still use. We do not promise the form passes once submitted.
FAQ
Q: An SDK was integrated years ago and nobody can explain it?
A: Start by exporting names from the current build’s dependencies and privacy manifest, then fill the form. If you cannot explain it, pause—do not pick the easiest “no collection” option.
Q: Ads do not show on one test device—can the form say no ads?
A: Describe the build you submit. If the build reviewers install can request ads, the form must acknowledge that.