3.2(f) termination after an update focused on balance, stability, and a small read-only News panel — looking for guidance

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?

Thank you for your post and appeal. We're investigating and will contact you in App Store Connect to provide further assistance. If you continue to experience issues during review, please contact us.

3.2(f) termination after an update focused on balance, stability, and a small read-only News panel — looking for guidance
 
 
Q