For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Sign inTry it free
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
  • Get started
    • Overview
    • Onboarding
    • Get started
    • Launch Insights
    • LaunchDarkly architecture
    • LaunchDarkly vocabulary
  • AgentControl
    • AgentControl
    • Manage AgentControl
      • Compare config variation versions
      • AgentControl and information privacy
  • Feature flags
    • Create flags
    • Target with flags
    • Flag templates
    • Manage flags
    • Code references
    • Contexts
    • Segments
  • Releases
    • Releasing features with LaunchDarkly
    • Release policies
    • Percentage rollouts
    • Progressive rollouts
    • Guarded rollouts
    • Feature monitoring
    • Release pipelines
    • Engineering insights
    • Release management tools
    • Applications and app versions
    • Change history
    • Restoring previous flag versions
  • Observability
    • Observability
    • Session replay
    • Error monitoring
    • Logs
    • Traces
    • Observability metrics
    • Product analytics events
    • LLM observability
    • Alerts
    • Dashboards
    • Service map
    • Vega for auto-remediation
    • Observability MCP server
    • Search specification
    • Observability settings
    • Observability integrations
  • Experimentation
    • Experimentation
    • Experiment metric types
    • Experiment configuration
    • Managing experiments
    • Analyzing experiments
    • Multi-armed bandits
    • Holdouts
  • Metrics and events
    • Metrics in LaunchDarkly
    • Creating metrics
    • Metric groups
    • Events
    • Autogenerated metrics
  • Warehouse native
    • Warehouse native metrics
    • Setting up external warehouses
    • Creating experiments using warehouse native metrics
  • Infrastructure
    • Connect apps and services to LaunchDarkly
    • LaunchDarkly in China and Pakistan
    • LaunchDarkly in the European Union (EU)
    • LaunchDarkly in federal environments
    • Public IP list
  • Your account
    • Projects
    • Views
    • Environments
    • Tags
    • Teams
    • Members
    • Roles
    • Account security
    • Feature previews
    • Billing and usage
    • Changelog
Sign inTry it free
LogoLogo
On this page
  • Overview
  • Privacy and PII in LaunchDarkly
  • LaunchDarkly and AI models
  • Online evaluations and provider credentials
AgentControlManage AgentControl

AgentControl and information privacy

Was this page helpful?
Previous

Create flags

Next
Built with

Overview

This topic describes how the LaunchDarkly AgentControl 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 PII, including names, email addresses, or other unique identifiers, depending on how you define your context attributes.

AgentControl works similarly to LaunchDarkly feature flags with respect to PII in end-user data. Specifically:

  • We recommend that you use private attributes when you target on 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 messages in your config variations. 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

When you work with AgentControl, LaunchDarkly does not send prompts, context attributes, or variation configuration to any AI provider. LaunchDarkly does not proxy model responses and does not use any information you provide to fine-tune or train any models. This includes information you provide when you create a config and its variations, as well as information included in context attributes. If you choose to use AgentControl playgrounds or evaluations, you will be required to input API keys from your model providers. LaunchDarkly will send your prompts, context attributes, and evaluation criteria to the models and API providers you specify using your credentials, under the terms of your existing agreements.

If you use variables within your config variation messages, either from a context attribute or directly from your application, LaunchDarkly substitutes the values of those variables into the message. 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 messages in your config variations.

Online evaluations and provider credentials

When you use online evaluations or custom judges, evaluation runs entirely within your application process. Your application calls the model provider directly using your configured provider credentials. The AI SDK provides the judge configuration and tracks evaluation results, but it does not independently invoke the model provider.

LaunchDarkly does not proxy model provider requests. The model provider receives only the prompts and parameters that your application sends.