-
Notifications
You must be signed in to change notification settings - Fork 2
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
Provide an easy way to close your account and delete all your data #132
Comments
This all sounds good to me as a first step! I think the issue I have is related to the
I think there's arguments on boths sides, and I've certainly come across people getting upset with Bandcamp because some of their purchased music has disappeared. I appreciate it's some extra work but I wonder if an option here is to add something to the "are you really sure" step that gives the option to the artist to allow their listeners to keep the music? Perhaps, if we wanted to make sure all the data was eventually destroyed, we could send an email to anyone who has purchased giving them a grace period to download the files? Otherwise, I think baking in the ability to delete your data from the beginning is the right thing to do and it'll make it easier for us to make sure we always allow data to be deleted. |
We should also look at using Postmark's Data Removal API to remove the relevant data from Postmark. |
An artist contacted me directly today to ask for their account/music to be deleted. They had no purchases so we didn't have the issue discussed above, but it's a useful indication that this feature would be useful. |
I've spun this out of #119 with the idea of doing something very basic. I'm imagining doing something like the following:
@chrislo:
User#artists
is not marked asdependent: :destroy
andArtist#user
is marked asoptional: true
. Was this intentional? Should we offer the option to leave the artists, etc in place? It doesn't seem to make much sense to me.UsersController#delete
&UsersController#destroy
, but then I noticed the controllers in theIdentity
namespace. Would it make sense to have something like anIdentity#DeletionsController
...?The text was updated successfully, but these errors were encountered: