Repository navigation
|
How can a team catch Google Play Advertising ID usage without disclosure or opt-out 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 -rn 'com.google.android.gms.permission.AD_ID\|AD_ID\|getAdvertisingIdInfo' --include='AndroidManifest.xml' --include='*.kt' --include='*.java' . && ! grep -rn 'opt-out\|reset AD_ID\|advertisingIdConsent\|delete AD_ID' .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. Using com.google.android.gms.permission.AD_ID permission or querying GAID but lacking opt-out support or user deletion pathways in code/privacy policy. The fix. Declare the AD_ID permission in AndroidManifest.xml and handle user opt-out or deletion requests in full compliance with Google Play policy. 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-ADVERTISING-IDwith a coverage line and a proper exit code.What the hit means. Using com.google.android.gms.permission.AD_ID permission or querying GAID but l…