/plushcap/analysis/launchdarkly/using-launchdarkly-to-target-personally-identifiable-information-pii-during-feature-flag-evaluation-without-leaking-sensitive-data

Using LaunchDarkly To Target Personally Identifiable Information (PII) During Feature Flag Evaluation Without Leaking Sensitive Data

What's this blog post about?

InVision uses LaunchDarkly as its feature flag service provider, which has significantly changed how teams think about feature deployment. One notable feature is the ability to mark certain user data as "private," allowing Personally Identifiable Information (PII) to be used in rule targeting without leaking beyond the application's boundaries. The most challenging aspect of using LaunchDarkly is understanding its user targeting mechanism, which involves syncing targeting rules with an application's local cache through asynchronous streaming. This approach enables designing targeting rules that depend on information only known by the client, such as email addresses marked as private. By denoting specific fields as "private," LaunchDarkly allows for safe targeting of PII while ensuring data security and compliance with privacy regulations.

Company
LaunchDarkly

Date published
April 24, 2018

Author(s)
Ben Nadel

Word count
871

Language
English

Hacker News points
None found.


By Matt Makai. 2021-2024.