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.

If you have any concerns relating to information and privacy in this community, you can contact the Python Discord data controller via Discord at joseph#1337 or through email as [email protected].

We perform monthly reviews of our data to decide whether data we are storing still has value and is required for the operation of the community. Previous reviews can be found on the data reviews page.

NOTE: Upon logging in with Discord, Discord will warn you that your email will be shared with Python Discord. We do not store any emails which are collected through OAuth2 authorization and we have an open issue to remove the email scope from Discord authorization.

Data collection

Discord user ID When you join the community Statistics, infractions Administrative staff
Discord username, discriminator and avatar hash When you join the community, and when it changes Display purposes (alongside ID in staff areas, public profiles) Administrative staff
Assigned roles on Discord Whenever your roles are updated. Access control for the site, infractions, role restoration after kicks Administrative staff
Messages sent on Discord When you send a message. 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
Anonymous statistics Events received from Discord (joins, leaves, messages) We calculate some statistics based on the events which Discord sends us. This helps us monitor the performance of a community and have stats to back community decisions. We have a list of anonymous statistics which provides more information on what we collect. Core developers, occasionally public for some statistics though always completely anonymised
Messages deleted by the auto-moderation system Upon a trigger of the spam prevention system, we delete messages and store a copy This data is used to allow staff to understand what happened in a situation and deal with it in an appropriate way. The data is kept in the database for as long as it is required to perform moderative actions and is deleted, typically at the monthly data review. Moderation staff


April 13th, 2020
Add link to statistics page.

April 12th, 2020
Add information about statistic collection. Add information about contacting the data controller. Add link to the data reviews page. Add information about auto-mod message retention.

Aug 7th, 2019
We no longer automatically remove any data if you leave the community, and we no longer store the avatar URL for any reason.

May 20th, 2019
We're no longer tracking anything related to Code Jams. Our data collection is now strictly limited to data available through your Discord user. Because we believe it now falls to Discord to ensure they have your consent for collecting this data, we no longer collect explicit consent.

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
Rectified an omission in the old privacy policy, where the system information you provide as part of a code jam signup wasn't mentioned.

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
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.