How can we help?
For installation, licensing, or audit questions, email the PreflightKit support inbox. Include the agent you are using and the report section you are stuck on.
Common questions
My agent already reviews my code. Why do I need this?
Because App Review doesn’t review your code. It reviews the signed archive, the privacy manifests, the store listing, and what happens on a fresh account. Your agent won’t open those unless something tells it to. PreflightKit tells it to, and gives it a scanner to read them with.
What does it check that Xcode doesn’t?
Xcode tells you the archive can be uploaded. PreflightKit tells you whether it survives review: privacy manifests against real SDK behaviour, metadata claims against the binary, purchase and account-deletion flows against the guidelines, and whether a reviewer can reach your core feature at all.
Does PreflightKit send my code anywhere?
No. PreflightKit runs locally and never sends your code, your archive, or your report to us. Your agent keeps working exactly as it does today, with whichever model provider you already use.
What if review still comes back with something?
You answer it the same afternoon. Every result in your last run carries the command, artifact, or observation behind it, and rejection-response support is built in.
What happens when the guidelines change?
The checks move with them. Guideline changes ship as updates, and every update is yours for the life of the product, including new major versions.
How many machines does one license cover?
Three. Activation happens at install, so a machine that’s set up keeps working offline.
What do I need to run it?
Your app’s repository and the agent you already use. For the full audit: macOS with the Xcode you’ll submit from, signing access, a test account, and your App Store Connect metadata.