Post

Replies

Boosts

Views

Activity

Comment on Account terminated under 3.2(f) — how do I find out what triggered it?
Hey @Tomato, saw your 11+ years on the forum so wanted to ask for your take. We got hit with 3.2(f) out of nowhere—clean history, zero rejections. We suspect a bot false-positive on an inactive Remote Config feature (logs prove it was never active in production). As an indie dev, is there any way to get a manual human review or escalation for edge cases like this? Appreciate any tips!
Aug ’26
Comment on Account terminated under 3.2(f) — how do I find out what triggered it?
Hey @Tomato, saw your 11+ years on the forum so wanted to ask for your take. We got hit with 3.2(f) out of nowhere—clean history, zero rejections. We suspect a bot false-positive on an inactive Remote Config feature (logs prove it was never active in production). As an indie dev, is there any way to get a manual human review or escalation for edge cases like this? Appreciate any tips!
Aug ’26
Comment on Account terminated under 3.2(f) — how do I find out what triggered it?
Hey @Tomato, saw your 11+ years on the forum so wanted to ask for your take. We got hit with 3.2(f) out of nowhere—clean history, zero rejections. We suspect a bot false-positive on an inactive Remote Config feature (logs prove it was never active in production). As an indie dev, is there any way to get a manual human review or escalation for edge cases like this? Appreciate any tips!
Replies
Boosts
Views
Activity
Aug ’26
Comment on Account terminated under 3.2(f) — how do I find out what triggered it?
Hey @Tomato, saw your 11+ years on the forum so wanted to ask for your take. We got hit with 3.2(f) out of nowhere—clean history, zero rejections. We suspect a bot false-positive on an inactive Remote Config feature (logs prove it was never active in production). As an indie dev, is there any way to get a manual human review or escalation for edge cases like this? Appreciate any tips!
Replies
Boosts
Views
Activity
Aug ’26