Android permissions and sensitive APIs: Play policy red lines
Self-check SMS, call log, precise location; what happens when declarations diverge from behavior. A red-line list for listing ops. Telegram @hagee66.
This guide · Guide library · Apple listing · Google listing · Both stores · Telegram @hagee66
Play review increasingly moves from Manifest declarations to Data Safety, actual API use, and store copy telling one story. SMS, call log, all-files, and other defaults you should not keep trigger supplementary requests or rejection. Goee (goee.cc) uses a default deny mindset—only core scenarios with policy exceptions. Overview Google Play materials; photos/video Play photo video permissions; SMS/call SMS call log red lines. Sensitive permission catalogs and forms per official pages.
What this guide solves
- Library manifest merge adds unused permissions.
- targetSdk upgrade without migrating storage/notifications model.
- Background location declared without compliant use disclosure.
- Data Safety says no location; manifest has
ACCESS_FINE_LOCATION. - Debug or OEM channel SDKs over-declare in production.
- Screenshots show permission-gated features; buttons are placeholders.
Who should read
| Role | Output |
|---|---|
| Android dev | Merged manifest review, tools:node remove |
| Architecture | Module split to cut transitive deps |
| Listing | Permission map + Data Safety |
| Product | Sign off minimal permission set |
Re-scan on every targetSdk bump or push/map/ad SDK swap.
Core practice
Red-line permissions (default: do not request)
| Category | Typical permissions | Default |
|---|---|---|
| SMS | READ_SMS, etc. |
Do not request except rare approved exceptions |
| Call log | READ_CALL_LOG, etc. |
Same |
| Contacts | READ_CONTACTS |
Only real invite/sync scenarios |
| Background location | ACCESS_BACKGROUND_LOCATION |
See background location guide |
| All files | MANAGE_EXTERNAL_STORAGE |
Extremely cautious |
| Unknown installs | REQUEST_INSTALL_PACKAGES |
Keep only with legitimate distribution |
Whether exceptions exist and how to declare per official pages—not old forum posts.
Manifest audit steps
./gradlew :app:processReleaseManifestor Android Studio Merged Manifest.- Map each permission to feature + UI entry; no entry → remove dep.
- Match Data Safety and privacy policy data types.
- Play Console permission / sensitive API forms match package.
- Submit recording includes “deny permission, core flow still works.”
Common targetSdk migrations
| Area | Note |
|---|---|
| Notifications | Android 13+ POST_NOTIFICATIONS runtime request |
| Media | READ_MEDIA_* replaces broad storage read |
| Nearby Wi‑Fi | Nearby devices vs Bluetooth split |
| Exact alarms | USE_EXACT_ALARM eligibility |
Copy-paste templates
Permission map row
Permission:
Source module: (app / com.xxx:library)
User-visible feature:
If denied:
Data Safety type:
Policy reference:
Keep / remove / pending product
Play internal release note
Sensitive permissions in this release:
- [permission]: used only when user taps [screen].
- Removed [permission] vs v1.2.0 (merged from old SDK).
Verified on API 34 device: deny all optional permissions → core flow OK.
Common mistakes
- Trust AI-generated manifest—merged output wins.
maxSdkVersiondodge without logic change—review watches behavior.- Console-only permission rationale—no in-app education.
- Keep-alive SDK drags in location.
- Copy iOS permission set because “it passed there.”
- Internal track lean, production fat—forms not updated.
FAQ
Which library added a permission?
Merged Manifest dependency stack or Gradle tree + library docs.
Photo Picker—still need storage permission?
Play photo video permissions—policy evolves, official docs.
Permissions policy rejection—order of fix?
Remove unused → update Data Safety → recording proving deny path.
Enterprise MDM exception?
Usually not consumer Play path—separate assessment.
Can Goee scan the package?
Checklist alignment help—no approval promise.
Gradle merge governance
Legacy SDKs declare phone permissions in child manifests. tools:node="remove" with version comment when confirmed unnecessary. Re-diff Merged Manifest after Dependabot. Dynamic feature modules: production track must match user-visible permissions.
Play declaration vs test tracks
If internal build has fewer permissions than production, forms describe production—re-verify before release. Closed test different signing but permission set should converge. After “Permissions policy” reject, check incomplete Console questionnaires.
Link to SMS/call red lines
Default deny SMS/call. OCR or OTP autofill via SMS permission should move to manual entry or system picker as policy tightens. Product insists on SMS read for autofill—legal and store feasibility first, then decide on listing path.
Execution rhythm
Each targetSdkVersion bump gets its own story: official behavior changes, manifest, runtime requests, Data Safety. Week-one post-merge permission diff meeting: Android, product, listing. Sync Google Play materials sensitive API questionnaire—avoid uploaded package with stale form.
Shortest fix path after rejection
- Export offending permissions from Merged Manifest.
- Remove if possible; patch track validate.
- If must keep: Console declaration + in-app copy + policy.
- Record deny-still-works path.
- Resubmit notes quote rejection lines.
Sideload/enterprise manifests out of scope here—Play artifact is what users install. Wear/TV modules: extra row on main checklist.
OEM ROM variance
Channel ROMs may sniff permissions; Play global listing validates Play artifact. Separate manifests for domestic stores—scope in handoff. Goee defaults to Play production package.
Internal review and boundaries
Listing is delivery, not legal sign-off. Steps align checkable items; policy changes—official pages. Defect vs wording: code vs notes/policy/screenshots. Telegram @hagee66 needs build number and checklist. No approval promise; no hidden features, dual binaries, or anti-review tactics.
| Check | Goee | Client |
|---|---|---|
| Path/notes readable | Yes | Valid demo account |
| Policy URL live | Yes | Certs/DNS |
| Forms vs package | Verify | Frozen SDK table |
| Legal conclusions | No | Counsel |
Next steps
Pair with overseas compliance basics. Scan help: Telegram @hagee66. No approval promise—verify manifest and forms match checklist.
Back to guide library · Apple listing · Google listing