ngoc24794 · May 26, 2025 07:25
diff --git a/gistfile1.txt b/gistfile1.txt
 Terms of Service for Jenkins Discord Bot
 1. Introduction
 This Terms of Service Agreement ("Agreement") governs your use of the Jenkins Discord Bot ("Bot"), which integrates with Discord to provide notifications and updates from a Jenkins server. By using the Bot, you ("User") agree to be bound by these terms and Discord’s Terms of Service (available at https://discord.com/terms).[](https://discord.com/terms)
 2. Purpose of the Bot
 The Jenkins Discord Bot is designed to send notifications to Discord channels about Jenkins build statuses, such as success, failure, or other pipeline events, using Discord webhooks. The Bot is provided "as is" without warranties of any kind.
 3. User Responsibilities

 Compliance with Discord Policies: Users must comply with Discord’s Terms of Service and Developer Terms of Service when interacting with the Bot.
 Proper Configuration: Users are responsible for correctly configuring the Bot’s webhooks and ensuring the Jenkins server has appropriate permissions to send messages to the designated Discord channel.
 Non-Abuse: Users must not attempt to misuse, reverse-engineer, or exploit the Bot for unauthorized purposes, including sending spam or malicious content.

 4. Bot Owner Responsibilities

 Operation: The Bot Owner strives to maintain the Bot’s functionality but does not guarantee uninterrupted service or error-free operation.
 Data Handling: The Bot processes minimal data, such as Jenkins build statuses and Discord webhook URLs. The Bot Owner will not store or process personal data beyond what is necessary for the Bot’s functionality.
 Updates: The Bot Owner may update or modify the Bot without prior notice, which may affect functionality.

 5. Privacy
 The Bot does not collect or store personal information beyond what is required for sending notifications via Discord webhooks. Users are responsible for ensuring that any data shared through the Bot (e.g., build logs) complies with applicable privacy laws and does not contain sensitive information.
 6. Limitation of Liability
 The Bot Owner is not liable for any damages, direct or indirect, arising from the use or inability to use the Bot, including but not limited to service interruptions, data loss, or inaccuracies in notifications. The Bot is provided on an "as is" basis without warranties of any kind.
 7. Termination
 The Bot Owner reserves the right to suspend or terminate access to the Bot at any time, for any reason, including violation of this Agreement or Discord’s policies. Users may stop using the Bot at any time by removing it from their Discord server.
 8. Modifications to Terms
 The Bot Owner may update this Agreement at any time. Continued use of the Bot after changes constitutes acceptance of the updated terms.
 9. Contact
 For questions or support regarding the Bot, contact [insert contact information, e.g., email or Discord handle].
 10. Governing Law
 This Agreement is governed by the laws of [insert jurisdiction, e.g., the state or country of the Bot Owner’s residence], without regard to conflict of law principles.

 Last Updated: May 26, 2025
	Terms of Service for Jenkins Discord Bot
	1. Introduction
	This Terms of Service Agreement ("Agreement") governs your use of the Jenkins Discord Bot ("Bot"), which integrates with Discord to provide notifications and updates from a Jenkins server. By using the Bot, you ("User") agree to be bound by these terms and Discord’s Terms of Service (available at https://discord.com/terms).[](https://discord.com/terms)
	2. Purpose of the Bot
	The Jenkins Discord Bot is designed to send notifications to Discord channels about Jenkins build statuses, such as success, failure, or other pipeline events, using Discord webhooks. The Bot is provided "as is" without warranties of any kind.
	3. User Responsibilities

	Compliance with Discord Policies: Users must comply with Discord’s Terms of Service and Developer Terms of Service when interacting with the Bot.
	Proper Configuration: Users are responsible for correctly configuring the Bot’s webhooks and ensuring the Jenkins server has appropriate permissions to send messages to the designated Discord channel.
	Non-Abuse: Users must not attempt to misuse, reverse-engineer, or exploit the Bot for unauthorized purposes, including sending spam or malicious content.

	4. Bot Owner Responsibilities

	Operation: The Bot Owner strives to maintain the Bot’s functionality but does not guarantee uninterrupted service or error-free operation.
	Data Handling: The Bot processes minimal data, such as Jenkins build statuses and Discord webhook URLs. The Bot Owner will not store or process personal data beyond what is necessary for the Bot’s functionality.
	Updates: The Bot Owner may update or modify the Bot without prior notice, which may affect functionality.

	5. Privacy
	The Bot does not collect or store personal information beyond what is required for sending notifications via Discord webhooks. Users are responsible for ensuring that any data shared through the Bot (e.g., build logs) complies with applicable privacy laws and does not contain sensitive information.
	6. Limitation of Liability
	The Bot Owner is not liable for any damages, direct or indirect, arising from the use or inability to use the Bot, including but not limited to service interruptions, data loss, or inaccuracies in notifications. The Bot is provided on an "as is" basis without warranties of any kind.
	7. Termination
	The Bot Owner reserves the right to suspend or terminate access to the Bot at any time, for any reason, including violation of this Agreement or Discord’s policies. Users may stop using the Bot at any time by removing it from their Discord server.
	8. Modifications to Terms
	The Bot Owner may update this Agreement at any time. Continued use of the Bot after changes constitutes acceptance of the updated terms.
	9. Contact
	For questions or support regarding the Bot, contact [insert contact information, e.g., email or Discord handle].
	10. Governing Law
	This Agreement is governed by the laws of [insert jurisdiction, e.g., the state or country of the Bot Owner’s residence], without regard to conflict of law principles.

	Last Updated: May 26, 2025
No results found