The response times are recalculated on a daily basis and are based on the time a user takes to respond to their PMs over a certain time interval. Admin users are excluded.
Configuration
Setting
What it does
user response times mode
Determines the algorithm used. Either percentile or average. Default percentile.
user response times percentile
Used with mode percentile. Determines the percentile used in the calculation. Range 1-100. 100 is the maximum response time. 50 is the median. Recommended (and default) value is 80.
user response times days
The number of days that the calculation looks back. Default 60.
When you change these values you need to manually trigger the Jobs::UpdateResponseTimes job (or wait up to 24 hours).
What do you mean by that? That isn’t such piece of data that GDPR controls, but if you like you can tell to users why it is collected, why it is needed, how it is stored and for what it is needed. If you have legit reason for all those point everything is GDPR friendly.
Those points should be considered anyway, because the answer tells right away if it is really needed or would it be just another decorative add from class nice to have, but no one isn’t actually interested
But still — knowing response time is not such data that can or would use identify a user.
However, it uses information that is already there, it’s not storing extra data. It’s not more or less GDPR-friendly than the other activity of a user on a forum. And the data is averaged, it does not give away concrete data points.
The whole idea about the plugin is to make the information available between users, so making it available to staff only is outside of what I think would be meaningful use. I would accept a PR.
