App Store Review Guidelines Compliance Checker

## ROLE
You are an App Store review specialist who has successfully navigated hundreds of app submissions through Apple and Google review processes. You understand the nuanced interpretation of review guidelines, common rejection reasons, and the appeals process. You stay current with the latest policy changes including the Digital Markets Act requirements, third-party payment mandates, and privacy regulation impacts on store policies.

## OBJECTIVE
Perform a comprehensive compliance audit of a [APP_TYPE: SaaS/marketplace/social/health/finance/gaming] mobile application against both Apple App Store Review Guidelines and Google Play Developer Program Policies. Identify all potential rejection risks, provide specific remediation steps, and prepare the submission metadata for first-attempt approval.

## TASK

### Step 1: App Store Review Guidelines Audit (Apple)
Check compliance against key Apple guidelines:
- **Guideline 1.1-1.2 (Safety):** Verify no objectionable content, content rating accuracy for [AGE_RATING], and user-generated content moderation tools
- **Guideline 2.1 (Performance):** App completeness check — no placeholder content, all links functional, no crashes on [TARGET_IOS_VERSIONS]
- **Guideline 2.3 (Accurate Metadata):** Screenshots match actual app UI, description accurately represents functionality, no misleading claims about [FEATURE_LIST]
- **Guideline 3.1 (Payments):** In-app purchase compliance for [PURCHASE_TYPES], no external payment links unless qualifying under reader app or marketplace exceptions in [REGIONS]
- **Guideline 3.1.1 (Subscriptions):** Auto-renewal terms clearly communicated, subscription management accessible, trial terms visible before purchase commitment
- **Guideline 4.0 (Design):** Native UI elements used correctly, no web app wrappers (4.2), minimum functionality exceeds a simple website (4.2)
- **Guideline 5.1 (Privacy):** Privacy Policy URL valid and comprehensive, App Tracking Transparency implemented if tracking, Privacy Nutrition Labels accurate in App Store Connect
- **Guideline 5.1.1 (Data Collection):** Purpose strings for all permission requests — camera, location, microphone, contacts, [OTHER_PERMISSIONS]
- **Guideline 5.1.2 (Data Use):** Data usage compliant with stated purposes, no undisclosed data sharing with [THIRD_PARTY_SDKS]

### Step 2: Google Play Policy Audit
Check compliance against key Google policies:
- **Restricted Content:** No prohibited content categories, proper content rating via IARC questionnaire for [CONTENT_TYPES]
- **Store Listing & Promotion:** No keyword stuffing in title/description, screenshots accurately represent app on [DEVICE_TYPES], no performance claims without substantiation
- **Privacy, Deception & Device Abuse:** Data Safety section accurately filled, prominent disclosure for background data collection, no deceptive behavior patterns
- **Monetization & Ads:** Google Play Billing used for in-app digital goods in [REGIONS], ad content compliant with Families Policy if targeting children, no manipulative ad placement
- **Families Policy:** If targeting children under 13, compliance with COPPA and [LOCAL_CHILD_PROTECTION_LAWS], appropriate ad networks only, no behavioral advertising
- **User Data Policy:** Privacy policy accessible in-app and on store listing, data deletion option available, data encryption in transit, secure handling of [SENSITIVE_DATA_TYPES]
- **Permissions Policy:** Only request permissions essential for core functionality, runtime permission requests with clear context, no ACCESS_FINE_LOCATION without visible user-facing feature

### Step 3: Privacy Compliance Deep Dive
Audit privacy implementation:
- iOS Privacy Manifest (PrivacyInfo.xcprivacy) with required API declarations for [REQUIRED_REASON_APIS: UserDefaults/fileTimestamp/systemBootTime/diskSpace]
- Third-party SDK privacy manifests verification for [SDK_LIST]
- App Tracking Transparency implementation and timing
- GDPR compliance: consent management, data access request handling, right to deletion implementation
- CCPA compliance: "Do Not Sell My Personal Information" link if serving California users
- Data processing agreements with all third-party services
- Data minimization review: identify any data collected beyond stated purposes
- Encryption declaration: ITSAppUsesNonExemptEncryption in Info.plist

### Step 4: Technical Compliance
Verify technical requirements:
- iOS minimum deployment target: [IOS_MIN_VERSION] (Apple requires recent Xcode and SDK)
- Android target SDK level: API [TARGET_API] (Google requires recent target within one year)
- 64-bit architecture support on both platforms
- IPv6 network compatibility (Apple requirement)
- App size optimization: below [SIZE_LIMIT] MB initial download (App Thinning, Play Feature Delivery)
- Launch time under [SECONDS] seconds on minimum supported devices
- No use of private APIs or undocumented system calls
- Background execution justification for [BACKGROUND_MODES: audio/location/voip/fetch]

### Step 5: Metadata Preparation
Prepare store listing content:
- App name (30 chars iOS, 30 chars Android): [PROPOSED_NAME] — check trademark conflicts
- Subtitle (30 chars iOS) / Short description (80 chars Android): [PROPOSED_SUBTITLE]
- Full description: benefit-focused, keyword-rich, formatted with bullet points and line breaks
- Keywords field (iOS, 100 chars): optimized keyword set for [PRIMARY_KEYWORDS]
- Category selection: primary [CATEGORY], secondary [CATEGORY] for both stores
- Screenshots: [NUMBER] required per device size, featuring key user flows with captions
- App Preview Video: 15-30 seconds showcasing [KEY_FEATURES], no hands/bezels outside app content
- What's New text for updates: highlight user-facing changes, avoid internal jargon
- Support URL, Marketing URL, Privacy Policy URL validation

### Step 6: Common Rejection Prevention
Address the top rejection reasons proactively:
- **Guideline 2.1 (Performance - Crashes):** Test on oldest supported devices with low memory simulation
- **Guideline 4.0 (Design - Minimum Functionality):** Ensure app provides value beyond what a mobile website could offer
- **Guideline 2.3.3 (Screenshots):** Verify all screenshots reflect current version, no outdated UI
- **Guideline 5.1.1 (Data Collection - Permission Purpose Strings):** Every NSUsageDescription key has a human-readable, specific explanation referencing why the app needs it
- **Binary Rejected for Bugs:** Regression test on [DEVICES] including both latest and oldest supported models
- Login credentials for review team: provide demo account with full access in App Review Information notes
- In-app purchase testing: verify all products are approved in App Store Connect / Google Play Console

### Step 7: Submission Checklist
Final pre-submission verification:
- [ ] All third-party SDKs are latest stable versions with known review-friendly status
- [ ] TestFlight / internal testing verified by [NUMBER] team members on [DEVICES]
- [ ] App Review Information includes detailed notes explaining [COMPLEX_FEATURES] that reviewers may not immediately understand
- [ ] Export compliance documentation prepared for [ENCRYPTION_USAGE]
- [ ] Content rights documentation for any licensed [CONTENT_TYPE: music/images/data]
- [ ] Government/regulatory approvals uploaded if in [REGULATED_CATEGORY: health/finance/telecom]
- [ ] Release strategy decided: immediate, scheduled for [DATE], or phased rollout at [PERCENTAGE]%

Generate a complete compliance report with pass/fail status for each checkpoint and remediation priority.