Apple App Store data collection policy

Overview

This topic explains the implications of using a LaunchDarkly SDK in an app you submit to the Apple App Store.

Since December 2020, the Apple App Store requires apps you submit to provide information about their privacy practices, including the practices of third-party partners whose code is integrated into the app. If you integrate a LaunchDarkly SDK into your app and submit it to the Apple App Store, you must disclose which data LaunchDarkly collects.

We're providing this topic to help facilitate the submission process. Read this topic to understand which SDKs are impacted by the Apple App Store's policy and learn about what kind of data our SDKs collect.

To learn more, read App privacy details on the App Store.

Affected SDKs

You can use these SDKs to build apps for Apple's platforms:

• Flutter
• iOS
• React Native
• Xamarin

This topic applies to each of these SDKs unless otherwise specified.

To learn more about how Apple uses the below data types, read Apple's documentation.

Collection practices

The tables below summarize the data that LaunchDarkly SDKs collect by default. These tables do not include optional fields you can provide when you use an SDK.

Contact info

This table explains the contact information LaunchDarkly SDKs collect by default:

Health and fitness

This table explains the personal health and fitness information LaunchDarkly SDKs collect by default:

Financial info

This table explains the financial information LaunchDarkly SDKs collect by default:

Location

This table explains the location information LaunchDarkly SDKs collect by default:

Sensitive info

This table explains the sensitive information LaunchDarkly SDKs collect by default:

Contacts

This table explains the contacts information LaunchDarkly SDKs collect by default:

User content

This table explains the user content information LaunchDarkly SDKs collect by default:

Browsing history

This table explains the browsing history LaunchDarkly SDKs collect by default:

Search history

This table explains the search history LaunchDarkly SDKs collect by default:

Identifiers

LaunchDarkly SDKs collect user IDs so you can target by individual users. While the SDKs require you to provide user IDs, your application code is responsible for defining them. To learn more, read your SDK's reference page.

This table explains the indentifier information LaunchDarkly SDKs collect by default:

Purchases

This table explains the purchase information LaunchDarkly SDKs collect by default:

Usage data

LaunchDarkly collects details about flag evaluations. This data powers LaunchDarkly features such as flag statuses, flag insights, and Experimentation.

You can opt out of publishing usage events to LaunchDarkly. To learn more about your SDK configuration options, read your SDK's reference page.

This table explains the usage data LaunchDarkly SDKs collect by default:

Diagnostics

Versions 5.0.0 and later of the iOS SDK, and all versions of the Flutter SDK, publish diagnostics to LaunchDarkly. Older versions of the iOS SDK, and all versions of the React Native and Xamarin SDKs, do not publish diagnostics to LaunchDarkly.

You can opt out of publishing diagnostics to LaunchDarkly. To learn more about your SDK configuration options, read your SDK's reference page.

This table explains the diagnostics information LaunchDarkly SDKs collect by default:

Other data

LaunchDarkly's mobile SDKs collect high-level information about devices and their operating systems so you can target on these attributes. You may override these values if you do not want LaunchDarkly to collect this information. To learn more, read your SDK's reference page.

This table explains the device and operating system information LaunchDarkly SDKs collect by default:

To learn more about how Apple uses these data types, read Apple's documentation.

LaunchDarkly's privacy policy

We have a clearly written, transparent privacy policy that explains how we collect, disclose, and use member data.

To learn more, read our Privacy policy.