Bernd Machenschalk

In my understanding the GDPR doesn't allow an "opt-out", _any_ personal data which is publicly visible and in particular shared externally needs to be hidden by default. "personal data" here...

>> projects could publish that aggregated statistics and stats sites could show that without violating the GDPR > Exactly. And that's what we do. I don't think so, at least...

Regardless of the GDPR I find it nowadays questionable to require anyone to share any information that he might not want to share (for whatever reason), here in BOINC not...

I think my position boils down to: BOINC is _volunteer_ computing, and if we want to retain volunteers, we should try to satisfy their wishes and needs before ours (here:...

> For instance, `nusers_total` appears to match our "participants with credit" (on the SSP), so that would almost certainly include users who haven't opted-in the stats export, I think. Oh,...

@AenBleidd could you please elaborate on what statistical information you are missing and for what purpose you need that? You will have to specify that anyway for the data policy...

> That is quite a clear answer, from my point of view: we need to know: While I can guess the reason for collecting some of that data across projects...

The GDPR requires you to collect, process and in particular export only information that is needed for documented legitimate reasons and purpose. The possibility of a purpose you may think...

The currently available RAM and even more so disk space doesn't help you much when deciding upon a new application or project, there are e.g. user preference settings that influence...

> we had two people in the discussion who have a good and quite recent experience with the GDPR. Would it be too much to ask for to disclose who...