COMMUNITY & ASSISTANCE

We Are Here to Empower You

Whether you need help with Anti-Nuke setup, configuring Discord permissions, or tuning AI parameters, our documentation and support community have you covered.

Join Official Support Server Open Web Dashboard

🛡️ Anti-Nuke & Permission Setup Checklist

To enable KYOKA's Anti-Nuke to strip unauthorized roles or kick malicious administrators before damage occurs, Discord requires proper role hierarchy configuration:

1. Role Position Hierarchy
In your Discord Server Settings > Roles, drag the KYOKA integration role as high as possible (above all moderator and staff roles you wish to protect against).
2. Administrator Permission
Grant KYOKA Administrator permissions upon invite so it can manage quarantine roles, voice states, and incident alert channels without permission blocks.
3. Extra Owner Designations
Use +extraowner add @User for trusted co-founders so they can configure the bot and bypass anti-nuke triggers without Discord server transfer.

Frequently Asked Questions

Common questions about hosting, permissions, and security.

Is KYOKA 3.0 really free to host and use?

Yes! The frontend website is designed for 100% free hosting on Cloudflare Pages (with unlimited bandwidth and free SSL). The backend API and bot run smoothly on free hosting platforms such as Render, Koyeb, or Supabase PostgreSQL free tiers.

Why does the dashboard require Discord login?

We use Discord's official OAuth2 to verify your identity and confirm that you possess Manage Server or Administrator privileges. We only request your public username and server list—we never receive or ask for your password or tokens.

How is data protected between different Discord servers?

Every single API request to view or edit server settings performs a server-side permission verification against Discord's live gateway permissions. Even if a user attempts to manually forge a request for another guild ID, the backend API rejects it with HTTP 403 Forbidden.

What is the privacy and data retention policy?

KYOKA only stores server configuration parameters (such as prefixes, role IDs, and channel IDs) in your PostgreSQL database. Any member can opt out of message activity tracking at any time using the /privacy command.