-
-
Notifications
You must be signed in to change notification settings - Fork 744
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update docs for data and privacy (#9397)
- Loading branch information
1 parent
1b67b28
commit eee212f
Showing
7 changed files
with
103 additions
and
39 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
22 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,41 +1,46 @@ | ||
--- | ||
title: Data collection | ||
title: Data and privacy | ||
--- | ||
At Unleash, we prioritize the privacy and security of our users' data. This document provides an overview of the data collected when running Unleash. We explain the purpose of data collection and provide instructions on managing data collection settings. | ||
|
||
At Unleash, we prioritize the privacy and security of our customers' data. Our [architecture](/understanding-unleash/the-anatomy-of-unleash) ensures privacy by evaluating feature flags locally within the [client SDKs](/reference/sdks), meaning no user data is shared with the Unleash instance. | ||
|
||
:::info | ||
|
||
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**: A unique identifier and version for your Unleash instance. This ID allows us to track usage statistics and measure the adoption of Unleash across different installations and helps us ensure that you're using the latest version with the most up-to-date features and security enhancements. | ||
### Version and instance ID | ||
|
||
**Feature Usage Data**: Starting from **Unleash 5.3**, we collect additional data related to feature usage in Unleash. | ||
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. | ||
|
||
This includes the following data points: | ||
- The number of active feature flags in use | ||
- The total number of users in the system | ||
- The total number of projects in the system | ||
- The number of custom context fields defined and in use | ||
- The number of user groups defined in the system | ||
- The number of custom roles defined in the system | ||
- The number of environments defined in the system | ||
- The number of segments in active use by feature flags | ||
- The number of custom strategies defined and in use | ||
- The number of feature exports/imports made | ||
### Feature usage data | ||
|
||
All collected data is anonymous, and we only collect 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. | ||
> **Version**: `5.3+` | ||
:::info | ||
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 | ||
|
||
Unleash does not collect personally identifiable information (PII). | ||
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: | ||
|
||
## Managing data collection settings | ||
We understand that privacy preferences may vary among our users. While the data collected by Unleash is limited and anonymous, we provide options to manage data collection settings: | ||
### Disable all telemetry | ||
|
||
**Disabling All Telemetry**: If you have previously disabled the version telemetry by setting the environment variable `CHECK_VERSION` to anything other than `true`, `t`, or `1`, then both the version telemetry and the feature telemetry will be disabled. This respects your choice to opt out of all telemetry data if you had previously disabled it. | ||
Set the `CHECK_VERSION` environment variable to anything other than `true`, `t`, or `1`. This disables both version and feature telemetry. | ||
|
||
**Turning Off Feature Telemetry**: To disable the collection of the new telemetry data while still allowing the version telemetry, set the environment variable `SEND_TELEMETRY` to anything other than `true`, `t`, or `1` before starting Unleash. This will ensure that the new telemetry data is not sent, but the version information is still sent. | ||
### Disable feature telemetry | ||
|
||
We respect your privacy choices, and we will continue to honor your decision regarding telemetry. If you have any questions or concerns about managing data collection settings or privacy, please reach out to our support team for assistance. | ||
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. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters