In this overview, Calamity Refuge is an entity located in British Columbia, and legally owned by the Arch-Administrator, the lead developer. A "user" is an individual with a Discord account. A "guild" is a Discord chat server. A "member" is a user within a contextual guild. An "operator" is a user that is contextually operating Dot's commands and functions within or outside of a guild.
Dot is a Discord bot, provided and developed by Calamity Refuge. As a service thereof, Dot is subject to Calamity Refuge's Code of Conduct. Dot's operation and administration abides by those guidelines and extends them to its operation such that:
Calamity Refuge will retract Dot from guilds which operate in contradiction to these guidelines, and bar operators from the ability to use Dot's commands and functions. Operators who wish to report violations to these guidelines my do so via the report command, or contact any member of the Calamity Refuge staff.
This software is provided as-is, with no warranties of any kind expressed or implied. In no event shall Calamity Refuge or its staff be held liable for claim, infringement, or damage of any kind arising from the use of this software which occurs within the stipulated guidelines of its Code of Conduct. Should any degree of which be illegal or unenforceable, the remainder of the text shall continue to apply.
Dot's commands often involve processing information from the Calamity Refuge database or third-party APIs. Third-party API data is only retained for the duration of the command's processing. Information stored in command settings and preferences is saved by the operator's discord ID and/or their guild's ID for the duration the settings are needed. The reminders that are pending or the operator's nation of reference in the timer command, for example, rely on these IDs to work. Other commands that include the operator's settings or progress behave in the same way.
Similarly, information about a guild is stored whenever a guild's admin sets preferences with Dot's administrative aid commands, and retained for the duration the settings are necessary for their function. This includes applicable guild IDs, channel IDs, and operator-set images and greetings for servers with active eyebeast commands, welcomes, farewells, autoroles, react roles, and other commands that cannot function without such data, such as recruit, where telegram templates and active sessions are differentiated by channel ID.
Meta-data is collected regarding Dot's operation, consisting of command usage frequency, total guild count, and the total volume of operators served. This data helps determine the types of commands that are desired for future development, whether Dot's commands are being maliciously spammed or misused, as well as anticipating hardware needs based on growth and usage trends. No information about individual operators is personally identifying, and message is only stored when it is an argument of an intentionally invoked command.
Many commands have built-in options for input data and settings to be wiped. If this is insufficient or an operator wishes to have any data deleted from existence where an operator cannot adequately locate these settings, they may contact Luca#0004 on Discord from the account whose data they wish to have removed.
Certain usage information is posted to the console when Dot is in operation. This includes whether assisted recruitment functions or timers are active, so as to establish flags which prevent the system from being restarted when doing so would be disruptive. Information regarding service malfunctions are service malfunctions are posted to the console and recorded in an error log. The error logs do not record any information about the operator or the guild in which the malfunction occurred, and are regularly cleared during bugfix development cycles.
If you have any questions or concerns relating to Dot, you can email me directly at firstname.lastname@example.org use the report command, or visit our server at https://calref.ca/chat.