Repository navigation
|
How can a team catch Missing prominent disclosure for sensitive user data automatically before a build goes to review? |
Replies: 1 comment
|
The quick check. Run this from the project root and read what it prints. grep -rnE 'android\.permission\.(READ_CONTACTS|WRITE_CONTACTS|READ_SMS|SEND_SMS|RECEIVE_SMS|READ_CALL_LOG|WRITE_CALL_LOG|GET_ACCOUNTS|MANAGE_EXTERNAL_STORAGE)' --include='AndroidManifest.xml' . && ! grep -rnE 'prominent disclosure|user consent|privacy consent|accept policy|[Pp]rominentDisclosure|[Dd]isclosureDialog|[Cc]onsentDialog|showDisclosure|requestConsent' .Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as What the hit means. 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. The fix. Provide a prominent in-app disclosure before collecting sensitive personal data, and obtain explicit user consent. Recipe source. data/detection-recipes.json This is a maintainer FAQ for app-store-compliance, an open playbook and pre-submission guard for App Store and Google Play review. Run |
The quick check. Run this from the project root and read what it prints.
Read the result honestly. This is a heuristic. A match is something to inspect, not proof of a violation, and an empty result means nothing was found, not that the app is compliant. For CI, run the full guard, which reports this as
ANDROID-USER-DATA-DISCLOSURE