Last updated: 23rd May 2021
This document details what data the Python Discord organisation store on you as a member of the Python Discord community. Privacy and security of member data is one of our top priorities while managing Python Discord. This document sets out what data we store, why we need this data, who has access to this data, and how we process it. Please see the terminology section to better understand this document.
This document is inspired by the GitHub Privacy Statement.
We may collect message contents tied to user accounts when a user has triggered our anti-spam system.
No message content is stored outside the guild unless a service explicitly requires it, this is detailed below in the services section.
When a user breaches our rules or the code of conduct in our guild we tie an infraction record to their account. This data is persisted across leaving the guild and is essential to processing.
We do not knowingly store the data of users under 13. On becoming aware of a user who is below the age of 13 we forward this information on to Discord who take action on the user as they find appropriate. Once this user has been deleted from Discord we remove data we hold on them.
We do not store message contents unless they are required for moderation, examples of this are the anti-spam filters.
We take numerous steps to ensure data is handled carefully in the community. Direct database access is only available a subset of the DevOps team.
Infraction data is only accessible to Moderators and Administrators and access to this information is audited.
We ensure that all data we store is critical to operation and do not store more than is needed. We aim to be as transparent as possible on what data we store and for what purpose.
Below is service specific information of what data we hold. There is an entry for at least every service we run on our servers which stores user data, and some third party services which have access to some user data.