Free rejection classification
Classify an Apple or Google Play rejection message into a likely category. Local, no login, and no AI cost.
Local in your browser · nothing stored
Free tool
The analyzer maps a pasted Apple or Google Play message to one likely main category locally in the browser. It narrows the next investigation area but does not write a finished reviewer response or claim a complete root cause without project context.
Store messages often combine a policy reference with observed behavior. Paste the complete relevant paragraph after removing names, credentials, app IDs, and confidential attachments.
Separate technical failures, missing declarations, inaccessible review accounts, and policy questions. The response must address the actual observation.
The category starts the investigation. For account deletion, verify the in-app path, public URL, re-authentication, downstream processors, tokens, and stored files.
Minimum Functionality and WebView concerns need a signed build and a reproducible flow, not configuration alone.
Name the affected build, describe the concrete change, and provide a short reproducible path. Stable demo credentials belong in designated review fields; infrastructure secrets never do.
Disagree only with verifiable facts. When the cause is unclear, ask a precise question and state what has already been tested.
Many rejections are contradictions between visible behavior, listing data, and project configuration. The full review connects the likely category to files, permissions, SDKs, and store fields.
The free analyzer keeps the message in the browser, uses no AI model, and deliberately returns one category rather than complete supporting evidence.