This policy informs you of what data the Wilbur Soot Discord organization ['us', 'our', 'we'] store on you as a member ['you', 'your', 'user'] of the Wilbur Soot Discord ['server', 'guild', 'community']. Our priority as moderators and administrators is the safety of the community, and we believe that privacy is paramount. This document sets out what data we store, why we need to store this data, who has access to it, and how we process and use it. If you have any questions, please contact the Data Controller at [email protected] or Josh_#5356
This document was last updated on 02/01/2022.
Firstly, please note that information for members who have left the server is cleared on the first day of each month, unless your account has an infraction (a 'ban' or 'mute').
We collect message contents and user IDs when our anti-spam and word filter systems are triggered, or a message has been edited or deleted. These are also cleared as part of the aforementioned monthly data reviews if you have left the server.
The content of messages is not stored outside the guild unless a service requires it to function correctly. We try to keep this to a minimum to ensure the safety of the community, and exemptions are detailed below.
When a user is given an infraction - a ban or a mute - this is logged to their account. This data persists even if you leave the server, as it is required to ensure a safe community.
We also store a variety of anonymous statistics, such as the amount of messages sent or deleted.
We do not knowingly store the data of users that are under the age of 13. On becoming aware of a user who is under the age of 13, we forward the information to Discord's Trust and Safety team who take appropriate action on the user. We delete all data upon becoming aware of a user under 13.
We do not store message contents externally (using a service that isn't Discord) unless required for moderation. If we have the need to store message data for any reason, this is removed from our servers once we have finished with it, often for analysis purposes.
To ensure the privacy and safety of our members, we take a variety of steps to handle the data carefully. This includes only 4 people having direct access to our systems - the development team - and this is regularly audited, along with taking all appropriate steps to ensure security.
Infraction data - bans and mutes - is accessible to moderators and administrators, and this is also regularly audited.
All data we store is needed to ensure the safety of the guild, and to help us create a happy and welcoming community. As a staff team committed to openness and transparency, our aim is to be as open as possible on what data we store and why. This document is part of this aim, as well as our regular data audits.
There is an entry for every service we run on our servers which stores user data, and some third party services which have access to some user data. Note that this does not cover any data we store using Discord, for example in our moderation logging channels.
Sootbot#7677 - stores data for moderation purposes. All user nicknames, user IDs and usernames are stored, as well as infraction reasons and messages that have been logged by our filters. Sootbot stores these in logging channels only accessible by a small number of people with regular security and access audits. When using our appeal site Sootbot will also (if authorized) have access to your username and email via Discord for purposes of ensuring fake appeals are not submitted and for contacting you when your appeal is accepted or rejected.Zeppelin#3008 — similar to our main moderation bot, also stores data for moderation purposes. This bot will be used while our main moderation bot is built by our developers. This bot allows server staff to carry out moderator functions such as mute, kick, ban, view user information, keep records of infractions, and post detailed logs in our logging channels. All user nicknames, user IDs and usernames are stored, as well as infraction reasons and messages that have been logged by out filters. Zeppelin stores these in logging channels only accessible by a small number of people with regular security and access audits. You can find Zeppelin's Privacy Policy here.