Before an app can go live, Play Console asks you to declare what the app does, who it is for, and what data it handles. These are the app content declarations.
They are not paperwork for its own sake. A mismatch between a declaration and the app's real behavior is a common cause of rejection, and sometimes suspension.
Here is the full list and what each one actually asks.
1. Privacy policy
You provide a public URL to a privacy policy that explains:
- What data the app collects.
- How it is used and shared.
- How users can request deletion.
- Who to contact.
The URL must work without a login. A PDF on a cloud drive that requires access is not acceptable.
Most apps need a privacy policy. If your app collects any personal data, handles accounts, or uses advertising or analytics, assume it is required.
2. App access
If reviewers cannot use the app without credentials, you must provide them.
- Demo username and password.
- Any required steps, such as selecting a region or bypassing an OTP.
- Notes about restricted features.
Broken credentials are a classic rejection cause. Test them before you submit.
3. Ads
Declare whether the app contains ads. This includes:
- Banner, interstitial, and rewarded ads.
- Ads in a web view.
- Cross-promotion that behaves like advertising.
If you add ads later, update the declaration. An undeclared ad network can trigger a policy issue.
4. Content rating
Complete the content rating questionnaire for each app. It asks about:
- Violence, sexuality, language, and controlled substances.
- User-generated content and sharing.
- Location sharing.
- Purchases and gambling-like mechanics.
Answer honestly. Ratings are used in many countries to restrict distribution, and an inaccurate rating can be treated as a policy violation.
5. Target audience and content
Select the age groups the app is designed for. This determines whether Families policy applies.
If any selected audience includes children, expect extra requirements:
- Families policy compliance.
- Approved ads SDKs.
- Content and privacy rules for child-directed experiences.
“Not designed for children” does not exempt you from general Play policies.
6. Data safety
The Data safety form describes:
- What data the app collects and shares.
- Whether data is encrypted in transit.
- Whether users can request deletion.
- Why the data is collected.
The form must match your SDKs, not just your own code. Analytics, crash reporting, ads, and authentication libraries all count.
A mismatch between the form and the app's traffic is a common rejection reason. Audit third-party SDKs before answering.
7. Sensitive permissions
Some permissions require a declaration and sometimes a justification:
- Location (especially background location).
- SMS and call log.
- Contacts.
- Microphone and camera.
- Background access.
- All files access.
Only request what the app genuinely needs. A permission that is declared but unused can still draw scrutiny.
8. Special app categories
Depending on the app, you may also see:
- News app declaration.
- Government app declaration.
- Financial features declaration.
- Health declaration.
- VPN declaration.
- COVID-19 or other temporary categories.
These add review requirements. Answer them accurately; misclassifying a regulated app is worse than declaring it.
9. Account deletion
Apps that let users create accounts generally need a way to delete the account, both in the app and through a web link. Play Console asks for the deletion URL.
The link must be public and functional, not a support email that never replies.
10. Advertising ID
If the app uses the advertising ID, declare it. If it does not, make sure your SDKs are not using it silently.
Why mismatches matter
Google compares declarations with:
- The app's behavior.
- The store listing.
- The privacy policy.
- The data safety form.
- Third-party SDK traffic.
A mismatch can lead to rejection, forced corrections, or account action. It is not worth guessing.
A practical review order
- Privacy policy live and public.
- App access credentials tested.
- Ads declaration accurate.
- Content rating complete.
- Target audience selected.
- Data safety audited against SDKs.
- Sensitive permissions justified.
- Special categories reviewed.
- Account deletion link working.
Clear every warning in the App content section before you create a production release.
Where Yara Testers fits
Yara Testers is a specialist managed closed-testing service for Google Play, not a declarations consultancy. What we handle is the tester side: 12 real testers, coordinated opt-ins, and a 16-day managed window that covers the 14-day production requirement. You still complete the declarations and own the app.
We are independent, Google makes the final review decision, and our terms apply. See yaratesters.com.
Need the testing half handled?
Related reading
Our team’s note
If this answered the question but your situation still feels messy, send us the screenshot or the rejection email. Some things are easier to solve in a two-minute conversation than another article.