Don't spend months in Apple's review queue.
AppClearance connects to App Store Connect, catches what gets apps rejected before Apple does, and hosts the privacy policy and support pages Apple requires.
- See your results before you pay
- Read-only access
- Disconnect any time
- 20 days
- per review, as developers are currently reporting
- 1 in 4
- submissions rejected, per Apple's transparency report
Guideline 4.3(a) · Design · Spam
What this actually means
Apple thinks your app is a template. Your listing, icon and screenshots need to show what is different about it, and your description currently reads like the demo.
- Lovable
- Bolt
- Replit
- Cursor
- Claude
Three things stand between you and the App Store.
Apple's own transparency report puts it at roughly 1 in 4 submissions rejected: 7.77 million reviewed, 1.93 million turned away. Each one costs another trip through the queue, and most of those rejections are mechanical. Mechanical problems can be caught before you submit.
Apple rejected your app, and the email doesn't say why.
A guideline number and a paragraph of boilerplate. We translate it into the exact thing to change, in plain English, and check the rest of your submission for whatever comes next.
Every finding names the problem, whose side it is on, and the fix.
You need a privacy policy, a support page and terms, all live before review.
Reviewers open the URLs. A page that returns 404, or a policy that does not match what your app collects, is a rejection on its own. Most people find this out from the rejection.
We write and host all three at your own address, from what your app actually collects.
The reviewer stopped at your login screen.
An empty demo account. In-app purchases that quietly detached after the last rejection. A paywall price that no longer matches App Store Connect. None of it is visible from your phone.
We check every one against your real submission before Apple sees it.
Apple says 24 hours. Developers are waiting weeks.
Developers are currently reporting waits of two to three weeks, far longer than the figure Apple publishes. Apple has not updated that figure.
That is the cost of one submission. A rejection means the whole wait again, usually for something that was visible in App Store Connect before you pressed Submit. Catching it first is the entire point of the check.
Apple's published figure
for 90% of submissions
24 hours
What developers are reporting
last checked 2026-08-14
20 days
Day 1: you press Submit for Review
Day 20: a typical decision
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- Apple's figure
- Typical wait right now
- After a decision
A rejection sends you back to day 1. Two rejections means three trips through the queue: about 9 weeks of waiting at the current rate, for something that was usually visible before the first submission.
One subscription. The whole submission covered.
The check, the pages Apple requires, and the fix. Everything a reviewer will look at, looked at first.
Every check, run against your real submission.
IncludedNot a questionnaire. We read your actual App Store Connect data, fetch your live URLs, and stream findings as each check completes. Failures first; passing checks collapsed.
2
blockers
59 of 82 pass
These 2 things would get the app rejected today
Fix these before anything else; any one of them alone is enough for a rejection.
- A processed, unexpired build is attached to the versionBuild & binary
- Required screenshot sets present with 1–10 shots eachScreenshots & icon
Privacy policy, support and terms, hosted at your address.
IncludedApple requires a working privacy policy URL and support URL, and reviewers open both. We generate all three pages from what your app actually collects, host them on a subdomain or your own domain, and keep them current as Apple's rules change.
- Built from your app's real data use
- Support inbox included
- The URLs App Review always opens
Fix it from the dashboard.
ComingToday every finding links to a step-by-step guide you can follow in your browser. Next: one-click fixes for the metadata problems, with before and after shown and each change confirmed by you.
Findings that tell you what, whose fault, and how.
- Proven
- We executed it. Fetched the URL, ran the call, saw the result.
- Verified
- Apple's API confirms it. Not a guess from the outside.
- Unknown
- We can't see this one. We say so, and tell you how to confirm it.
Every finding is also tagged by owner: your side, not done yet, or Apple's side. When it isn't your fault, we say that too.
The check
The whole submission, checked the way a reviewer checks it.
Not a questionnaire. The check reads what Apple will read and tells you, one finding at a time, what a reviewer is going to stop on.
- 1We read the same sources a reviewer doesYour App Store Connect record, your build, your live privacy and support pages, and RevenueCat if you use it to run subscriptions.
- 2Findings stream in as each check completesEighty-odd checks across ten categories. Failures first; passing checks collapsed underneath so the report is about what to fix.
- 3Each one says how we know and whose side it is onProven means we fetched it ourselves. Verified means Apple’s API confirms it. Then the owner: yours to fix, not done yet, or Apple’s side.
- 4Each one links to the fixA step-by-step guide you can follow in your browser. No terminal, no Xcode, and the guideline Apple would cite named on every finding.
- Privacy & legal2 to fix
- Purchases & subscriptions1 to fix
- Review readiness1 to fix
- Store listing11 pass
- Screenshots & icon8 pass
- Build & binary5 pass
- + 4 more categories
Your privacy policy URL returns a 404
We fetched https://example.app/privacy and got nothing back. A reviewer opens this link; guideline 5.1.1 is one of the most-cited rejections there is.
How to fix it →
Your in-app purchases are not attached to this version
App Store Connect lists 3 products in Ready to Submit, and none are attached to 1.2.0. The last rejection detached them.
How to fix it →
The demo account is marked required, but has no password
App Review Information says sign-in is required and the password field is empty.
How to fix it →
Comparing your paywall price with App Store Connect…
Legal
A privacy policy and terms, built from questions we mostly answer for you.
Apple opens your privacy policy URL during review and reads it. A page that does not say what the app collects, who receives it and how to delete it is one of their listed reasons for rejection. Writing one from a blank page is where most people get stuck.
- 1Check the answersEleven short sections, most of them prefilled from your App Store Connect privacy answers and your build. You confirm them rather than write them.
- 2Build the documentsOne button turns the answers into a privacy policy and terms of use, with every section Apple and the GDPR ask for, in plain English.
- 3Publish at your addressBoth go live on your subdomain or your own domain, and the URLs are ready to paste into App Store Connect. Change an answer and rebuild any time.
Legal
23 of 28 answered, 3 needed before we can build
- Who is publishing thisfrom App Store Connect
- What the app collectsfrom your privacy answers
- Who else receives itfrom your build
- Your users2 left
- Moneyfrom your subscriptions
- Keeping and deleting data1 left
Privacy policy
What we collect
Email address and account name, so you can sign in. Photos you choose to upload, to build your morning routine. Purchase history, provided by Apple.
Who else sees it
RevenueCat processes subscriptions. Sentry receives crash reports with no personal data. Nobody receives your photos.
Deleting your data
Open Settings, Account, Delete account. Everything is removed within 30 days, or email us and we do it for you.
+ Your rights · Children · Changes to this policy · Contact
Where an honest answer describes something App Review will not accept, such as accounts that can be created but not deleted, we say so before you publish, because the fix belongs in the app, not in the document.
Support
A support page a reviewer cannot fault, and an inbox that feeds it.
Apple checks that your support URL resolves and offers a way to reach a person. Most support pages fail a quieter test: they do not answer the questions people actually ask.
- 1The page is generated and hostedA contact form, your email, and a list of questions and answers, live at your own address alongside your privacy policy.
- 2We show what a reviewer findsA question with no answer, a page that is not published, a link that does not match your listing. Problems first, and the button that fixes each one.
- 3Messages land in the inboxThe form on the page posts to a minimal inbox in your dashboard. No queues, no assignees; a list of what people asked.
- 4Answers go back on the pageA question asked twice is one the page should answer. One click turns a message into a published answer, and we suggest the ones your kind of app gets asked.
- 1 question with no answerThey go out on the page exactly like that.
- Listing link uncheckedPublish and we compare it with App Store Connect.
- How do I restore a purchase?
- How do I cancel my subscription?
- How do I delete my account and data?
- Untitled questionno answer
- Suggested for your app
- Can I get a refund?You cannot refund an App Store purchase yourself. Saying so plainly stops it reading as a brush-off.Add
Support
Questions, problems, or a bug in Contour? Send a message. A person reads it.
Send us a message
How do I restore a purchase?+
How do I cancel my subscription?+
How do I delete my account and data?+
- PriyaI paid and nothing unlocked, what do I do?Answer on the page
- TomDoes it work without an internet connection?
The problems you didn't know you had.
The count isn't the point. It's the one finding you had no idea about, named in full, that saves the week. Real findings from real App Store Connect data, not a questionnaire:
Run it on mineYour privacy policy URL returns a 404.
We fetched it ourselves; that's what Proven means.
The last rejection silently detached your in-app purchases.
Resubmitting without them reproduces the same rejection. Almost nobody knows this.
Your description doesn't link to your Terms of Use.
A one-line fix for a whole class of subscription rejections, and it isn't in Apple's docs.
Your demo account is marked required, but empty.
The reviewer stops at your login screen.
The problems that only show up between two sources.
Most tools read one source. We hold your App Store Connect account, your live privacy and support pages, the wording of your listing and your subscription setup at the same time, and the worst problems live in the disagreements between them.
- Your age rating declares no user-generated content, while your own description advertises a community feed. A reviewer reads both.
- Your subscription IDs almost match between App Store Connect and RevenueCat, the service most apps use to run their subscriptions. Purchases fail silently, with no error shown to anyone.
- The price on your paywall no longer matches the price in App Store Connect.
Connected in two minutes. Checked in one.
1Connect
Add a read-only App Store Connect API key. Two minutes, and we show you exactly where to click.
2Check
We run every check against your real submission and stream the findings as each one completes.
3Fix
Each finding links to a plain-English guide with steps you can do in your browser. No terminal, no Xcode.
4Submit
Press Submit for Review knowing what Apple will find. Then re-check on every update after.
Launch day is your first submission, not your last.
Every update is a fresh review with fresh ways to get rejected, and Apple keeps moving the rules underneath apps that were compliant when they launched.
Every release, re-checked
Ship as often as you like. Run the full check again on every submission, as many times as you want, at no extra cost.
Rule changes, watched
SDK deadlines, privacy requirements, payment rule changes. Your app was compliant; we tell you when it stops being.
Silent breakage, caught
Certificates expire yearly. Product IDs drift and purchases fail without an error. A monthly digest tells you either way.
One price. The whole thing.
Run the check against your real submission and see what it found before you decide to subscribe.
AppClearance
Flat rate$29/month
No credits, no tokens, no usage counters. One app, cancel any time.
- Every check run against your real submission
- Every finding named, in plain English
- The guideline Apple would cite for each one
- What to change, step by step: no terminal, no Xcode
- Hosted privacy, support and terms pages at your own address
- Legal documents built from what your app actually collects
- Support inbox for your app
- Unlimited re-checks, on every future submission
Tiers by app count later, never by usage. Cancel any time.
Before you pay
We would rather you saw the product than read about it. Nothing here is a demo account or a screenshot of somebody else's app:
- The full check runs against your own submission first
- You see how many problems, how serious, and where
- One of them named in full, so you can verify we are right
- Every other screen previews what it looks like unlocked
Read-only access to App Store Connect. Disconnect any time and the key is deleted.
Not ready to connect anything yet?
Leave an email and we'll tell you when Apple changes a rule that affects apps like yours. That's the only thing we'll send.
Rule changes only. Unsubscribe any time.
The questions we get asked.
Honest answer: ASC keys are team-wide, so treat any tool that asks for one seriously, including us. Ours is read-only in practice: we only make GET calls, your .p8 is stored encrypted and never shown again, every call appears in an audit log you can read, and disconnecting deletes the key instantly. You can also revoke it on Apple's side at any time.
No, and nobody can promise that; App Review decisions are Apple's alone. What the check does is catch the common, mechanical rejections before Apple does, so your submission isn't rejected for something a machine could have told you about.
No. Everything the check flags can be fixed in App Store Connect in your browser or by prompting the AI tool that built your app. The guides never assume you can read code.
Yes. Apple requires a privacy policy URL and a support URL for every app, and reviewers open them. The privacy policy also has to match what your app actually collects, which is the part most people get wrong. We generate both from your app's real data use and host them at your own address, so they exist, resolve, and stay accurate.
Yes, and we think you should. Connect your key and the whole check runs against your real submission before you're asked for a card: you see how many problems there are, how serious each one is, which part of your submission each sits in, and every check that passed. One of the problems is named in full so you can go and verify it in App Store Connect yourself.
$29 a month, flat. No credits, no tokens, no usage counters anywhere; you shouldn't have to do arithmetic before pressing a button. One app, cancel any time.
Then we say so. Some findings aren't your fault and can't be fixed from your side: a stuck review, a locked setting. Those get labelled "Apple's side" with the escalation path, not dressed up as something to sell you. Knowing it isn't you is worth something too.
The rejection guides.
Free, no signup. Plain-English guides to the guidelines that actually get apps rejected, each one verified against Apple's current rules.
Spam
Your app looks like a duplicate of other apps. The existential one for template and AI-built apps.
Read the guide →App completeness
Crashes, placeholder screens, or a login the reviewer couldn't get past.
Read the guide →Data collection & storage
Missing privacy policy, or accounts that can be created but not deleted.
Read the guide →Submit knowing what Apple will find.
The check takes about a minute once you're connected. The rejection it saves you costs weeks, and the next one costs the same again.
Check my app