Privacy
We take every step to ensure that your data is used ethically and that includes making sure that you know exactly what data we collect, and what we do with it. That means that instead of a bunch of legalese, we've provided this information in an easy, human-readable form below.
Please note that we are a completely non-profit community. We have no interest in selling your data, or shipping it off to third parties. Our community is entirely volunteer-run - it does not have any form of monetary income whatsoever - and we believe that this is how it should be.
Data collection
What we collect | When | What it's used for | Who can access it |
---|---|---|---|
Discord user ID | self.accept() run on Discord | Statistics, data association (infractions, code jam applications, etc) | Administrative staff |
Discord username and discriminator | self.accept() run on Discord | Display purposes (alongside ID in staff areas, public profiles) | Public, for code jam team listings and winner info |
Assigned roles on Discord | self.accept() run on Discord | Access control for the site | Administrative staff |
Messages sent on Discord | self.accept() run on Discord | Stored in memory by the bot for processing temporarily, no message content reaches the database unless you're using a bot command that interfaces with the site - May be temporarily written to a log file for debugging purposes | N/A |
OAuth access and refresh token | Discord login on site | Used to find your Discord user ID when you log in | Administrative staff |
Date of birth | Code jam profile | Age verification and a factor in code jam team match-ups; only stored if you're over 13 | Administrative staff |
GitHub username | Code jam profile | Used to identify you on GitHub as part of a code jam team | Public, for code jam team listings |
Timezone | Code jam profile | A factor in code jam team match-ups | Administrative staff |
Collecting consent
If you joined the community on or before the 20th of May, 2018, you will have seen an announcement about our privacy policy on the Discord server. You will have had the opportunity to leave the server if you weren't happy with it. If you decided to stay, then we will consider you to have accepted our use of your data, as detailed on this page.
If you joined the community after the 20th of May, 2018, you will have been greeted with the
#checkpoint
channel. In this channel, you must run the self.accept()
command to signify that you accept both our rules and this privacy policy. This will also have been
detailed in a message in that channel.
Please note that your acceptance of this privacy policy is retroactive, and you agree that any revisions to it will apply when they are published. We will attempt to keep everyone updated on changes to this policy via the usual announcement channels - if at any point you are not happy with a change to the privacy policy, please bring it up with a member of staff. If we're unable to solve your issue in a satisfactory way, you may remove your data as detailed below.
Data removal
If you'd like to remove your data from our servers, there are two options available to you.
Complete data removal
If you'd like to remove all of your personal data from our servers, all you need to do is leave the Discord server. As much of the data we collect is necessary for running our community, we are unable to offer you community membership with zero data collection.
Once you've left the Discord server, your data is removed automatically. Please note that for the sake of data integrity and moderation purposes, we do not remove your Discord user ID from our database - but we do anonymize your data as far as possible.
As with deleting your code jam profile directly, you will be issued an automatic ban from future code jams if you have applied for or are currently taking part in a code jam.
Code jam profile removal
If you've provided us with a code jam profile in the past and would like to remove it, you may do so by heading to the "My Profile" page, where you will find a button that will remove your profile.
Please note that this is a nuclear option. If you have applied for or are currently taking part in a code jam, this will void your application and you will receive an automatic ban from future code jams until you've contacted us about it.
GDPR compliance
Under the terms specified above, we do aim to comply with GDPR. While we do not currently have
an automated way for users to export the data they've provided to us, we're happy to do this
manually or answer any other GDPR- or privacy-related queries you may have. Feel free to contact
our GDPR officer on Discord (gdude#2002
), or any other member of the administrative
staff.
We are currently working on an automated way to get all of your data in both a human-readable and machine-readable format. Keep your eye on the usual announcements channels for more information on that, as it happens.
Changelog
-
May 20th, 2018
Completed the first version of our privacy policy. We also updated our OAuth scopes for Discord logins - we no longer collect your email, or get the access to join you to servers automatically. All collected emails have also been removed from the database.