auditing-ios-app-group-and-pasteboard-exposurelisted

# Auditing iOS app group and pasteboard exposure: when a secret leaves the app through a shared door An iOS app is meant to be a sealed container, but it has several legitimate doors through which data leaves: an app-group container it shares with its own extensions, a shared keychain access group, the general pasteboard any app can read, and the state the system captures in snapshots or hands to extensions. Each door is fine for data whose sensitivity tolerates the audience on the other side, and a leak when a secret goes through a door wider than it should. A token written to an app-group container is readable by every extension and app in that group; a secret in an over-broad shared keychain group is reachable by apps that should not have it; a value copied to the general pasteboard is readable by any app, including ones the user never launched deliberately; and sensitive data left on screen or in memory lands in a snapshot or an extension context. The bug is a sensitive value on a shared surface whose audience exceeds the app's own boundary. You audit these by listing what the app writes to each shared surface and who can read it. ## When to use - An iOS app shares data with its own extensions through an app group or a shared keychain access group. - The app copies or exposes values through the general pasteboard or hands data to an extension. - Sensitive data may appear in a snapshot, a shared container, or a channel other apps can read. ## Scope check Audit shared-