From 78e9e1ce38e9723299324cc3f1e03390981e955d Mon Sep 17 00:00:00 2001 From: Grzegorz Bokota Date: Tue, 12 Sep 2023 11:35:46 +0200 Subject: [PATCH] add gdpr information --- docs/naps/8-telemetry.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/naps/8-telemetry.md b/docs/naps/8-telemetry.md index 0c1635e51..e1dbed3ab 100644 --- a/docs/naps/8-telemetry.md +++ b/docs/naps/8-telemetry.md @@ -130,6 +130,14 @@ I do not expect that it is a high risk, but exists. We could address it by code Another option is to scan public plugins and their dependencies. This is simpler but will require establishing additional communication channels to be able to warn users about the potential problem. +## GDPR compatybility + +I'm almost sure that we will not collect data that are covered by GDPR. But to get better atmosphere +we need to add instruction how user could retrive his unique identifier and setup a process +for requests to remove data from the server. It is not high propability of usage as life span of data is short, +but we need to be prepared for such a situation. I suggest to use e-mail for that. + + ## Backward Compatibility