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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discord will not delete your chat messages #54

Open
cloudrac3r opened this issue Jan 30, 2021 · 7 comments · May be fixed by #97
Open

Discord will not delete your chat messages #54

cloudrac3r opened this issue Jan 30, 2021 · 7 comments · May be fixed by #97
Assignees
Labels
product Related to a product on PrivacySpy

Comments

@cloudrac3r
Copy link

Messages you send are extremely personal information, but on Discord they will not be deleted when you delete your account. Every message you have sent will remain, though will be "anonymised" by changing the display name on the message to "Deleted User [Identifier]".

There is no way to mass delete your messages at all.

I don't think this is good enough for a 100% rating in this category. I'm not sure how I should edit the information on the page to reflect that.

[rubric.data-deletion]

@privacyspy-bot
Copy link

Thanks for submitting this issue. @milesmcc has been assigned to determine next steps.

To learn about the PrivacySpy contribution process, check out the contribution guide.

@milesmcc
Copy link
Collaborator

Hmm, this is tough. It's unclear whether this is a violation of the current selection ("yes, using an automated mechanism") or not. We could change this to no, but then we'd have to reckon with whether we'd need to change Wikipedia's scores as well (after all, there's no way to 'delete' a user's edits). @ibarakaiev what do you think?

@cloudrac3r
Copy link
Author

That's a fair point. I think on discord it's more of a problem than on wikipedia since direct messages you send to your friends are likely to be much more personal than factual edits on wikipedia about some specific topic.

@ibarakaiev
Copy link
Collaborator

ibarakaiev commented Jan 31, 2021

@milesmcc I'd say we should stick with the current selection for Discord, because messages are user-generated content that is shared with many other users (not just with Discord as a company). Perhaps we should modify the rubric to say that data deletion only applies to personally identifiable data?

@cloudrac3r
Copy link
Author

Depending on what the person used discord for, there's every chance that their messages contain personally identifiable data.

@QuickWrite
Copy link

The problem is that you can still access files even if the message has been deleted.
This can be done simply via a link. These files are also not protected, which means that anyone can access them if he has the link (which is very unlikely, because you have to do this via bruteforce and this would take an immensely long time).

Everything that is sent to Discord stays on Discord and people who may have accidentally sent the wrong thing will have a hard time getting rid of it (you'll probably have to write to Discord themselves).

@Deivedux
Copy link
Contributor

Deivedux commented May 28, 2021

Calling Discord messages as "extremely private" is a bit of an exaggeration, in my opinion. Given that Discord's primary message storage are from community servers, the fact that every content hosted on a CDN is easily accessible via a URL, and that the messages themselves are never encrypted suggests that your messages on Discord were never private to begin with, which makes it rather easy to argue that the said data cannot be anything more than just "user-generated content", and whether users want to use this method of content generation for actual private communication is entirely up to them, not to the platform.

@milesmcc milesmcc added the product Related to a product on PrivacySpy label Jun 15, 2021
@ibarakaiev ibarakaiev linked a pull request Jun 16, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
product Related to a product on PrivacySpy
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants