Repository navigation
|
My app was flagged or rejected on Google Play for this. Missing prominent disclosure for sensitive user data. Which guideline is this, how do I find it in my project, and how do I fix it before I resubmit? |
Replies: 1 comment
|
Guideline. User Data (Google Play) Severity in the playbook. critical What triggers it. A declared permission that reads contacts, SMS, call logs, device accounts, or all files (the surface Play enforces prominent disclosure on) with no disclosure or consent flow in the app. What to search your code for. How to fix it. Provide a prominent in-app disclosure before collecting sensitive personal data, and obtain explicit user consent. The guard reports this as This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
Guideline. User Data (Google Play)
Severity in the playbook. critical
What triggers it. A declared permission that reads contacts, SMS, call logs, device accounts, or all files (the surface Play enforces prominent disclosure on) with no disclosure or consent flow in the app.
What to search your code for.
READ_CONTACTS,WRITE_CONTACTS,READ_SMS,SEND_SMS,RECEIVE_SMS,READ_CALL_LOG,WRITE_CALL_LOG,GET_ACCOUNTSHow to fix it. Provide a prominent in-app disclosure before collecting sensitive personal data, and obtain explicit user consent.
The guard reports this as
ANDROID-USER-DATA-DISCLOSURE. The full pattern is in data/rejection-patterns.json.This is a maintainer FAQ for app-store-comp…