Connect
Choose the repository that actually produces your App Store build.
APP STORE PRIVACY PREFLIGHT
Catch privacy blockers before upload.
Run a deterministic, read-only repository check against Apple-published privacy-manifest and required-reason API requirements. No prompts. No customer-code execution.
Read-only GitHub access · repeatable checks · file-level evidence · not affiliated with Apple
See the workflow →Preflight
Check PrivacyInfo.xcprivacy, app-owned required-reason API usage, and Apple-listed SDK dependencies with the same rule set every run.
Fix & rescan
Use file-level evidence, fix locally, then rerun the same checks before submission.
RELEASE CHECK, NOT GENERAL CODE REVIEW
Focus on requirements that can stop an upload.
AccessVerdict does not try to predict the entire App Review process. It starts with published privacy requirements that can be checked consistently from repository evidence.
PREFLIGHT RESULT
BLOCKER
Required-reason API detected:
NSPrivacyAccessedAPICategoryUserDefaults
No matching PrivacyInfo.xcprivacy category found
REVIEW
FirebaseCore dependency detected
Verify the submitted SDK version's privacy manifest/signatureWhy not just ask AI?
AI is useful for explaining a finding or suggesting a fix. A release preflight has a different job: run the same checks every time without depending on how a prompt was written.
Repository-wide evidence
You do not need to paste selected snippets into a chat. The scanner checks the granted repository and reports the file path, rule category, and review checklist behind each finding.
Rescan the exact same gate
After a fix, rerun the same preflight and compare the result. The value is repeatability at release time, not another one-off answer.
Validation phase · repository scans are free while we prove developers actually value this release gate
Why checkout is still off →