No profanity, violence, or explicit content violations

App Store Review Guideline 1.1 (apple-review-guidelines-content) and Google Play's Developer Content Policy (google-play-developer-content-policy) both enumerate content that results in immediate rejection: profanity, graphic violence, sexually explicit content, and hateful speech. Beyond binary-level rejection, content violations discovered post-publication trigger app removal and can result in developer account suspension — losing access to all published apps, not just the offending one. Misleading marketing claims ("100% free" for a subscribed app) are explicitly called out under Guideline 3.1 as deceptive pricing and trigger a separate rejection track. Hardcoded strings in error messages, debug dialogs, and placeholder copy are the most common sources of unintended policy violations in vibe-coded apps.

Search all user-visible string literals for policy-violating content and misleading claims before submitting. Scan source files first:

# Check for common profanity patterns in source
grep -rn --include='*.ts' --include='*.tsx' \
  -E '(fuck|shit|damn|ass\b|crap)' src/

# Check for misleading pricing claims in store metadata
grep -rn 'free\|no cost\|zero cost' src/ store-metadata/

Replace any profanity in error messages, debug copy, and default strings with neutral language. If the app has a subscription or IAP, ensure no marketing copy claims the app is "free" without qualifying it ("Free to download" with "Premium features from $X/mo" is compliant; "Free app" for a paywalled core feature is not). For user-generated content features, implement a server-side moderation layer before content reaches other users.