SDK PRIVACY REVIEW
Review Firebase privacy-manifest evidence before App Store upload.
Firebase is not one dependency: apps can ship multiple Firebase modules. Inventory the exact submitted SDK versions and confirm the privacy-manifest/signature expectations that apply to them.
INVENTORY
Start from the dependency files used by the build
AccessVerdict looks for common Firebase modules in Podfile, lockfiles, Package.swift/Package.resolved, and mobile dependency manifests.
VERSION
Confirm the exact version in the submitted build
A dependency-name match is a REVIEW finding, not proof of a rejection. Confirm the version that is actually packaged and whether it ships the required privacy manifest and signature.
APP CODE
Keep app-owned required-reason APIs separate
An SDK privacy manifest does not automatically cover required-reason API use in your own app code. Review both sources of evidence.
FINAL BUILD
Verify the generated privacy report before submission
The repository preflight is an early release gate. The final built product can contain generated or binary evidence not visible to a source-only scan.