Before an app can go live, Google Play requires a set of declarations that describe what the app is, what it collects, and who it is for. These live on the App content page in Play Console, and an incomplete page is one of the most common reasons a submission never reaches review at all. This guide lists every requirement and where to finish it.
Find the App content page
Open your app in Play Console and go to the App content section, sometimes surfaced as tasks on the app dashboard. Each incomplete declaration appears as its own task with a status. Your goal before any production submission is a page where every required task shows complete.
The declarations every app needs
- Privacy policy: a live URL describing how user data is handled, required for essentially every app.
- Data safety: what data the app collects, how it is used, whether it is shared, and whether it is encrypted in transit.
- Content rating: the completed questionnaire that produces age badges per country.
- Target audience: the age groups the app is intended for, which drives family policies and ads behavior.
- Ads declaration: whether the app contains advertising, asked as part of the content questions.
- App access: login credentials or a demo path so reviewers can get past a sign-in screen.
- Content declarations: where relevant, features like user-generated content, web views, or restricted content categories.
How to complete them well
Answer from the shipped build
Read each question against the actual app, including third-party SDKs. An analytics or advertising SDK you added three months ago counts as data collection even if nobody on the team remembers installing it.
Keep the policy URL live
The privacy policy link must load without login and must match what the app actually does. A dead link or a generic template is a rejection waiting to happen.
Provide app access details
If the app requires an account, give reviewers working test credentials in the app access task, plus any multi-factor steps they will hit. Reviewers who cannot sign in review the app blind.
Revisit the page after big changes
New features, new SDKs, and new content types can invalidate old answers. Tie a pass over the App content page to every major release, not just first submission.
Most declaration problems are not policy ignorance, they are drift: the app changed and the forms did not. AppsTestLab's pre-submission audit reads the declarations against the build, so inconsistencies surface before a reviewer finds them.
Frequently asked questions
Why is my app stuck on App content requirements?
The submission cannot proceed until every required declaration on the App content page is complete. Open the page, finish the outstanding tasks, then resubmit your release.
Is a privacy policy hosted anywhere acceptable?
It must be a public URL that loads without authentication and accurately describes your data practices. Any reliable host works, as long as the content matches what the app actually does.
Do these declarations apply to updates too?
The declarations stay live for the life of the app. You do not refill them per release, but you must update them whenever the app's data practices, audience, or content change.
Sources & references
Official Google documentationThese links open Google's official Play Console Help pages used to verify this guide. AppsTestLab guidance is independent and not affiliated with Google.
Get help doing this
