By continuing to use this website, you agree to the collection of the data listed above. If you would not like any or all of this data to be collected, you may either disable cookies in your browser altogether, block the cookies from specific service(s) listed above, or clear your cookies and stop using this website. Note: If you disable or block cookies, this website may not work correctly.
Terms of Service
The following applies to usage of the Bender Discord bot: (referred to as "Bender")
Also, "server" refers to a Discord guild and "server staff" refers to a guild's owner, administrators, and/or moderators.
- Bender's developers are not responsible for user content uploaded or distributed via Bender.
- If you see any content stored or distributed via Bender that is illegal or against Discord's TOS, report it to staff of the support server and report the user(s)/server(s) to Discord directly.
- Intentionally exploiting issues in Bender, such as DoS (denial of service) attacks, are not permitted for any reason except helping the developers fix said exploits.
- Misuse of Bender, as defined in these terms, may result in you being blacklisted from using the bot and/or your content being deleted.
- Bender is provided as-is. Its uptime is not guaranteed and availability may be changed at any time.
- Premium features are not guaranteed as listed on this site; they may be changed or disabled if necessary, with a 30-day (or longer) prior notice being posted in the support server.
- Your permission to use Bender may be changed or revoked at any time if these terms are breached. Blocked users may or may not be notified depending on context.
Temporary data collection
Bender temporarily collects data including, but not limited to:
- Names and IDs of guilds it has been added to. This is stored in a temporary log file and is only accessible by Bender's developers.
- Error logs, which may include information about commands and arguments used (but no user or guild data.) This is also stored in a log file for developer use.
- Edited and deleted messages, which are kept in volatile memory for up to a day. These are accessible to different users depending on the permissions set by server staff.
Permanent data collection
Bender collects the following information permanently in a database:
All of this information can be deleted immediately at any time using the ;gdpr command. Use ;help gdpr in a DM to Bender to see all categories of user info that can be deleted.
If moderation logging is enabled in the server, the following is also collected in the database:
- Username and nickname history, used for the ;names command. You can opt-out of this collection using ;names disable in a DM to Bender.
- Reminders, which can only be seen by the user that created them
- After purchasing Bender Pro, data from PayPal is collected and used to validate subscriptions. This includes:
- Name and email, used only for displaying to the user to indicate which PayPal account is linked
- Unique PayPal ID, used to identify the user and link them to the subscription they purchased
- Transaction ID and timestamp, used to determine the length of the subscription
- Plan information, including the number of servers selected, length of the subscription, and amount paid.
These may also be collected, if enabled in the server, but are stored only in log channels and not in a database.
- Details about when and by whom users were muted, kicked, banned, etc. This does not include usernames or discriminators, only IDs.
- Since these features are customizable, you'll need to contact the staff of your server to know exactly what is being collected.
- Logs of deleted messages with contents, authors, and IDs, and timestamps
- Logs of edited messages with old and new contents, authors, and IDs, and timestamps
- Logs of commands used with message contents, authors, IDs, and timestamps
- Separate logs of moderation commands used, e.g. Moderator, user, reason and timestamp when using ;warn
By using Bender or joining a server containing Bender, you agree to be subject to data collection including, but not limited to, the above. Collecting this data is necessary for all features to function and/or for debugging. It is the responsibility of the server staff to inform you what optional data is collected, but if they do not, assume all optional data is collected.