Discord Permissions
DEV uses Discord permissions required by the modules and actions you enable. Role-based features also depend on Discord role hierarchy.
Trust should be documented.
Understand why DEV requests Discord permissions, how server-scoped configuration is separated, and when local or external AI systems may be involved.
Server-Scoped Data
Configuration, operational records and learned server context are associated with the Discord server they belong to rather than treated as one shared global server profile.
Local-First Intelligence
Local retrieval and decision systems handle supported work without sending every request to an external AI provider.
External AI Boundaries
Tasks can escalate to an external AI provider when the requested capability needs it. Provider usage is governed separately from DEV's local systems.
Security Evidence
Guardian is designed to keep the evidence behind risk and enforcement decisions available for staff review instead of relying on unexplained actions.
Private Security Reports
Report suspected vulnerabilities or sensitive security issues privately through Living DEV Support rather than posting them in a public channel.
Need a security or data answer for your server?
Join Living DEV Support and open a private ticket so server-specific details can be handled outside public chat.