10000app
10000app #0101 · PMF pre-judgment 81/100 · $12 one-time release evidence pack under strong Xcode, App Store Connect and vendor-native substitutes

The app has a manifest.
Does every SDK own its truth?

Map three sanitized components before submission and expose missing, unknown, stale or unowned evidence across the exact build handoff. A complete row proves only that a responsibility record exists—not that PrivacyInfo.xcprivacy is valid or Apple will accept the build.

Map three components locally核对依据
Free · browser-only

App + SDK privacy-manifest evidence map

State contract
required_reason_api_state: declared_current, none_found_human, undeclared_or_mismatch, unknown · data_collection_state / tracking_domain_state: declared_current, none_declared_human, mismatch_or_unknown · signature_state: valid_current, not_required_human, missing, unknown · decision: pass, hold, escalate.
Release gateADD COMPONENT RECORDS
Valid / invalid / duplicate0 / 0 / 0
Recorded / review / cannot tell0 / 0 / 0
Manifest / API-reason gaps0 / 0
Data / tracking gaps0 / 0
Signature / stale-source gaps0 / 0
Boundary fixtures0 / 10
Component / versionTypeManifest / API reasonData / trackingSignatureEvidence / source / ownerDecisionNarrow result

Release evidence and human review queue

    “Evidence recorded” means only that the abstract current-version states, safe reference, owner and decision are internally present. This page did not inspect PrivacyInfo.xcprivacy, discover API calls or data behavior, verify a signature, select an approved reason or submit a build.

    Mobile release and privacy boundary: all free analysis stays in this browser. Enter only synthetic aliases and safe internal references. Never paste a bundle/package ID, source code, plist, build or binary, SDK archive, real vendor, domain, tracking list, certificate, signature, hash, Team ID, account, token, personal data or unpublished security material. This page does not scan a build, parse a manifest, discover API use, select an approved reason, determine data collection or tracking, validate an SDK signature, provide legal advice, change code or submit to App Store Connect. Authorized mobile engineering, privacy, legal and release owners control every real decision.

    Source ledger

    Current Apple requirements and strong native substitutes

    PMF pre-judgment 81/100 · $12 one-time release evidence pack under strong Xcode, App Store Connect and vendor-native substitutes

    Apple · Privacy manifest filesPrimary documentation separates data collection, required-reason API and tracking-domain declarations across apps and third-party SDKs.Apple · Describing required-reason APIsApps and SDKs must truthfully declare approved reasons for covered API categories; this abstract map cannot choose or validate those reasons.Apple · Adding a privacy manifestCurrent App Store Connect submission requirements and invalid-manifest rejection make the release trigger real; Xcode and App Store Connect remain the controlling validators.