Boy, thank god for the safety act: Discord customer service data breach leaks user info and scanned photo IDs

by Saedraverse

7 comments

  1. At least we’re safer with it in place.

    Step 1) Verify yourself by uploading personal info to a company that is at risk of having a massive data leak.
    Step 2) ????
    Step 3) We’re all safer on the internet.

  2. Seems only a small number of people who specifically appealed an age verification are the ones who have been affected by the breach.

    Regardless, even if it was only one person it would have been too many. Sending sensitive personal ID information to a third party on the internet a good idea? Hahaha

  3. You mean that thing that we all warned was going to happen happened? I’m shocked I tell you, shocked!

    ![gif](giphy|6nWhy3ulBL7GSCvKw6)

  4. Just change your country on a VPN and press CTRL+R when connected. I will never put ID on any of this shit.

  6. We’ll doxx as many people as it takes if it means ~~we get more control~~ protecting even 1 child! – current labour

  7. Lot of misinformation flying around about this implying that it’s their entire age verification system (Which is a 3rd party and does not store data, and no I don’t care what unproven conspiracies fly around about this). What was actually hacked was the support Zendesk for Discord, so the hackers dumped all of the tickets and customer details of people who had logged support tickets.

    If you’ve submitted a ticket before, your email, name, IP and the ticket content was included (As well as some limited payment data like last 4 digits etc).

    The only way this affects the age verification thing is that it looks like a small number of users who (maybe had issues with automated verification) sent scans of their ID in to support to be manually verified.

    The overarching point in all of this is that you should not be emailing scans of your IDs random companies as they *will* be stored in systems like this if you do so.

    I had an email as I had an old ticket and it explained what was leaked and gave me the ticket number so I could check myself what had actually been taken.

Comments are closed.