App Store Privacy
Digia Engage's iOS SDK and its Flutter plugin each ship an Apple privacy manifest
(PrivacyInfo.xcprivacy). Xcode merges it into your app when you build, so Digia Engage shows up
in your app's privacy report, and you can use that report to fill in App Store Connect's App
Privacy section. Nothing needs to be configured.
To see the merged report, archive your app in Xcode, then open the archive in the Organizer, right-click it and choose Generate Privacy Report.
Tracking
Digia Engage does not track users in Apple's sense. It sets NSPrivacyTracking to false and
lists no tracking domains, so it needs no App Tracking Transparency prompt.
Data Digia Engage collects
Each type is collected for App Functionality and Analytics. None of it is used for tracking.
It is linked to the user once your app calls Digia.setUserId; before that,
it is tied only to an anonymous device ID.
| App Store Connect data type | What Digia Engage records |
|---|---|
| Device ID | An anonymous device identifier |
| User ID | The ID your app passes to setUserId |
| Product Interaction | Campaign impressions, clicks and dismissals |
| Other Diagnostic Data | SDK health diagnostics |
| Other User Content | Answers to Digia Engage surveys |
Required-reason APIs
| API category | Reason | Why |
|---|---|---|
| File timestamp | C617.1 | Managing the cache of campaign media |
| User defaults | CA92.1 | Storing the SDK's own state, local to your app (iOS SDK only) |
The Flutter plugin stores its state through shared_preferences, which ships its own manifest, so
the plugin itself declares only the file timestamp reason.