1. Introduction
This Privacy Policy explains how Obsidian Protocol ("Obsidian Protocol," "the Bot," "the Application," "we," "us," or "our") collects, uses, stores, processes, protects, and deletes information when the Bot is installed in, accessed through, or used within Discord servers, Discord channels, Discord application commands, Discord components, Discord tickets, and related Discord-based features.
Obsidian Protocol is designed as a modular Discord server management, moderation, automation, ticketing, analytics, and community utility system. Because the Bot operates through Discord, certain information made available through Discord may be processed for the Bot to function properly.
By using Obsidian Protocol, interacting with its commands, submitting forms, using ticket systems, participating in supported server features, or remaining in a Discord server where Obsidian Protocol is installed and active, you acknowledge that you have read and understood this Privacy Policy.
2. Relationship to Discord
Obsidian Protocol operates on Discord and depends on Discord's platform, APIs, permissions, interaction systems, and developer services.
Use of Obsidian Protocol does not replace, override, modify, or supersede Discord's own Terms of Service, Privacy Policy, Community Guidelines, Developer Terms of Service, Developer Policy, or any other applicable Discord rules, policies, or requirements.
Users remain responsible for complying with Discord's rules and policies. Server owners, administrators, and moderators are responsible for ensuring that their use of Obsidian Protocol within their communities is lawful, appropriate, and consistent with Discord's requirements.
Obsidian Protocol is not owned by Discord, operated by Discord, endorsed by Discord, sponsored by Discord, or officially affiliated with Discord unless expressly stated otherwise in writing by Discord.
3. Scope of This Policy
This Privacy Policy applies to information handled by Obsidian Protocol when:
- The Bot is installed in a Discord server.
- A user interacts with Obsidian Protocol through slash commands, buttons, menus, panels, or modals.
- A user opens, responds to, or participates in a ticket system.
- A user uses anonymous confession or anonymous vent features.
- A server uses logging, moderation, automod, analytics, statistics, protocol, role, welcome, goodbye, starboard, invite tracking, or utility features.
- A server configures Obsidian Protocol settings.
- Obsidian Protocol processes Discord events necessary to provide enabled functionality.
This Privacy Policy does not apply to Discord's independent data practices, third-party bots, external websites not controlled by the Bot operator, or manual actions taken by server staff outside the Bot.
4. Information We May Process
The exact information processed by Obsidian Protocol depends on which modules are enabled, how a server configures the Bot, and which permissions are granted.
4.1 Discord Account Identifiers
Obsidian Protocol may process Discord user IDs, usernames, display names, server nicknames, avatar references, role memberships, permission status, and server membership status. These identifiers are used for commands, moderation tools, ticket routing, role systems, analytics, and server configuration.
4.2 Server, Channel, and Role Information
The Bot may process server IDs, server names, channel IDs, channel names, category IDs, role IDs, role names, permission structures, enabled modules, logging channels, ticket panels, automod rules, welcome/goodbye settings, and protocol alert channels.
4.3 Command and Interaction Data
When users interact with the Bot, Obsidian Protocol may process command names, command options, button clicks, menu choices, modal submissions, timestamps, user IDs, server context, channel context, permission checks, and command success or failure status.
4.4 Moderation and Administration Data
If moderation features are enabled, the Bot may process and save moderation-related data, including user IDs, moderator IDs, punishments, action types, warning records, mute records, timeout records, kick records, ban records, unban records, case numbers, moderation reasons, evidence references, timestamps, moderator notes, administrative notes, and appeal references.
| Data Type | Example | Purpose |
|---|---|---|
| User ID | Discord numeric user identifier | Associating records with the correct Discord account |
| Punishment | Warn, mute, timeout, kick, ban | Server rule enforcement and accountability |
| Notes | Moderator or staff notes | Context for future moderation decisions |
| Case Records | Case number, reason, timestamp | Moderation history, appeals, and recordkeeping |
4.5 Automod Data
If automated moderation is enabled, Obsidian Protocol may process message content necessary to evaluate configured filters, triggered keyword or regex rule identifiers, user IDs associated with triggered rules, channel IDs, timestamps, actions taken, whitelist/blacklist settings, and punishment configurations.
4.6 Ticket System Data
For ordinary non-anonymous tickets, Obsidian Protocol may process the ticket opener's user ID, ticket channel ID, ticket category, ticket reason, ticket status, staff responses, message content within the ticket, timestamps, transcripts where enabled, and closure metadata.
Anonymous confession and anonymous vent tickets are governed by the strict anonymity rules in Section 7.
4.7 Statistics and Analytics Data
If statistics or analytics features are enabled, the Bot may process message count totals, voice activity duration, command usage counts, leaderboard values, invite counts, activity timestamps, and server-level or user-level engagement metrics where configured.
4.8 Community Feature Data
Depending on enabled features, Obsidian Protocol may process birthday entries, starboard message references, invite tracking data, trust score entries, watchlist entries, confession submissions, anonymous community submissions, wheel utility entries, reaction-based moderation data, welcome events, and goodbye events.
4.9 Message Content
Obsidian Protocol may process message content only where necessary for enabled functionality, such as automod filtering, purge utilities, starboard systems, ticket responses, confession submissions, form submissions, command arguments, or user-submitted modals.
The Bot does not process message content for unrelated advertising, resale, behavioral advertising, or unrelated profiling.
5. Information We Do Not Intentionally Collect
Obsidian Protocol does not intentionally collect payment card numbers, banking information, government identification numbers, passwords, Discord account passwords, private authentication tokens from users, biometric identifiers, precise physical addresses, private health records, or private financial records.
Users should not submit sensitive personal information to Obsidian Protocol unless specifically required for a legitimate server support purpose and unless they understand how the information will be handled.
6. Sentinel Watch: IP Address and Geolocation Privacy
Neither moderators, administrators, server owners, server staff, nor the Bot owner can view user IP addresses or geolocation data through Sentinel Watch.
For the avoidance of doubt:
- Moderators cannot see IP addresses through Sentinel Watch.
- Administrators cannot see IP addresses through Sentinel Watch.
- Server owners cannot see IP addresses through Sentinel Watch.
- Server staff cannot see IP addresses through Sentinel Watch.
- The Bot owner cannot see user IP addresses through Sentinel Watch.
- Moderators cannot see geolocation data through Sentinel Watch.
- Administrators cannot see geolocation data through Sentinel Watch.
- Server owners cannot see geolocation data through Sentinel Watch.
- Server staff cannot see geolocation data through Sentinel Watch.
- The Bot owner cannot see user geolocation data through Sentinel Watch.
Sentinel Watch is not intended to function as an IP logger, geolocation tracker, doxxing tool, location detection tool, physical tracking system, or hidden surveillance mechanism.
If Sentinel Watch uses risk indicators, abuse signals, account metadata, server behavior patterns, or rule-based checks, such processing is not designed to expose IP addresses or geolocation data to human operators.
7. Anonymous Confessions and Anonymous Vent Tickets
Confession submissions and vent tickets designated as anonymous are intended to be 100% anonymous within Obsidian Protocol.
7.1 Anonymous Confessions
For anonymous confessions, the submitting user's identity is not shown to moderators, administrators, server owners, server staff, other users, or the Bot owner through Obsidian Protocol.
The submitting user's Discord ID, username, display name, nickname, avatar, or other direct account identifier is not included in public confession posts, staff-facing confession messages, hidden staff logs, Bot-owner views, transcript exports, or moderation transcripts generated by the anonymous confession system.
7.2 Anonymous Vent Tickets
Anonymous vent tickets are intended to allow users to privately express concerns, emotional distress, personal issues, or sensitive matters without having their identity revealed through the ticket system.
For anonymous vent tickets, the submitting user's identity is not shown to moderators, administrators, server owners, server staff, other users, or the Bot owner through Obsidian Protocol.
7.3 No Secret Transcripts
Obsidian Protocol does not create secret transcripts for anonymous confessions or anonymous vent tickets.
- There is no hidden transcript that reveals the anonymous user's identity.
- There is no staff-only transcript that reveals the anonymous user's identity.
- There is no Bot-owner-only transcript that reveals the anonymous user's identity.
- There is no private export file that secretly links anonymous content to the submitting user.
- There is no concealed moderation log that records who submitted an anonymous confession or anonymous vent ticket.
7.4 Limits of Anonymity
Obsidian Protocol is designed to preserve anonymity within the Bot's own systems. However, anonymity may be affected by factors outside the Bot's control, including a user voluntarily revealing identifying details, Discord's independent data processing, screenshots taken by other users, manual copying by staff, legal requests directed to Discord or other parties, or identifying details included by the user in the submitted content.
8. Purposes for Processing Information
Obsidian Protocol processes information for the following purposes:
- Providing Discord bot functionality.
- Responding to commands and interactions.
- Operating moderation and administration tools.
- Enforcing server-configured automod rules.
- Creating and managing ticket systems.
- Providing anonymous confession and anonymous vent features.
- Managing server settings and Bot configuration.
- Providing welcome, goodbye, role, utility, and community features.
- Generating server statistics and activity insights.
- Maintaining logs for accountability and troubleshooting.
- Preventing abuse, spam, misuse, or unauthorized access.
- Complying with Discord's applicable platform rules and applicable legal obligations.
9. Data Storage and Retention
Obsidian Protocol may store information in databases, configuration files, log systems, backups, or other storage systems controlled by the Bot operator or authorized hosting providers.
Stored information may include server configuration, user moderation records, punishment records, moderator notes, ticket metadata, command configuration, automod rules, community feature settings, analytics counters, protocol system status, staff configuration, and role configuration.
Retention periods may vary depending on server configuration, feature type, moderation requirements, ticket settings, legal requirements, security needs, and database maintenance practices.
11. Third-Party Services
11.1 Discord
Obsidian Protocol operates through Discord. Discord independently processes user information according to Discord's own terms and privacy policies. This Privacy Policy does not govern Discord's separate data practices.
11.2 Hosting, Database, and Infrastructure Providers
Obsidian Protocol may rely on hosting providers, database providers, logging providers, monitoring services, or similar infrastructure providers. Such providers may process limited technical information as necessary to provide their services.
11.3 Wheel of Names API
Obsidian Protocol may use the Wheel of Names API for wheel-based utility features, random selection tools, event tools, giveaway tools, or similar server utilities.
Obsidian Protocol is not an official affiliate, partner, sponsor, representative, agent, or endorsed product of Wheel of Names. All credit for Wheel of Names, its service, brand, website, technology, and API belongs to Wheel of Names and its respective owners.
Use of wheel-related features may involve sending wheel configuration or related utility data necessary to create or manage a wheel. Users and server owners should avoid submitting sensitive personal information into wheel entries.
12. Server and User Responsibilities
12.1 Server Owners and Administrators
Server owners and administrators are responsible for informing users that Obsidian Protocol is active where appropriate, configuring Bot permissions properly, limiting staff access to sensitive features, avoiding excessive or unnecessary data collection, and ensuring Bot usage complies with Discord rules and applicable law.
Server staff must not misrepresent Sentinel Watch as an IP or geolocation tracking tool and must not misrepresent anonymous confession or anonymous vent ticket features as secretly identifiable.
12.2 Users
Users are responsible for their own conduct when interacting with Obsidian Protocol. Users should not submit passwords, authentication tokens, payment details, government identification numbers, private addresses, illegal content, doxxing material, threats, harassment, or unnecessary sensitive personal information.
13. Data Rights and Requests
Depending on your location and applicable law, you may have rights to request access, correction, deletion, restriction, portability, or objection regarding personal data associated with you.
Users may submit requests using the contact information in this Privacy Policy. Reasonable verification may be required before fulfilling a request.
Requests may be limited where disclosure would reveal information about another user, compromise safety or security, expose moderation methods, violate Discord policies, violate applicable law, compromise anonymous confession or anonymous vent ticket anonymity, or involve data the Bot does not store or cannot reasonably retrieve.
14. Security
Obsidian Protocol uses reasonable technical and organizational measures intended to protect information against unauthorized access, misuse, alteration, loss, or disclosure.
Security measures may include permission-based access controls, restricted database access, limited staff access to sensitive records, logging and monitoring for errors and abuse, input validation, secure hosting practices, token protection, regular maintenance, and removal of unnecessary data where appropriate.
No online service, Discord bot, database, server, or transmission method can be guaranteed to be completely secure. Users should exercise caution when submitting information through Discord or through Bot features.
15. Children and Minors
Obsidian Protocol is intended for use on Discord and is subject to Discord's age requirements and policies. The Bot is not intended to knowingly collect personal information from children below the age permitted by Discord or applicable law.
If the Bot operator becomes aware that information has been collected in violation of applicable child privacy laws or Discord requirements, reasonable steps will be taken to delete such information, restrict access, or otherwise address the issue.
16. Changes to This Privacy Policy
This Privacy Policy may be updated from time to time to reflect changes in Bot functionality, Discord platform requirements, legal obligations, data handling practices, security practices, server feature availability, third-party services, or contact information.
When this Privacy Policy is updated, the "Last Updated" date should be revised. Continued use of Obsidian Protocol after changes are posted indicates acknowledgement of the updated Privacy Policy.
17. Contact Information
For privacy questions, data requests, deletion requests, concerns, or complaints regarding Obsidian Protocol, contact:
- Bot Operator: kellex_49
- Support Server: https://discord.gg/nqDmsxE64y
- Discord Contact: kellex_49
Please include enough information to understand and respond to your request. Do not include passwords, authentication tokens, payment details, or unnecessary sensitive personal information in your request.
18. Final Statement
Obsidian Protocol is designed to provide powerful Discord server management tools while respecting user privacy, Discord platform requirements, and the expectations of server communities.
Sentinel Watch is not an IP or geolocation exposure system. Moderators, administrators, server owners, server staff, and the Bot owner cannot view user IP addresses or geolocation data through Sentinel Watch.
Anonymous confessions and anonymous vent tickets are designed to be fully anonymous within Obsidian Protocol. They do not create secret identity records, secret staff transcripts, secret Bot-owner transcripts, or hidden logs that reveal the submitting user.