[wp-trac] [WordPress Trac] #43492: Core Telemetry and Updates

[WordPress Trac]

#43492: Core Telemetry and Updates
------------------------------+------------------------------
 Reporter:  xkon              |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Upgrade/Install   |     Version:
 Severity:  normal            |  Resolution:
 Keywords:  gdpr 2nd-opinion  |     Focuses:
------------------------------+------------------------------

Comment (by DavidAnderson):

 @azaozz I think you might be using a 'personal' definition of 'personal
 data'. Under the *GDPR's* definition, it is not the case that some data is
 'personal' and other data isn't. *All* linked data is personal as soon as
 *any* of it can be _associated_ with an _identifiable_ person - see:
 https://core.trac.wordpress.org/ticket/43492#comment:14 . (And things like
 whether it can be obtained elsewhere or not is not relevant).

 The key from a GDPR POV, as I understand it, is that the GDPR doesn't
 offer exceptions for things like "if the user decided to put their name in
 the URL or on the 'About' page of their website, that's their problem".
 It's reasonably forseeable that many URLs sent in updates checks are
 "identifiable" with a person (in distinction to, e.g. if they decided to
 put it in the name of a customised plugin); generally, the GDPR's rules
 all apply *without any distinction based upon how you obtained that data*
 (or whether it was already public by some other means, etc.). These
 attributes are the deliberate intention of the GDPR; it's not loose
 wording or a mistake; that result is exactly what they are trying to
 achieve.

 N.B. WHOIS may be killed by GDPR, according to many news sources.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/43492#comment:24>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform