Privacy policy clauses for LaunchDarkly
LaunchDarkly is a feature management and experimentation platform that allows websites to control which features are visible to users, run A/B tests, and collect experiment results. It evaluates feature flags server-side or client-side to enable dynamic feature rollouts and user segmentation.
Free scan · No signup · Results in 60 seconds
What data LaunchDarkly collects
Your privacy policy must disclose each of the following data types when you use LaunchDarkly.
When does LaunchDarkly trigger privacy obligations?
Data Flow Activation
The moment you integrate LaunchDarkly's SDK into your application, user context attributes (key, email, name, and any custom attributes you define) are transmitted to LaunchDarkly's servers in the United States for flag evaluation. This happens on every page load or app session where a user is identified. This data flow—not a privacy policy alone—triggers obligations.
Regulatory Thresholds
GDPR (EEA users): If any of your users are in the EEA, GDPR Article 4(1) classifies user context data as personal data. You must have a lawful basis (Article 6) for sending it to LaunchDarkly. Consent under Article 7 is one option; legitimate interest (Article 6(1)(f)) requires a documented balancing test. You also need a Data Processing Agreement (DPA) with LaunchDarkly under Article 28(3).
