Full-lifecycle Apple App Store review for iOS and iPadOS apps. Use for pre-submission audits, rejection diagnosis and Resolution Center replies, Guideline 4.3 spam or similarity recovery, human-craft and low-effort audits, App Review Notes, privacy manifests, Info.plist permission strings, subscriptions, Sign in with Apple, account deletion, UGC, third-party AI consent, TestFlight or App Store readiness, and vague requests such as "review my app" or "will Apple approve this" when an Xcode, Expo, React Native, or Flutter project is present. Produces evidence-tagged Markdown, JSON, and a self-contained visual HTML report, runs a read-only deterministic scan first, and only offers grouped fixes after the report.
95
94%
Does it follow best practices?
Impact
99%
1.67xAverage score across 3 eval scenarios
Passed
No findings from the security scan
4.3(b) rejection recovery for weather app
4.3(b) vs 4.3(a) distinction
20%
100%
Response classification
50%
100%
Exact rejection message preserved
62%
100%
Resolution Center reply present
100%
100%
Build number placeholder or reference
100%
100%
Attachments listed
100%
100%
No code obfuscation recommendation
100%
100%
No unsupported provenance claim
75%
75%
Fast review timeline not mischaracterized
87%
100%
Evidence confidence labels
0%
100%
No invented evidence
37%
100%
No AI-detection claim
100%
100%
Expo app full pre-launch review with extension targets
Mode A declared first
0%
100%
Mode C declared
0%
100%
Expo config cited as evidence
87%
100%
Fix targets app.json or plugin
87%
100%
Share extension reviewed separately
87%
100%
MANUAL CHECK for absent ios/ directory
25%
100%
Missing camera purpose string identified
0%
100%
Policy verification date recorded
57%
100%
ITMS-91053 absent
100%
100%
Five Mode C interventions
0%
100%
All five Mode C dimensions graded
0%
100%
No files modified
100%
100%
Fix plan section present
44%
100%
HTML report generation from reviewed audit JSON
Script invocation
0%
100%
No remote assets
100%
100%
System typography
100%
100%
Amber accent only
30%
100%
No forbidden design patterns
0%
100%
JSON-only findings
100%
100%
All three paths reported
100%
100%
Verification documented
30%
100%
Verdict in summary
100%
100%
No Markdown in JSON
100%
100%