lee/caprover
1
0
Fork 0
mirror of https://github.com/caprover/caprover synced 2025-12-11 05:46:12 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Updated terms

Browse Source
This commit is contained in:
Kasra Bigdeli
2023-08-06 17:38:54 -07:00
parent 926d71db8a
commit 37d4f092f7
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
TERMS_AND_CONDITIONS.md
View File

@@ -21,7 +21,7 @@ CapRover developers will do their best to ensure that CapRover remains functiona
### Analytics
CapRover has built in anonymous usage analytics starting v1.11. CapRover **never** sends any private data, such as env vars, private images, etc. This data is only used to understand usage patterns of CapRover and optimize the experience for the users. For example, in the future, we will add download counts to one click apps. If you wish to disable anonymous analytics, you can do so by passing an env variable CAPROVER_DISABLE_ANALYTICS=true to CapRover service. In the future, we will use this information to find out which one click apps are popular, whether or not we should focus on supporting multiple nodes (percentage of single node vs multi node), whether or not we should invest in supporting multi CPU clusters, and etc.
CapRover has built in anonymous usage analytics starting v1.11. CapRover **never** sends any private data, such as env vars, private images, etc. This data is only used to understand usage patterns of CapRover and optimize the experience for the users. For example, in the future, we will have the possibility to add download counts to one click apps. If you wish to disable anonymous analytics, you can do so by passing an env variable CAPROVER_DISABLE_ANALYTICS=true to CapRover service. In the future, we will use this information to find out which one click apps are popular, whether or not we should focus on supporting multiple nodes (percentage of single node vs multi node), whether or not we should invest in supporting multi CPU clusters, and etc.
### Future changes