Weak permission text
Find empty, vague, or risky purpose strings before submission — the most common avoidable rejection cause.
App Store submission preflight
Upload an exported IPA and get a private readiness report with evidence-backed findings, exact fixes, and verified source deletion after processing.
Readiness guidance only — not an approval prediction or guarantee.
Ready for submission preparation
Original IPADeleted · verified
Location purpose text needs review
Payload/App.app/Info.plistNSLocationWhenInUseUsageDescriptionThe cost of finding out late
By the time Apple rejects a build, the release is already delayed. A preflight scan catches common submission risks before review.
Find empty, vague, or risky purpose strings before submission — the most common avoidable rejection cause.
Compare project details against what the IPA actually contains, so the listing and the binary do not drift apart.
Surface review notes and app context that need your answer. Some checks cannot be automated honestly.
Catch missing privacy or binary metadata signals before review, while there is still time to fix them.
Agentic scan
The scanner inspects build metadata and submission-readiness signals without running your app.
Scan exported IPA for App Review readiness
Static inspection. No execution. Evidence recorded for every check.
Pipeline
From upload to verified deletion, every step is tracked so the operator can confirm the scan completed safely.
Report preview
See what was found, why it matters, where it was found, and how to fix it.
Ready for submission preparation
Payload/App.app/Info.plistNSCameraUsageDescriptionFixAdd a clear purpose string explaining why camera access is needed.
13.0FixConfirm this matches your App Store listing and supported devices.
FixAdd reviewer instructions if the app requires login, demo mode, hardware, or location context.
Example data from a synthetic app. Readiness reports are guidance and evidence — not a prediction of Apple's decision.
Security
Your exported IPA is scanned for submission-readiness signals. It is not run, installed, or sent to an AI model.
Scans operate on the exported archive. Your repository never leaves your machine.
Binary contents are never transmitted to an AI model. Findings come from deterministic rules.
The uploaded build is deleted after processing, and the report shows deletion verification.
Uploads, scans, and deletions are logged so your team can confirm exactly what happened.
Who it is for
Catch avoidable rejection risks before release day — without a review team behind you.
Run a final preflight before sending client builds to review.
Reduce uncertainty when shipping fast and revising weekly.
Create a structured readiness report with evidence before every submission.
Scope
The scanner detects rejection risks and produces readiness guidance. Apple's final decision is always independent.
No. Release Preflight provides readiness guidance and risk detection. Apple's final decision is independent.
No. It scans exported IPA builds only.
Yes. The original build is deleted after processing and the report shows deletion verification.
No. Binary contents are not sent to an AI model.
Permission strings, metadata mismatches, policy-risk signals, missing values, manual review areas, and evidence-backed checks.
Yes. Reports are kept so you can compare what changed.
Private beta
Upload your exported IPA, review the findings, fix what matters, and submit with better visibility.
Readiness guidance only — not an approval prediction or guarantee.