You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I realised, by looking at the code only, that some stats about use appear to be sent by default to a remote database.
Although I understand the benefits of such stats as a tool builder, in particular during a beta, I find it problematic that it is not advertised clearly in the readme, with instructions to opt-out, or a completely opt-in operation instead (RGPD compliance etc).
I doubt most users will realise that (especially when using the Docker version), so I'm creating an issue to give a bit of visibility to this topic.
I realised, by looking at the code only, that some stats about use appear to be sent by default to a remote database.
Although I understand the benefits of such stats as a tool builder, in particular during a beta, I find it problematic that it is not advertised clearly in the readme, with instructions to opt-out, or a completely opt-in operation instead (RGPD compliance etc).
I doubt most users will realise that (especially when using the Docker version), so I'm creating an issue to give a bit of visibility to this topic.
DATA4PTTools/cmd/validate.go
Lines 27 to 32 in c9c2573
DATA4PTTools/cmd/validate.go
Line 73 in c9c2573
DATA4PTTools/cmd/validate.go
Line 103 in c9c2573
DATA4PTTools/cmd/validate.go
Lines 221 to 222 in c9c2573
DATA4PTTools/cmd/validate.go
Lines 226 to 257 in c9c2573
The text was updated successfully, but these errors were encountered: