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!
