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.
Please note that data marked with blurple text below is not automatically removed. We need to hold onto this information in order to maintain infraction records and ensure the smooth running of our community.
We do not store any data until you have verified yourself in
#checkpoint on the server,
like us to remove this data as well, please contact a member of staff directly.
|What we collect||When it's collected||What it's used for||Who can access it|
|Discord user ID||!accept run on Discord||Statistics, data association (infractions, code jam applications, etc)||Administrative staff|
|Discord username and discriminator||!accept run on Discord||Display purposes (alongside ID in staff areas, public profiles)||Public (for code jam team listings and winner info) and staff areas|
|Discord avatar URLs||!accept run on Discord||Display purposes (alongside ID in staff areas, public profiles)||Public (for code jam team listings and winner info) and staff areas|
|Assigned roles on Discord||!accept run on Discord||Access control for the site, infractions, role restoration after kicks||Administrative staff|
|Messages sent on Discord||!accept run on Discord||Stored in memory by the bot for processing temporarily, may also end up in staff-only logging channels for the purposes of accountability and infraction management||Administrative staff|
|OAuth access and refresh token||Discord login on site||Used to find your Discord user ID when you log in||Administrative staff|
|GitLab username||Code jam profile||Used to identify you on GitLab 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|
|System Information||Code jam signup||Used to verify that you have a working environment||Administrative staff|
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
detailed in a message in that channel.
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.
Please note that data marked with blurple text in the table above is not automatically removed. We need to hold onto this information in order to maintain infraction records and ensure the smooth running of our community. If you are leaving the server and would like us to remove this data as well, please contact a member of staff directly.
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.
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 any member of the administrative staff directly.
We believe that the best way to keep your personal data safe is to avoid collecting it at all. Discord itself is GDPR-compliant and they've already done the legwork required to ensure that your data may be collected - so we don't see the need to collect your personal information ourselves. Don't forget that by using Discord, you are stating that you are of legal age in your country to give consent to process your data!
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.
July 27th, 2018
As we're replacing Rowboat (the bot we use for moderation), we need to hold onto some of your data - even after you've left the server. This is necessary to ensure the smooth running and security of our community.
July 3rd, 2018
While we don't collect your email addresses, they are visible on GitLab if you email an issue directly to our
[email protected]email address, but only to staff.
June 7th, 2018
We no longer collect GitHub usernames - instead, we collect GitLab usernames. Additionally, we now collect user avatar URLs for display purposes.
June 5th, 2018
May 31st, 2018
We no longer collect your date of birth, and all collected dates of birth have been removed from our database. The reason for this is that Discord itself already complies with GDPR - and in order for you to sign up for a code jam, you must already have a Discord account.
May 20th, 2018