WordPress.org

Make WordPress Core

Opened 8 weeks ago

Last modified 6 weeks ago

#43921 assigned enhancement

Include community-events-location user meta value in Personal Data Export

Reported by: coreymckrill Owned by:
Milestone: Future Release Priority: normal
Severity: normal Version: trunk
Component: Privacy Keywords: gdpr has-patch 2nd-opinion
Focuses: Cc:

Description

Any user who visits the Dashboard screen will have a row in the usermeta table with location information, which is used by the WordPress Events and News widget to show relevant WP community events. The location information may include an IP address, location description, and/or lat/lon coordinates. This seems like personally identifiable information that should be included in a Personal Data Export.

Attachments (1)

43921.diff (2.0 KB) - added by coreymckrill 8 weeks ago.
Add community-events-location to exported data, update unit test

Download all attachments as: .zip

Change History (8)

#1 @coreymckrill
8 weeks ago

As noted here, the IP address is partially anonymized already, so it may not be completely necessary in the data export. However, if the user customizes the location in the widget UI, the database value will contain a location description (city name) and lat/lon, which is potentially much more specific than the IP.

@coreymckrill
8 weeks ago

Add community-events-location to exported data, update unit test

#2 @coreymckrill
8 weeks ago

  • Keywords has-patch 2nd-opinion added; needs-patch removed

In 43921.diff:

  • Add a case in the exporter function to grab the value of the community-events-location key for the given user and convert the array into a human-readable string.
  • Update the unit test for the data exporter function. It was already failing with an incorrect number of exported user properties. This adds the location data so that every possible piece of exportable data is included for the test.

Given that the comment exporter includes the Commenter IP value, I decided to go ahead and include it here along with the other possible location values, even though it's already partially anonymized.

The function that converts the exported user data into HTML doesn't handle values that are arrays, which is why this converts it to a string.

This ticket was mentioned in Slack in #gdpr-compliance by coreymckrill. View the logs.


8 weeks ago

This ticket was mentioned in Slack in #gdpr-compliance by coreymckrill. View the logs.


7 weeks ago

#5 @iandunn
6 weeks ago

  • Component changed from General to Administration
  • Milestone changed from Awaiting Review to 4.9.7
  • Status changed from new to assigned
  • Version set to trunk

#6 @desrosj
6 weeks ago

  • Milestone changed from 4.9.7 to Future Release

Moving gdpr tickets that are not bugs to Future Release until the next steps can be properly evaluated.

#7 @desrosj
6 weeks ago

  • Component changed from Administration to Privacy

Moving to the new Privacy component.

Note: See TracTickets for help on using tickets.