What problem does it solve? Adding ads to a mobile app invalidates the previous "collects nothing" privacy declarations on both stores, and missing any re-declaration (Play Data safety, ASC App Privacy, age rating, ATT) causes review rejections. This Skill provides the wiring skeleton for Google AdMob in an Expo app plus the complete checklist of declarations that must be redone once ads are in. ## Core Features & Use Cases - AdMob Wiring Skeleton: Steps for creating AdMob apps and ad units, installing react-native-google-mobile-ads, configuring app.json plugin App IDs, and switching test/production ad unit IDs via DEV. - Consent Flows: iOS ATT prompt (requestTrackingPermissionsAsync) plus Google UMP consent for GDPR and US state laws, both before the first ad shows. - Privacy Re-Declaration Checklist: Table covering Play Data safety (device IDs, advertising purpose), Play ads declaration, ASC App Privacy questionnaire, ASC age rating advertising flag, and app-ads.txt hosting. - Use Case: You have an Expo app live on both stores with zero-data-collection declarations and want to add banner ads. Follow the skeleton to wire AdMob, then walk the checklist so both store listings are re-declared correctly before resubmission. ## Quick Start Ask the agent to walk you through adding AdMob banner ads to your Expo app and updating both stores' privacy declarations accordingly.
