[wp-meta] [Making WordPress.org] #3244: Data Protection and Bank Detail issues

Making WordPress.org noreply at wordpress.org
Tue Nov 7 18:00:39 UTC 2017

#3244: Data Protection and Bank Detail issues
 Reporter:  Hugo Finley                 |       Owner:
     Type:  defect                      |      Status:  new
 Priority:  normal                      |   Milestone:
Component:  WordCamp Site & Plugins     |  Resolution:
 Keywords:  needs-patch good-first-bug  |

Comment (by andreamiddleton):

 Replying to [comment:6 TJNowell]:
 > Having thought about it further, as soon as the status is set to PAID
 the personal information should be immediately redacted or removed, a cron
 job shouldn't be necessary. This should simplify the technical side of

 We originally thought to keep the info for 14 days because sometimes after
 the bank tells us money has been sent, they come back and tell us that the
 money has not been sent, and we need to review what payment details were
 used to send the funds. That said, we can usually get that information
 from the bank (banking software can be really buggy, which is where the
 "usually" comes from). So if it's going to cause an issue with GDPR, then
 we could probably wipe banking info immediately after the request is
 marked Paid and research issues based on what the bank tells us.

Ticket URL: <https://meta.trac.wordpress.org/ticket/3244#comment:7>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list