Dot's commands involve processing information from the CalRef database or third-party APIs. Third-party API data is only retained for the duration of the command's processing. Some information is stored regarding the operator and their servers for the command of function working successfully. This includes referencing account IDs or server IDs as a means of storing preference settings. 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, such as in Dot's economy, behave in the same way.
Similarly, information about a server is stored whenever a server admin sets preferences with Dot's administrative aid commands. This includes applicable server IDs, channel IDs, and operator-set images and greetings for servers with active eyebeast commands, welcomes and farewells, autoroles and react roles, and other commands that cannot function without such data.
Meta-data is collected regarding Dot's operation, consisting of command usage frequency, total server 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 anticipating hardware needs based on growth and usage trends. No information about individual operators is personally identifying, and message content is only stored when input by the operator via preference-setting commands.
Many commands have built-in options for input data to be wiped. If this is insufficient or an operator otherwise wishes to have their command preferences and/or economy data deleted from existence, they may contact me on Discord (Luca#0004) from the account whose data they wish removed.
Certain usage information is posted to the console when Dot is in operation. This includes whether or not 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 command or 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 server in which the malfunction occurred, and are cleared regularly.
If you have any questions or concerns relating to Dot, you can email me directly at email@example.com
Powered by CalRef