You upload an AAB to Play Console, and an hour later you get a rejection email. The Data Safety section doesn't match the actual traffic, the manifest is missing maxSdkVersion for READ_EXTERNAL_STORAGE, and the permission declaration isn't filled at all. These are common reasons for rejections that we fix within 1–2 business days.
Google Play Review differs from App Store in that most initial checks are automated. The automation catches mismatches in the manifest, permission declarations, and data storage policies. A human reviewer steps in later, after the algorithm has flagged issues. Our experience shows that proper documentation reduces time-to-market by 2–3 times.
Structure of Documentation for Play Console
Data Safety section — an analog of Apple's Privacy Nutrition Label, but with more detailed breakdown. Requires specifying for each data type: whether it's collected, whether it's shared with third parties, and whether users can request deletion. Mistakes in this section are a top reason for rejections in recent Android versions. Every integrated SDK must be checked separately: Google Analytics, Firebase Crashlytics, Adjust, Unity Ads — all have their own Data Safety FAQs that must be considered.
Content Rating via IARC — a questionnaire covering violence, sexual content, gambling. A rating mismatch with actual content leads to app removal. For UGC apps, the rating is typically set to the maximum.
Target Audience and Content — section for apps that may target children. If targetSdkVersion + theme + screenshots suggest a child audience, Google requires COPPA compliance and automatically restricts advertising SDKs.
App Access in Play Console — an analog of App Review Information from Apple. Here you provide test credentials, instructions for the reviewer, and information about features available only with specific hardware.
Why Permission Declaration Causes Complexity?
Starting with Android 13, using permissions READ_MEDIA_IMAGES, READ_MEDIA_VIDEO, READ_MEDIA_AUDIO instead of the deprecated READ_EXTERNAL_STORAGE is mandatory for new apps and updates. If your AndroidManifest.xml still has the old READ_EXTERNAL_STORAGE without android:maxSdkVersion="32", Play Console will issue a warning and in some cases block publication.
Permissions like MANAGE_EXTERNAL_STORAGE, REQUEST_INSTALL_PACKAGES, PACKAGE_USAGE_STATS, and the use of Accessibility Service all require separate justification in the Declaration Form. Without a completed form, the app won't pass review.
Separately — READ_PHONE_STATE and access to Device ID. Google is steadily tightening requirements on using device identifiers. If an SDK collects IMEI or Android ID without explicit business necessity, review will be rejected.
How We Audit Documentation?
- Full audit of AndroidManifest.xml for compliance with current policies.
- Check all integrated SDKs for Google Play Families Policy compliance if the app targets children.
- Fill the Data Safety section based on actual traffic (verified via Charles Proxy or mitmproxy).
- Prepare reviewer instructions with test credentials and description of non-standard functionality.
Timeline: one to two business days. Cost is calculated individually based on complexity and number of SDKs. For example, a standard audit with filling costs $397. We guarantee that after our preparation, the app will pass review first time, or we fix everything for free.
What's Included in Preparation?
- Audit of manifest and all integrated SDKs.
- Filling the Data Safety Section with detailed descriptions.
- Preparing the Permission Declaration (Declaration Form).
- Completing the Content Rating questionnaire.
- Writing reviewer instructions with test credentials.
- Checking the privacy policy for GDPR and COPPA compliance.
- Recommendations for improving review speed.
Common rejection reasons: Data Safety mismatch with actual data (90% of cases); using deprecated permissions without maxSdkVersion; missing declaration for dangerous permissions; insufficiently detailed reviewer instructions.
| Documentation Section | What It Includes | Typical Mistakes |
|---|---|---|
| Data Safety | Data types, collection purposes, third-party sharing | Missing SDK, incorrect categorization |
| Content Rating | IARC questionnaire (violence, content, gambling) | Mismatch with actual content |
| App Access | Credentials, instructions, feature descriptions | Missing login details |
| Permission Declaration | Justification for dangerous permissions | Using deprecated permissions |
| Typical Mistake | Solution |
|---|---|
| Data Safety doesn't match traffic | Analyze via Charles Proxy, cross-check with SDK documentation |
| Deprecated READ_EXTERNAL_STORAGE | Replace with READ_MEDIA_* with maxSdkVersion |
| Missing test data | Prepare instructions with login/password |
Our documentation preparation is 3 times faster than doing it yourself and leads to 90% first-attempt approval rate compared to 40% without audit. With our documentation, review time is 2–3 times less than with self-preparation. Our clients save on average 30% of their publication budget. Contact us for a project assessment. Order a documentation audit now.
Our specialists hold Google Play Console certifications and have 5+ years of experience in app publishing. We have helped over 50 projects successfully pass review. Google Play Developer Policy requires strict compliance with all rules, and we guarantee it.