Context After our latest update we received a termination notice referencing 3.2(f) (feature/concept switching after review). The update itself included performance/stability improvements, bug fixes, numeric balance tuning, and a small user-initiated News panel (globe icon in the main menu) that displays a single static announcement image and can be closed at any time. There are no links, no navigation, no login/UGC/ads, and no executable content in that panel. We do not collect personal data (no IDFA/ATT). What we’ve done so far Restricted any post-release changes to numeric balance values only. The News panel remains strictly informational (one static image from our own domain with offline fallback). Prepared a short screen recording and code excerpts that demonstrate these constraints. Questions for the community Has anyone faced a 3.2(f) action in a similar scenario (read-only announcement panel)? What clarifications or evidence helped your appeal? Which additional safeguards (domain allow-list, redirect blocking, formal release checklists, etc.) proved most convincing to App Review? Is it helpful to provide a short video (tap globe → panel shows a single image → close) along with code snippets confirming there’s no navigation or executable content? References / Illustrations Main menu and News button: /mnt/data/62591a87-a516-499a-a743-86ace7e9e3a4.png Store creative preview: /mnt/data/337413b0-e5db-466c-bd04-28efa7fb6b52.png News panel mock (single image): /mnt/data/A_screenshot_of_a_mobile_game's_update_news_screen.png Any practical advice or precedents would be greatly appreciated. Thanks in advance!

Hi Apple Staff / App Review Team, We’re following up because we haven’t received a substantive reply to our previous forum post or our messages in App Store Connect. Context (unchanged): Our last update focused on performance/stability, bug fixes, and numeric balance tuning (difficulty/rewards). We also added a small, user-initiated News panel (globe icon in the main menu) that displays one static announcement image and can be closed at any time. There are no links, no navigation, no login/UGC/ads, and no executable content in that panel. We don’t collect personal data (no IDFA/ATT). Safeguards already in place: Post-release changes are restricted to numeric balance values only (no feature toggles, no navigation changes). The announcement is strictly read-only (one static asset from our own domain) with an offline fallback. Internal release policy forbids any post-review feature switches or concept changes. What we’re asking for: Specific guidance on what observation(s) led to the 3.2(f) determination. Whether a resubmission under the constraints above is acceptable (we can tighten further if preferred). We’re ready to provide any materials immediately and submit a new build as soon as we receive direction. Thank you for your help—could you please escalate or advise on next steps?