1. Principle of Data Minimization
KYOKA 3.0 operates under the strict principle of data minimization. We only collect the minimal identifiers necessary to execute security enforcement, audio streaming, member verification, modular ticket management, and guild configuration persistence.
2. Telemetry and Records Collected
To provide operational services, the following data may be stored in our cloud PostgreSQL database:
- Discord Identifiers: Guild IDs, User IDs, Channel IDs, and Role IDs for configuration bindings and permission checking.
- Server Configuration: Custom prefixes, language preferences, log channel destinations, moderation thresholds, and anti-nuke rules.
- Leveling & Activity Metrics: Aggregate message count and XP score per guild for leaderboard calculation.
- Security Audit Trails: Timestamped records of administrative actions (e.g. anti-nuke triggers, whitelist modifications, and role updates) for guild owner forensic review.
3. Data We NEVER Collect
We strictly do NOT log, store, sell, or monitor:
- Passwords, personal emails, or credit card details.
- Private Direct Messages (DMs) between Discord users.
- Message content outside configured verification, sticky message, or AI interaction channels.
- Discord user OAuth access tokens (tokens are securely discarded after session generation).
4. Artificial Intelligence Subsystem
When interacting with the KYOKA neural AI persona in designated channels, prompts are transmitted via encrypted HTTPS to Groq inference infrastructure for real-time generation. Prompts are processed ephemerally and are never retained, sold, or utilized for model training.
5. Right to Erasure (GDPR / CCPA)
Every Discord user and guild administrator maintains full sovereignty over their records:
- User Data Purge: Execute
/privacy forgetin any server to erase all personal XP, leveling records, and afk notes. - Guild Data Deletion: Guild owners can reset all guild settings using
/config reset, or remove KYOKA from the server to flag all records for automated expiration.
6. Infrastructure Security
Database communication is encrypted with TLS 1.3 across Supabase / AWS cloud infrastructure. Web session cookies are protected with HMAC-SHA256 signatures, HttpOnly flags, and cross-site scripting (CSP) headers.