Connect iOS SDK privacy manifest
Apple requires the data your app and its third-party SDKs collect to be declared in PrivacyInfo.xcprivacy. This page lists what the Connect iOS SDK collects, the required-reason APIs it uses, and its tracking-domain status. For background on the manifest format, see Privacy manifest files.
ImportantCustomers are responsible for writing their own privacy manifest. The information below is intended for reference.
On this page, "customer" refers to the application's developer (Acoustic's customer), and "user" refers to the end user of the application.
Languages: Swift and Objective-C
Availability: Pro, Premium, and Ultimate
Collected data
Apple requires the categories of data collected by your app or its third-party SDKs — including the Connect SDK — to be declared in the privacy manifest. For more information, see Describing data use in privacy manifests.
NoteIf your app uses multiple third-party SDKs, packages, or plug-ins, each provider supplies its own privacy manifest entries.
The Connect SDK does not link any of the data it collects to individual users, and does not use any of it for tracking. The table below lists the categories collected when configured by the customer.
| Category | Data type | Purpose | Description |
|---|---|---|---|
| Location | Precise location | Developer's Advertising or Marketing; App Functionality: Product Personalization | When captured, precise location data is used to group application users by geographic area for general reporting purposes. |
| Coarse location | Developer's Advertising or Marketing; App Functionality: Product Personalization | When captured, coarse location data is used to group application users by geographic area for general reporting purposes. | |
| Identifiers | User ID | Developer's Advertising or Marketing; App Functionality: Product Personalization | When captured, user identifiers are used for app functionality. |
| Device ID | Developer's Advertising or Marketing; App Functionality: Product Personalization | When captured, device identifiers are used for app functionality. | |
| Usage data | Product interaction | Developer's Advertising or Marketing; App Functionality: Product Personalization | When captured, application interaction data is used to optimize the application's performance and usability. |
| Diagnostics | Crash data | App Functionality | When captured, crash data is used to optimize the application's performance and usability. |
| Performance data | App Functionality | When captured, performance data is used to optimize the performance and usability of the application. |
Required reason API usage
Apple lists some APIs that have the potential of being misused to access device signals to identify the device or the user, known as fingerprinting. Regardless of whether a user gives your app permission to track, fingerprinting is not allowed.
These APIs may have been used to deliver core functionality and are required by Apple to be declared in the privacy manifest with reasons. For more information, see Describing use of required reason API.
The Connect SDK uses the following APIs, with the reasons declared:
| API type | Reason | Description |
|---|---|---|
| NSPrivacyAccessedAPICategoryUserDefaults | CA92.1 | Used to access user defaults set in the app to persist SDK settings. |
| NSPrivacyAccessedAPICategoryFileTimestamp | C617.1 | Used to access timestamps of the files in the app. |
| NSPrivacyAccessedAPICategoryDiskSpace | E174.1 | Used to access the available disk space in the app. |
Tracking domains
The Connect SDK does not track any data protected by the App Tracking Transparency framework. Tracking is set to false in the Connect privacy manifest.
Updated 2 days ago
