1. Introduction
These Terms of Service ("Terms," "Agreement," or "Terms of Service") govern access to and use of Obsidian Protocol ("Obsidian Protocol," "the Bot," "the Application," "the Service," "we," "us," or "our"), including all related Discord bot features, slash commands, moderation systems, ticket systems, automation systems, anonymous systems, logging systems, analytics systems, protocol systems, community tools, integrations, and other functions provided through the Application.
By adding Obsidian Protocol to a Discord server, authorizing the Application, configuring the Application, using any command, interacting with any button, menu, modal, panel, ticket system, confession system, vent system, moderation system, wheel system, or other feature, or remaining in a Discord server where Obsidian Protocol is active, you agree to be bound by these Terms.
If you do not agree to these Terms, you must not use Obsidian Protocol. If you are a server owner, administrator, or authorized representative and you do not agree to these Terms, you must remove Obsidian Protocol from your Discord server.
Important: This document is a formal template and should be reviewed by a qualified legal professional before publication if legal certainty is required.
2. Relationship to Discord
Obsidian Protocol operates on Discord and uses Discord's platform, APIs, gateway events, permissions system, interaction system, application commands, and related developer tools.
Obsidian Protocol is not Discord. Obsidian Protocol is not owned by Discord, operated by Discord, endorsed by Discord, certified by Discord, sponsored by Discord, or officially affiliated with Discord unless expressly stated otherwise in writing by Discord.
Your use of Discord remains governed by Discord's own Terms of Service, Privacy Policy, Community Guidelines, Developer Terms of Service, Developer Policy, and all other applicable Discord rules and policies.
By using Obsidian Protocol, you agree that you will comply with Discord's rules and that you will not use Obsidian Protocol to evade, bypass, or violate Discord's safety systems or platform requirements.
3. Eligibility and Acceptance
You may use Obsidian Protocol only if you are permitted to use Discord and only if your use complies with applicable law, Discord's rules, and these Terms.
You may not use Obsidian Protocol if you are prohibited from using Discord, if your account has been restricted in a manner that prevents such use, if you intend to use the Bot unlawfully, or if your use would violate these Terms.
You accept these Terms when you add Obsidian Protocol to a server, authorize the Application, use a command, interact with Bot components, submit content through a Bot feature, configure Bot settings, or continue using a server feature powered by Obsidian Protocol.
If you accept these Terms on behalf of a Discord server, team, organization, or community, you represent that you have authority to bind that server, team, organization, or community to these Terms.
4. Description of the Service
Obsidian Protocol is a modular Discord bot and server management framework. Depending on configuration and availability, it may provide features including moderation tools, administration tools, automated moderation, ticketing systems, anonymous confession systems, anonymous vent ticket systems, interactive panels and embeds, role management, staff management, welcome and goodbye systems, server diagnostics, statistics and analytics, invite tracking, starboard features, trust scoring, watchlist systems, utility tools, protocol systems, and integrations.
The availability of any feature may depend on server configuration, Bot permissions, Discord permissions, hosting status, Discord API availability, third-party API availability, or decisions made by the Bot operator.
5. Availability and Changes
Obsidian Protocol is provided on an "as available" basis. We do not guarantee that the Bot will be available at all times, uninterrupted, error-free, secure, or free from delays.
The Bot may become unavailable due to hosting outages, Discord API outages, third-party API outages, maintenance, updates, bugs, rate limits, permission changes, server misconfiguration, security incidents, database failures, removal or suspension by Discord, or decisions by the Bot operator.
We may modify, suspend, restrict, or discontinue any part of Obsidian Protocol at any time, with or without notice.
6. Server Owner and Administrator Responsibilities
Server owners and administrators are responsible for how Obsidian Protocol is used within their Discord servers.
- Configure Bot permissions carefully and appropriately.
- Inform users that Obsidian Protocol is active where appropriate.
- Ensure server rules accurately describe relevant Bot features.
- Limit sensitive Bot permissions and log access to trusted staff.
- Use moderation, logs, analytics, tickets, and anonymous features responsibly.
- Comply with Discord's Terms of Service, Community Guidelines, Developer Terms, Developer Policy, and applicable law.
- Not misrepresent Sentinel Watch as an IP address, geolocation, doxxing, or physical tracking tool.
- Not misrepresent anonymous confession or anonymous vent ticket systems as secretly identifiable.
Server owners and administrators are responsible for reviewing the Bot's requested permissions before authorization and for removing the Bot if they no longer agree with these Terms.
7. User Responsibilities
Users of Obsidian Protocol agree to use the Bot lawfully, follow Discord's rules, follow applicable server rules, avoid abusing or disrupting the Bot, and avoid submitting unlawful, harmful, threatening, abusive, harassing, hateful, exploitative, or malicious content.
Users must not submit passwords, authentication tokens, financial information, government identification numbers, private addresses, or unnecessary sensitive personal information through Bot features unless a specific legitimate support purpose requires it and the user understands the risk.
8. Acceptable Use
You may use Obsidian Protocol only for legitimate Discord community management, moderation, automation, support, engagement, and utility purposes.
- Managing moderation workflows.
- Creating ticket systems.
- Automating server rules.
- Organizing staff teams and role structures.
- Operating anonymous confession and anonymous vent systems.
- Improving server safety and community engagement.
- Maintaining logs for accountability and troubleshooting.
- Using wheel utilities and other integrations for community activities.
9. Prohibited Use
You may not use Obsidian Protocol to violate Discord's rules, violate applicable law, harass or threaten users, dox users, expose private information, distribute malware, conduct phishing, collect tokens, evade moderation, disrupt services, abuse anonymous systems, or attempt unauthorized access to Bot systems, databases, infrastructure, logs, source code, or credentials.
You may not use Obsidian Protocol to secretly identify anonymous users, create or demand secret transcripts revealing anonymous users, or misrepresent any Bot feature as capable of exposing information it is not designed to expose.
10. Sentinel Watch Terms
Sentinel Watch privacy commitment: Sentinel Watch is not an IP logger, geolocation tracker, doxxing tool, private location exposure system, or hidden surveillance mechanism.
Sentinel Watch does not provide moderators, administrators, server owners, server staff, or the Bot owner with access to user IP addresses.
Sentinel Watch does not provide moderators, administrators, server owners, server staff, or the Bot owner with access to user geolocation data.
By using Sentinel Watch, you agree not to describe it as an IP tracking tool, location tracking tool, address tracking tool, coordinate tracker, doxxing tool, or any similar system. Any server or user that misrepresents Sentinel Watch may be restricted or terminated from using Obsidian Protocol.
11. Anonymous Confessions and Anonymous Vent Tickets
Obsidian Protocol may provide anonymous confession features and anonymous vent ticket features. These features are intended to allow users to submit content without revealing their Discord identity through the Bot.
Anonymous feature commitment: Anonymous confessions and anonymous vent tickets are designed to be fully anonymous within Obsidian Protocol. The Bot does not create secret staff transcripts, secret Bot-owner transcripts, hidden identity records, or hidden logs that reveal the submitting user.
- Moderators cannot see who submitted an anonymous confession through Obsidian Protocol.
- Administrators cannot see who opened an anonymous vent ticket through Obsidian Protocol.
- Server owners and staff cannot see the anonymous submitter's identity through Obsidian Protocol.
- The Bot owner cannot see the anonymous submitter's identity through Obsidian Protocol.
- No secret transcript is created that identifies the anonymous submitter.
Anonymous status does not permit abuse. Users may not use anonymous features to submit threats, harassment, doxxing, illegal content, sexual content involving minors, malicious links, scams, impersonation, or content intended to harm other users or disrupt a server.
Anonymous vent tickets are not a substitute for professional help, emergency services, therapy, medical care, crisis counseling, or legal advice. If a user is in immediate danger or at risk of harming themselves or others, they should contact local emergency services or a qualified crisis support service immediately.
Anonymity may be affected by factors outside Obsidian Protocol's control, such as a user voluntarily revealing identifying details, other users recognizing details, screenshots, manual copying, Discord's independent data processing, or legal requests directed to third parties.
12. Stored Data and Records
Obsidian Protocol may save certain data as necessary to provide server management, moderation, automation, ticketing, analytics, utility, and configuration features.
Stored data may include, but is not limited to:
- Discord user IDs.
- Discord server IDs, channel IDs, role IDs, and message IDs.
- Moderation actions, including warnings, mutes, timeouts, kicks, bans, unbans, and related case records.
- Punishment information, including action type, reason, timestamp, duration, responsible moderator, and affected user ID.
- Moderator notes, staff notes, case notes, user records, and administrative comments.
- Ticket metadata and non-anonymous ticket records, subject to server configuration.
- Automod rule triggers, automod actions, and associated configuration.
- Server settings, module settings, role settings, panel settings, protocol settings, and logging settings.
- Statistics, analytics counters, invite counts, leaderboard values, and activity records where enabled.
- Wheel utility configuration or inputs where necessary to operate wheel-related features.
- Error logs, diagnostic logs, and security-related records necessary to maintain the Bot.
Such data is used to operate the Bot, maintain server safety, support moderation workflows, provide accountability, troubleshoot errors, preserve server configuration, and provide requested features.
Anonymous confession and anonymous vent ticket systems are treated differently. Those systems are designed not to store identity-linking information that reveals the anonymous submitter.
13. Wheel of Names API
Obsidian Protocol may use the Wheel of Names API to provide wheel-based random selection, spin animation, name picker, giveaway, event, selection, or utility features.
Wheel of Names is a separate third-party service. Obsidian Protocol is not Wheel of Names. Obsidian Protocol is not owned by Wheel of Names, operated by Wheel of Names, endorsed by Wheel of Names, certified by Wheel of Names, sponsored by Wheel of Names, or officially affiliated with Wheel of Names unless expressly stated otherwise in writing by Wheel of Names.
All credit for the Wheel of Names service, brand, platform, website, API, wheel functionality, and related intellectual property belongs to Wheel of Names and its respective owners. Obsidian Protocol acknowledges and respects Wheel of Names as the creator and provider of its own service and API.
Use of wheel-related features may involve sending limited wheel-related data to the Wheel of Names API, such as wheel entries, wheel configuration, labels, names, or options provided for the purpose of generating or operating a wheel. Users and server staff should not submit private, sensitive, confidential, or unnecessary personal information into wheel features.
Obsidian Protocol is not responsible for third-party outages, API changes, rate limits, data handling, policy changes, errors, downtime, or service discontinuation by Wheel of Names. Wheel-related features may stop working or change if the third-party API changes or becomes unavailable.
14. Moderation, Automod, and Administrative Systems
Obsidian Protocol may provide moderation and administration features, including bans, kicks, mutes, timeouts, warnings, notes, case records, message cleanup, diagnostics, profile inspection, automated moderation, trust systems, watchlists, and related tools.
Server owners and staff are responsible for how moderation tools are used. Obsidian Protocol does not independently determine a server's rules. The Bot provides tools that server staff may configure and use.
Automod may use keyword detection, regex filters, anti-spam rules, blacklist and whitelist systems, configurable punishments, alert channels, and logging. Automod may produce false positives or false negatives. Server staff are responsible for reviewing important automated actions where appropriate.
15. Tickets, Protocol Systems, and Community Features
Obsidian Protocol may provide ticketing systems for support, moderation, reports, appeals, staff contact, partnerships, applications, or other server workflows. Non-anonymous tickets may identify the ticket opener to server staff and may generate records or transcripts depending on server configuration.
Obsidian Protocol may include protocol systems such as CERBERUS, LUMEN, operational modes, alert routing, protocol activation, monitoring, reset controls, status embeds, and related features. These are server management tools and do not provide emergency services, law enforcement services, professional security services, medical services, legal services, or crisis response services.
Community features may include birthdays, starboards, confessions, invite tracking, wheel utilities, reaction-based tools, role systems, staff directories, and engagement systems. Users are responsible for the content they submit to these features.
16. User Content
Users may submit content through commands, forms, tickets, confessions, vent systems, moderation reports, applications, panels, wheel utilities, or other Bot features.
You retain any rights you have in content you submit, subject to the permissions necessary for Obsidian Protocol to process, display, transmit, moderate, store, or delete that content as required to provide the Service.
By submitting content to Obsidian Protocol, you grant Obsidian Protocol a limited, non-exclusive, worldwide, royalty-free permission to process that content solely for the purpose of operating the Bot, providing requested features, enforcing rules, maintaining safety, and complying with applicable obligations.
You may not submit content that is unlawful, violates Discord rules, violates server rules, harasses or threatens others, contains doxxing, contains malicious links, infringes intellectual property rights, impersonates others, or is otherwise harmful, abusive, deceptive, or inappropriate.
17. Privacy Policy
Your use of Obsidian Protocol is also governed by the Obsidian Protocol Privacy Policy.
The Privacy Policy explains what information may be processed, how it may be used, how data may be stored, how anonymous features work, how Sentinel Watch handles IP and geolocation limitations, and how users may contact the Bot operator regarding privacy matters.
By using Obsidian Protocol, you acknowledge that you have reviewed or had the opportunity to review the Privacy Policy.
18. Security
You agree not to compromise or attempt to compromise the security of Obsidian Protocol. You may not attempt to access Bot tokens, private databases, restricted logs, infrastructure, source code, anonymous identity systems, or other restricted resources.
You may not exploit vulnerabilities, conduct denial-of-service attacks, spam commands to disrupt service, upload malicious content, use the Bot to distribute malware or phishing links, bypass permissions, or attempt to expose anonymous users.
Security issues should be reported responsibly to the Bot operator through the contact method listed in these Terms.
19. Enforcement and Termination
We may enforce these Terms by ignoring or blocking commands, restricting access to features, blacklisting users, blacklisting servers, removing functionality, deleting or refusing to process content, reporting abuse to server staff, reporting serious violations to Discord, reporting illegal activity where required or appropriate, or suspending or terminating access to Obsidian Protocol.
We may suspend, restrict, or terminate access to Obsidian Protocol at any time if you violate these Terms, violate Discord's rules, misuse the Bot, create security risks, abuse anonymous features, attempt to collect private user information, misrepresent Sentinel Watch, attempt to identify anonymous users, or use the Bot for unlawful purposes.
20. Disclaimers and Limitation of Liability
Obsidian Protocol is provided on an "as is" and "as available" basis. To the fullest extent permitted by law, we disclaim all warranties, whether express, implied, statutory, or otherwise, including warranties of merchantability, fitness for a particular purpose, non-infringement, availability, accuracy, reliability, security, and error-free operation.
We do not guarantee that the Bot will always be online, that automod will catch every violation, that automod will avoid every false positive, that logs will always be complete, that tickets will always be preserved, that analytics will always be accurate, that third-party APIs will remain available, or that Discord will not change its platform.
To the fullest extent permitted by law, Obsidian Protocol, the Bot operator, developers, contributors, maintainers, affiliates, and team members shall not be liable for indirect, incidental, special, consequential, exemplary, or punitive damages, including loss of data, server disruption, moderation errors, downtime, third-party API failures, Discord enforcement, misuse of Bot features, or unauthorized actions by server staff.
21. General Legal Terms
Indemnification
You agree to defend, indemnify, and hold harmless Obsidian Protocol, the Bot operator, developers, contributors, maintainers, affiliates, and team members from and against claims, damages, liabilities, losses, costs, and expenses arising from your use of the Bot, violation of these Terms, violation of Discord's rules, submitted content, server configuration, misuse of moderation tools, misuse of anonymous systems, misrepresentation of Sentinel Watch, or unauthorized access attempts.
Governing Law
These Terms shall be governed by the laws of Sweden, without regard to conflict of law principles. The Bot operator should designate an appropriate governing law before publishing these Terms.
Severability
If any provision of these Terms is found to be invalid, unlawful, or unenforceable, the remaining provisions will remain in full force and effect.
No Waiver
Failure to enforce any provision of these Terms does not constitute a waiver of that provision or any other provision.
Changes to These Terms
We may update these Terms from time to time. Continued use of Obsidian Protocol after updated Terms are posted means you accept the updated Terms.