Bot & Integration Policy
Rules for connecting the Guildorax Discord bot, webhooks, OAuth applications, API access and automated features.
Guildorax should request only permissions needed for enabled features. Server administrators remain responsible for reviewing and managing granted Discord permissions.
Authorized connections only
You may connect Guildorax to a Discord server, bot, application, webhook or channel only if you have the necessary permission to do so.
Feature-specific permissions
Features such as verification, tickets, role assignment, logging, analytics, invite repair, automated reports and channel setup may require different permissions. Guildorax may block setup if required permissions are missing rather than silently proceeding with an incomplete configuration.
Verification
Where enabled, Guildorax may validate a member, assign a configured role, send success/failure messages and create related logs. Server owners are responsible for selecting appropriate roles and ensuring the bot is positioned high enough in the Discord role hierarchy to perform authorized assignments.
Tickets
Guildorax may create private ticket channels, set permissions for the requesting user and selected staff, send configured embeds/messages and generate transcripts where enabled. Server owners must ensure ticket content is handled lawfully and with appropriate access controls.
Webhooks and custom branding
If Guildorax allows a user-supplied webhook, the user is responsible for creating it in an appropriate channel, protecting the webhook URL and ensuring the webhook has the permissions necessary for the requested feature. Guildorax may disable a webhook that is invalid, compromised or abused.
Automated setup and deletion
Where a server owner authorizes automatic setup, Guildorax may create or delete configured categories, channels, roles, messages or other Discord resources. Guildorax should clearly identify destructive actions before they are requested.
Analytics and reports
Guildorax may process server activity and statistics made available through Discord or configured Guildorax features to generate analytics, growth estimates, automated reports and dashboards. Forecasts and derived metrics are informational and are not guaranteed predictions.
API and rate limits
API access is subject to plan limits, authentication requirements and rate limits. You may not share secret keys publicly, circumvent quotas, resell access in violation of your plan, or use the API to harm Guildorax or third parties.
Discord dependency
Guildorax integrations depend on Discord APIs, permissions and platform rules. Features may stop working if Discord changes endpoints, intents, scopes, rate limits, permissions or policies.
Disconnecting Guildorax
Server owners can remove the Guildorax bot, revoke OAuth authorization, delete webhooks and disable integrations through Discord or Guildorax controls. Some historical logs or records may remain where required for security, billing, dispute resolution or legal compliance.
