Privacy, permissions and Apple manifests#

Permissions#

BrainAccessKit never requests UI permissions. Consumer apps add the Bluetooth usage description and present any explanatory UI they need. CoreBluetooth does not require location permission on iOS.

Privacy manifest shipped by the SDK#

BrainAccessCore contains UserDefaultsConfigStore, which reads and writes per-headset device configuration when an app opts into persistent config storage. Apple’s required-reason API guidance says SDKs must declare their own required-reason API use in the SDK’s manifest; the host app’s manifest does not cover SDK code.

BrainAccessKit ships Sources/BrainAccessCore/PrivacyInfo.xcprivacy and packages it for source SwiftPM consumers and prebuilt BrainAccessCore.xcframework consumers. The manifest declares:

  • NSPrivacyAccessedAPICategoryUserDefaults

  • reason C56D.1

Apple’s current UserDefaults reason text says C56D.1 is for a third-party SDK that provides a wrapper function around UserDefaults APIs for the app to use, only accesses UserDefaults when the app calls that wrapper, is not primarily a required-reason API wrapper, and does not use or send the accessed information for the SDK’s own purposes. That maps to UserDefaultsConfigStore: the SDK’s purpose is EEG transport, not UserDefaults wrapping; the host app explicitly opts into the store by passing it to BrainAccessClient; calls read/write only the app’s local per-headset config; and BrainAccessKit does not upload, track with, or otherwise use the stored values for SDK-owned purposes. This is why the SDK uses C56D.1 rather than app-only CA92.1.

Data handled by the SDK#

The SDK transports EEG samples, impedance values, optional motion values, battery/charging state, contact flags, device identifiers and Device Information Service strings to the consuming app. It does not upload data, start a network connection or provide analytics. Apps are responsible for their own data storage, uploads, user notices and App Store privacy answers.