Which URL goes in which field
Three consoles, eight fields, five pages. This is the map between them, and the list the dashboard checks for you.
Last updated
The fields
Field names change as the consoles are redesigned. If what you see does not match, trust the console and the official documentation linked at the bottom.
| Console field | Page that answers it |
|---|---|
| App content → Privacy policy Google Play Console | /privacy |
| App content → Data deletion Google Play Console | /account-deletion |
| Store listing → Contact details (website) Google Play Console | / |
| Store listing → Contact details (email) Google Play Console | your support address |
| App Information → Privacy Policy URL App Store Connect | /privacy |
| App Information → Support URL App Store Connect | /support |
| App Information → Marketing URL (optional) App Store Connect | / |
| App settings → app-ads.txt (via the listing's website) AdMob | /app-ads.txt |
On AppFoyer every path above sits on one subdomain, so the four fields that want a URL get
https://your-app.appfoyer.page plus the path.
What the checklist checks
The dashboard computes this per app and recomputes it on every change. It is a readiness list, not a guarantee: a green checklist means you have what the stores ask for, not that a review will pass.
- Privacy policy is published Both stores require a public privacy-policy URL.
- The privacy policy names your third-party SDKs The template asks you to list each analytics, ads and crash provider. This is the part a reviewer compares against your Data safety answers, and the checklist keeps warning until the placeholder is replaced.
- Terms of service are published Recommended by both stores, and required by most payment providers.
- Support page is published App Store Connect requires a support URL; Play asks for contact details.
- Support email is set Shown on the support page and used for deletion notifications.
- Account-deletion page is published Google Play requires a web URL where users can request account deletion.
- A verified notification channel receives deletion requests Until one is verified, the page shows your support address instead of a request form — a form nobody receives is worse than no form.
- app-ads.txt lists your ad networks Beta Only needed if the app shows ads. Marked Beta: crawler acceptance on this domain is not yet verified.
- Store listing URL is set Lets your home page link to the app, and helps a reviewer match the site to the listing.
- The App Store listing points back to this site When the listing's website field matches your site, we can verify it against the public App Store record and show it in the footer. Google Play has no equivalent read API, so it cannot be checked automatically.
- App icon uploaded Optional, but a bare page looks less trustworthy to a reviewer and to a user.
Two things a checklist cannot do for you
It cannot know what your app collects. The privacy item goes green when the placeholder is gone, not when the content is correct. Only you can confirm the SDK list is true.
It cannot delete your users' data. The account-deletion item goes green when the page is published and a channel is verified. Acting on each request inside your own systems is yours, and is what the store is actually requiring of you.
Official documentation
- Privacy policy requirements — Google Play
- Data deletion — Google Play
- App information fields — App Store Connect
- Set up app-ads.txt — AdMob
The dashboard runs this checklist per app and links each unfinished item straight to the editor that fixes it. One app is free. Start free