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.
13.5kProductPricingSign inStart free trialBook a demo
DocsAPIsSDKsEnterprise EdgeGuidesAcademyRelease notes
DocsAPIsSDKsEnterprise EdgeGuidesAcademyRelease notes
    • Home
  • Get started
    • Quickstart
    • Introduction to feature flags
    • Unleash architecture overview
  • Core concepts
    • Overview
    • Import and export
      • Data collection and privacy

Unleash reduces the risk of releasing new features, drives innovation by streamlining the software release process, and increases revenue by optimizing end-user experience. While we serve the needs of the world's largest, most security-conscious organizations, we are also rated the “Easiest Feature Management system to use” by G2.

GitHubGitHubLinkedInLinkedInX (Twitter)X (Twitter)SlackSlackStack OverflowStack OverflowYouTubeYouTube

Server SDKs

  • Node.js
  • Java
  • Go
  • Rust
  • Ruby
  • Python
  • .NET
  • PHP
  • All SDKs

Frontend SDKs

  • JavaScript
  • React
  • Next.js
  • Vue
  • iOS
  • Android
  • Flutter

Feature Flag use cases

  • Secure, scalable feature flags
  • Rollbacks
  • FedRAMP, SOC2, ISO2700 compliance
  • Progressive or gradual rollouts
  • Trunk-based development
  • Software kill switches
  • A/B testing
  • Feature management
  • Canary releases

Product

  • Quickstart
  • Unleash architecture
  • Pricing
  • Product vision
  • Open live demo
  • Open source
  • Enterprise feature management platform
  • Unleash vs LaunchDarkly

Support

  • Help center
  • Status
  • Changelog
Made in a cosy atmosphere in the Nordic countries.Copyright © 2026 Unleash
LogoLogo
13.5kProductPricingSign inStart free trialBook a demo
On this page
  • What data is collected
  • Manage data collection settings
Data privacy and compliance

Data and privacy

||View as Markdown|
Was this page helpful?
Previous

Compliance for feature flags

Next
Built with

At Unleash, we prioritize the privacy and security of our customers’ data. Our architecture ensures privacy by evaluating feature flags locally within the client SDKs or Unleash Edge, meaning no user data is shared with the Unleash instance.

Unleash does not collect any personally identifiable information (PII).

Unleash collects anonymous usage counts to help measure usage statistics and improve the product. The following sections explain what data we collect and how you can manage data collection settings.

What data is collected

When running Unleash, we collect the following data:

Version and instance ID

We collect a unique identifier and version number for your Unleash instance. This ID allows us to measure usage statistics and the adoption of Unleash across different installations. It also helps us ensure that you’re using the latest version with the most up-to-date features and security enhancements.

Feature usage data

v5.3

To improve Unleash, we collect anonymous usage statistics:

  • Number of active feature flags
  • Number of projects, environments, users, user groups, and custom roles
  • Number of active segments, custom strategies, and custom context fields
  • Number of times features flags have been exported or imported

All collected data is anonymous and limited to usage counts. This data helps us understand how features are used in Unleash, enabling us to prioritize important features and make informed decisions about deprecating features that are no longer relevant to our users.

Manage data collection settings

We recognize that privacy requirements differ across organizations. While the data collected by Unleash is limited and anonymous, we provide options to manage data collection settings:

Disable all telemetry

Set the CHECK_VERSION environment variable to anything other than true, t, or 1. This disables both version and feature telemetry.

Disable feature telemetry

Set the SEND_TELEMETRY environment variable to anything other than true, t, or 1 before starting Unleash. This disables feature telemetry while still allowing version tracking.