Datasets:
GDPR 2
Hello, - EDIT
Thank you for the quick response and for deleting the file from the current version of the dataset. I appreciate your prompt action.
However, I noticed that the file containing the usernames and email addresses is still fully accessible in the repository's commit history. To fully comply with the GDPR right to erasure, the data must be permanently removed from the version history as well.
Could you please purge the commit history to completely wipe the previous versions of this file?
Please let me know once the commit history has been cleared. Thank you again for your continued help with this!
Best regards,
Prime
Hello,
I am writing to confirm that the erasure process is now complete.
On Hugging Face, the repository's commit history has been fully purged. The dataset now contains a single empty commit, and no previous versions are accessible.
Additionally, I want to inform you that the same dataset was also published on Kaggle.com, a platform you may not have been aware of. I have taken the same corrective action there: the files containing personal data have been replaced by empty data and access to previous versions has been permanently restricted.
To summarize, your information (and everyone else's) has been removed from all locations where it was stored:
- Hugging Face: full commit history purged
- Kaggle: previous versions restricted and files replaced
I sincerely apologize for any inconvenience this situation may have caused. I have taken steps to ensure this does not happen again in future versions of the dataset.
Close the issue when you think everything is correct.
Best regards
Hello,
Thank you for the thorough follow-up and for taking the proactive step of removing the data from Kaggle as well. I appreciate your diligence in getting the commit histories fully purged on both platforms, and I am glad to hear that you removed everyone else's information from this dataset alongside mine.
I will be taking a look around to ensure there are no other lingering GDPR issues or instances of my data floating around.
As a piece of advice going forward, I highly recommend that you audit your other projects and remove the personal data of any other individuals from anywhere else it might be published without their consent. I noticed that this dataset was downloaded 5,129 times last month alone. Because of this, my data—and everyone else's—is essentially out in the wild, and you remain responsible for that initial unauthorized distribution.
This highlights exactly why it is so critical to verify that you have the proper rights and explicit opt-in before publishing datasets containing personally identifiable information (PII). Ensuring strict GDPR compliance prior to publication will prevent irreversible situations like this from happening in the future.
Everything looks correct on my end regarding this repository, so I will go ahead and close this issue. Thank you again for your cooperation.
Note: If I stumble on any problems in the future I will let you know.
Best regards,
Prime