[wp-trac] [WordPress Trac] #43175: Discussion - Pseudonymisation

[WordPress Trac]

#43175: Discussion - Pseudonymisation
-------------------------+------------------------------
 Reporter:  xkon         |       Owner:  (none)
     Type:  enhancement  |      Status:  closed
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  Privacy      |     Version:
 Severity:  normal       |  Resolution:  fixed
 Keywords:               |     Focuses:
-------------------------+------------------------------
Changes (by idea15):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 Great discussion Konstantinos.

 The thing about pseudonymisation is that it's not a one size fits all
 solution or requirement. It depends on the situation it's being used for,
 and the nature of the data. The guidance on when to use pseudonymisation
 is very useful for situations like academic research, big data, and
 situations where you might be aggregating information from thousands of
 data points. For your average WP database, not so much.

 What I have been advising people is that the greater the chance that
 pseudonymised data can be matched with other data to be identified, the
 greater the risk of using it. Making it too easy to pseudonymise data,
 through an automated tool for example, would play into that.

 I'm also not sure on an example of where an average WP admin would need to
 use a pseudonymisation tool. If you are going to be doing that, it's going
 to be on a raw database export, not within the WP back end. (Would love to
 hear differing opinions or imaginings of how it could work.)

 So there's certainly scope to create pseudonymisation tools and functions,
 but IMHO it would be overkill to put them into core.

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