App Store Review Guidelines · pre-flight + rejection recovery
Your listing is fine. Your demo account is what gets you rejected.
Paste your App Store listing, answer ten questions about your build, and get a readiness score plus the specific things App Review will flag. Free. About two minutes.
No account. No signup. Nothing you paste is stored on a server — your submission stays in your browser.
It checks Guideline 2.1, not just your character counts
App Completeness is the single most common rejection, and it almost never means your app crashed. It means the reviewer couldn't find it — couldn't sign in, couldn't reach the paywall, couldn't get to the feature your screenshots promised. Metadata scanners cannot check that. This walks the path the reviewer walks.
It knows what changed this year
The age-rating questionnaire became a hard submission gate. 4.3 was rewritten to target apps that don't add value. Disclosure is now required before user data goes to a third-party AI. Screenshot captions started getting OCR-indexed. A checklist you bookmarked last year knows none of this.
Already rejected? Paste the letter
Drop Apple's rejection message into the form and the audit reads it: which guidelines they actually cited, what the reviewer concretely could not do, the fixes in order, and a drafted Resolution Center reply. You have 14 days on that clock — a specific reply moves faster than a silent resubmit.
How it works
- 01
Paste your listing
Name, subtitle, description, category. The description is the evidence — the audit quotes your own words back at you.
- 02
Answer ten questions about the build
Monetization, login, user content, AI, the App Privacy types you declare, China availability, kids. These are the flags that decide which of the 60 rules can even apply to you.
- 03
Get the findings
Red, yellow, and confirmed-clear, each with the guideline number so you can check us. Score, top three to fix, and the concrete change for each.
What's behind it
60 rules, hand-written from verbatim Apple rejection letters and the review checklists that indie developers actually get bounced by — 23 rejection-risk, 13 metadata, 10 monetization, 7 privacy, 7 conversion. The audit pre-filters to the rules your specific app can trip, then checks each one against what you pasted.
Deterministic, not vibes: 100 points, minus 13 for every red, minus 4 for every yellow, floored at 5. The model decides what applies to you; the arithmetic is the same for everybody.
- 3.1.2Your Terms of Use link is required in two separate places — the in-app paywall and the App Store description. Missing either is its own rejection.
- 5 · China DSTAn AI app saying "ChatGPT" in metadata, in any locale, is rejected while China mainland is still ticked in Pricing and Availability. The fix is one checkbox.
- 2.3.4Screenshots may use device frames. App preview videos may not. One marketing template, two different rules.
- 4.0Asking for name and email after Sign in with Apple is a rejection — and Apple returns those fields only on the very first authorization, never again.
Free tells you what's wrong. $9 tells you what to write.
Free audit. $9 for the whole report.
You can see every finding above — count, severity, and guideline number for each. Nothing is hidden about what's wrong with your submission. One time. Not a subscription — you're submitting an app, not renting a dashboard.
If it doesn't find something you didn't already know, reply to the receipt and I'll refund it. No form.
- 01The full write-up and the exact fix for every finding, not just the top three — the field to change, the text to paste, the Info.plist key to set.
- 02Your App Review notes, drafted. Demo credentials, the tap path to your core feature, and the one paragraph explaining anything unusual. It's the field most first-time submitters leave blank.
- 03A reviewer-path checklist specific to your app — what to verify on a clean device before you hit Submit.
- 04If you pasted a rejection: the ordered fix list and a ready-to-send Resolution Center reply.
Questions
- Is this affiliated with Apple?
- No. It's a checklist built by an iOS developer from public App Store Review Guidelines and from rejection letters. Guideline numbers are cited so you can verify every finding against Apple's own text.
- Do you store my description?
- No. Your submission is sent to the audit endpoint, evaluated, and returned. It is not written to a database — there is no database. Your inputs are held in your browser so the report survives a refresh and the Stripe redirect.
- Why is it $9 and not a subscription?
- Because you submit an app, then you're done for a few months. A monthly bill for a thing you use twice a year is a bad deal, and you'd cancel it. Pay once per submission.
- What if I already got rejected?
- Paste Apple's message into the optional field at the bottom of the form. The audit switches to recovery mode: it maps what they cited to specific fixes and drafts your Resolution Center reply. Same $9.
- Can it guarantee I'll be approved?
- No, and be suspicious of anything that says otherwise. Review is performed by people and there is judgment in it. What this does is remove the boring, predictable reasons — which are most of them.
- What does it not check?
- Anything requiring your binary or your assets: crashes, broken links, whether your screenshots match the build. Where a rule depends on those, the report tells you what to verify rather than pretending it looked.