Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Right to be Forgotten #3315

Closed
andreslucena opened this issue May 2, 2018 · 3 comments
Closed

Right to be Forgotten #3315

andreslucena opened this issue May 2, 2018 · 3 comments

Comments

@andreslucena
Copy link
Member

@andreslucena andreslucena commented May 2, 2018

This is a Feature Proposal

  • This issue is part of the GDPR EPIC #3320

馃帺 Description

This is a feature proposal to have a better compliance with GDPR (General Data Protection Regulation).

We need to track every deleted user id, so if we have to restore the database there is a procedure where an admin check that this users don鈥檛 get recreated.

@tramuntanal
Copy link
Contributor

@tramuntanal tramuntanal commented May 2, 2018

@decidim/product how do you think to implement this?

  • how and where do we track these user_ids?
@MarcReniu
Copy link
Contributor

@MarcReniu MarcReniu commented May 8, 2018

How are the backups stored?

I'm thinking in a rake task to restore the backups, and then an auxiliar/temporal file with user_ids, only to search and destroy them. As a first aproach.

@MarcReniu MarcReniu mentioned this issue May 24, 2018
2 of 5 tasks complete
@isaacmg410
Copy link
Contributor

@isaacmg410 isaacmg410 commented May 28, 2018

We close this issue, because PR is merged

@isaacmg410 isaacmg410 closed this May 28, 2018
@Xfolchf Xfolchf added this to the Release v.0.13.0 milestone May 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants