|
|
@@ -14,15 +14,34 @@ through Netdata Cloud. The ACLK establishes an outgoing secure WebSocket (WSS) c
|
|
|
The Cloud App lives at app.netdata.cloud which currently resolves to 35.196.244.138. However, this IP or range of
|
|
|
IPs can change without notice. Watch this page for updates.
|
|
|
|
|
|
-Netdata is a distributed monitoring system. Very few data are streamed to the cloud, such as data about:
|
|
|
- - All configured alarms and their current status
|
|
|
- - Metrics that are requested by the cloud user
|
|
|
- - A list of the active collectors
|
|
|
-
|
|
|
For a guide to claiming a node using the ACLK, plus additional troubleshooting and reference information, read our [get
|
|
|
started with Cloud](https://learn.netdata.cloud/docs/cloud/get-started) guide or the full [claiming
|
|
|
documentation](/claim/README.md).
|
|
|
|
|
|
+## Data privacy
|
|
|
+
|
|
|
+Privacy is very important to us. We firmly believe that your data belongs to you. This is why **we don't store any metric data in Netdata Cloud**.
|
|
|
+
|
|
|
+All the data that the user sees in the web browser when using Netdata Cloud, are actually streamed directly from the Netdata Agent to the Netdata Cloud dashboard. They pass through our systems, but they are not stored.
|
|
|
+
|
|
|
+We do however store a limited number of *metadata* to be able to offer the stunning visualizations and advanced functionality of Netdata Cloud.
|
|
|
+
|
|
|
+### Metadata
|
|
|
+
|
|
|
+The information we store in Netdata Cloud is the following (using the publicly available demo server `frankfurt.my-netdata.io` as an example):
|
|
|
+- The email address you used to sign up/or sign in
|
|
|
+- For each node claimed to your Spaces in Netdata Cloud:
|
|
|
+ - Hostname (as it appears in Netdata Cloud)
|
|
|
+ - Information shown in `/api/v1/info`. For example: [https://frankfurt.my-netdata.io/api/v1/info](https://frankfurt.my-netdata.io/api/v1/info).
|
|
|
+ - The chart metadata shown in `/api/v1/charts`. For example: [https://frankfurt.my-netdata.io/api/v1/info](https://frankfurt.my-netdata.io/api/v1/info).
|
|
|
+ - Alarm configurations shown in `/api/v1/alarms?all`. For example: [https://frankfurt.my-netdata.io/api/v1/alarms?all](https://frankfurt.my-netdata.io/api/v1/alarms?all).
|
|
|
+ - Active alarms shown in `/api/v1/alarms`. For example: [https://frankfurt.my-netdata.io/api/v1/alarms](https://frankfurt.my-netdata.io/api/v1/alarms).
|
|
|
+
|
|
|
+How we use them:
|
|
|
+- The data are stored in our production database on Google Cloud and some of it is also used in BigQuery, our data lake, for analytics purposes. These analytics are crucial for our product development process.
|
|
|
+- Email is used to identify users in regards to product use and to enrich our tools with product use, such as our CRM.
|
|
|
+- This data is only be available to Netdata and never to a 3rd party.
|
|
|
+
|
|
|
## Enable and configure the ACLK
|
|
|
|
|
|
The ACLK is enabled by default, with its settings automatically configured and stored in the Agent's memory. No file is
|
|
|
@@ -129,3 +148,4 @@ If you changed the runtime setting in your `var/lib/netdata/cloud.d/cloud.conf`
|
|
|
Restart your Agent and [claim your node](/claim/README.md#how-to-claim-a-node).
|
|
|
|
|
|
[](<>)
|
|
|
+
|
Odysseas Lamtzidis