Below discloses what information OvenBreak: 3baked collects, stores, and uses. For inquiries, please contact ovenbreak3baked@gmail.com.

OvenBreak: 3baked uses Discord login to avoid obtaining sensitive information from the user. After logging in via Discord login, OvenBreak: 3baked gains access to the username and ID of the user's Discord account. the user's Discord profile picture is also obtained, but only visible on the login screen and is not stored or saved. The user's Discord ID is stored on the server for account management, and the user's Discord username is visible to other users while in-game.

Since OvenBreak: 3baked does not have access to the user's Discord friends list, users must make friends manually using our bot, OvenBreak: 3baked Social. When the "friendme" command is used, our bot obtains both Discord user IDs of who sent the command initially, and who interacted with the command. Then, the database is updated to connect both users together.

Additionally, OvenBreak: 3baked Social has a tournament system, where users can add our bot to his/her Discord server and host a tournament. To assist with this, the bot will create a list of all members within the Discord server the command is used in, and store it on OvenBreak: 3baked's server for the duration of the tournament. This list may be visible to any player, but is only used to detect if a user is in a Discord server a tournament is being hosted in. After the tournament ends, this information is deleted from the server.

Finally, In order to log into OvenBreak: 3baked, users authorize via our bot, and are given a code he/she can use to log in. Once this code is entered in OvenBreak: 3baked's login screen, the user will be granted access. After authorizing, Discord information such as identifying user data (username, ID, etc.), refresh tokens, etc. are stored on OvenBreak: 3baked's server for when the login code is entered. This data is stored privately, and can only be viewed by the server. After a code is entered, the server checks if the code has any valid data, and if so, it is given to the user. After a login code is used, all data associated with it is deleted from the server, and the user now has access to the account. For extra security, login codes are deleted after 100 seconds of inactivity.

Last updated Feb 23, 2026.