PeriodicDex is run on a self-hosted installed version of the Ballsdex code. The Ballsdex code is released under the MIT Licence. More info at this link.
PeriodicDex requires access to certain data to function, including the following:
User IDs
Used to identify whose substances belong to whom in the database
Server IDs
Information integral to how the bot runs is tied to server data, including where substances are caught, to prevent possible farming
Channel IDs
Required to ensure substances spawn in the right channel as configured on bot installation
Message Content
Needed to prevent possible farming by abusing the internals of the bot. Message content is NEVER saved or logged. Only the bot owner has access to any data stored by the bot, see below
PeriodicDex itself also collects the following to ensure the bot runs smoothly:
Trade history, which includes gifting substances to other players, as well as a log of all players who have owned a substance at any given time
A list of all substances currently owned by a player
Any customizations the player elects through the bot that could change how certain commands function. These are tied to User IDÂ
All important information is stored privately on the owner's servers, connected to a secure, private network and encrypted separately. These run locally and have no point of access outside the encrypted private network. Backups are made daily to prevent major data loss.
Only the owner has access to the bot data, and only the owner can access the secured admin interface which controls key interworkings of the bot. Moderators, server admins, and the like cannot access this information.
If you have questions about your data or would like your data to be removed from the bot, the best way of doing this is to email haapsalu25@icloud.com, especially if the request is larger. There is also a built-in command to remove data, but emailing (or also DMing Haapsalu at the discord "haap_") can make sure everything is cleaned up with.