No results for ""
EXPAND ALL
  • Home
  • API docs

AI configs and information privacy

Read time: 2 minutes
Last edited: Nov 08, 2024

Overview

This topic describes how the LaunchDarkly AI configs product treats personally identifiable information (PII).

Privacy and PII in LaunchDarkly

End-user data is information about your customers that your application sends to LaunchDarkly as part of a context. End user data can include personally identifiable information (PII), including names, email addresses, or other unique identifiers, depending on how you define your context attributes.

The AI configs product works similarly to LaunchDarkly feature flags with respect to personally identifiable information (PII) in end-user data. Specifically:

  • We recommend that you use private attributes when you target on personally identifiable information (PII) or other sensitive data. To learn more, read Minimizing LaunchDarkly's access to end user data.
  • If your organization prohibits sending PII to AI providers, then you must take care not to include PII in any of the context attributes that you reference in the prompts in your AI config versions. LaunchDarkly does not have guardrails that prevent you from sending PII from your application to LaunchDarkly, or from LaunchDarkly to a third-party, such as an AI model.

LaunchDarkly and AI models

LaunchDarkly is not integrating directly into the response from any AI provider.

When you work with AI configs, LaunchDarkly does not send any of the information you provide to any AI provider or model, and does not use any of the information your provide as part of an AI config to fine tune any models. This includes information you provide when you create an AI config and its versions, as well as the information you provide in context attributes.

If you use variables within your AI config version prompt, either from a context attribute or directly from your application, LaunchDarkly does substitute the values of those variables into the prompt. If your organization prohibits sending PII to AI providers, then you must take care not to include PII in any of the variables that you reference in the prompts in your AI config versions.