What privacy manifests and permission copy prove: declarations versus runtime and sites

A declaration is not whole-path acceptance or proof that data never leaves

Current PrivacyInfo.xcprivacy lists UserDefaults/FileTimestamp accessed-API categories and reason codes. Info.plist separately contains microphone/camera purpose text and other configuration. These are source declarations/copy, not audits of every runtime entry, third-party page or later handoff. They establish neither zero collection, App Store review nor legal/privacy certification.

Different from redaction, file options and service privacy

Redaction concerns content, protection concerns actual writes, sites/services have separate scopes. Here static declarations within an evidence chain matter. No legal conclusion, private-data access, request or permission change occurs.

Check Verified scope Manual review Not established
PrivacyInfo Lists NSPrivacyAccessedAPITypes Actual file/version All runtime data flows audited
Categories/reasons UserDefaults/FileTimestamp and CA92.1/C617.1 Only listed source scope Invent missing Tracking/CollectedData fields
Info.plist copy Mic/camera purpose text Copy versus entry implementation One sentence proves every path
Background configuration audio etc. declared Actual runtime/system evidence All locked/low-power scenarios guaranteed
Native/pages Different code/service scopes Scripts/Cookies/accounts/later actions Native declarations cover every site
Local ASR/handoff Separate stages Actual destination/upload/send Local recognition means data never leaves
Distribution/review Files are not external acceptance Real release evidence Unverified App Store/sameAs
Retention evidence Version/declarations/tests separated Actually reviewed scope Security/privacy/legal certification

Synthetic declaration note

Known: two API categories are declared in fixed source. Unknown: every device path, third-party page and destination’s processing. Report reviewed declarations, not whole-chain zero collection/compliance.

Absent fields do not automatically create runtime guarantees. Preserve copy, choice, implementation and actual network/destination evidence separately. No store identity, certification or privacy test is supplied.

FAQ

Is PrivacyInfo a complete runtime audit?

No. Source declarations differ from actual flows/third-party evidence.

Does an absent collection field prove whole-chain zero collection?

No. Invent neither meanings nor coverage.

Does purpose copy replace testing every entry?

No. Native/shortcut/page/later actions need implementation-specific evidence.

Does local ASR mean later text is never uploaded?

No. Recognition and authorized handoff/services differ.

Does a manifest prove App Store release/review?

No. Do not generate unverified store links/sameAs.

Is legal/privacy certification provided?

No. Static evidence scope only, without testing or compliance conclusions.

Reading and source

File options · Sensitive content layers · Shell/services · Actual handoff · Start · Privacy

Actual API declarations · Purpose/background settings · Native/workbench boundaries