-
Notifications
You must be signed in to change notification settings - Fork 0
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Automated flow for GDPR/CCPA deletion requests #7
Conversation
|
||
|
||
@router.delete("/api/v1/users/{user_id}") | ||
async def delete_user(user_id: int) -> Response: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To be invoked from RAP
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably with a ratelimit on admins, e.g. 3/hr or 10/d or something
"""\ | ||
An anonymization process for user deletion, mainly implemented | ||
for the purpose of complying with GDPR, CCPA and other regulations. | ||
""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are still quite a few open questions for "full compliance", but this is a pretty good start
dont clear hardware ids please (just set the associated user to 0 maybe or anonymize the actual user) |
I want to get this feature our ASAP & there are some other code changes required here to accomodate this desire, so I think we can treat this as p3/follow-up, so long as we're only really deleting unbanned users for the time being. We do have the follow note in our account deletion acceptance terms:
|
Tested locally, generally seems to be working as intended.