Skip to main content
WonkaChat is an enterprise AI chat platform built on top of LibreChat, a robust open-source project with a thriving community. We’ve enhanced it with enterprise-grade security, governance controls, and compliance features designed for organizations that need to use AI securely with their data.
This page covers the built-in security measures and governance controls that WonkaChat provides out of the box.

Governance

Control what AI models, tools, and agents are available in your organization. WonkaChat comes with extensive capabilities out of the box, but you can customize your deployment to include only what’s relevant for your company. This helps reducing complexity, minimizing unnecessary access, and maintaining a focused, secure environment.

Organization Access

MCP Selection

Wonka configures which MCP servers are available to your organization, ensuring only approved tools are accessible.

AI Model Selection

Administrators control which AI models and providers (OpenAI, Anthropic, Google, etc.) users can access within the organization.
These governance controls ensure your organization uses only approved AI resources that align with your security policies and compliance requirements.
Beyond WonkaChat’s built-in security measures, your organization maintains direct control over user access. For example, admins manage which agents are available to users and grant granular permissions per agent. See Access Control for details.

Security Architecture

WonkaChat implements enterprise-grade security with multiple layers of protection.

Authentication System

WonkaChat uses a secure, token-based authentication system to protect user access:
Short-lived access tokens allow users to authenticate and interact with the platform. These tokens expire after 15 minutes, minimizing the risk of unauthorized access if compromised.
Refresh tokens maintain user sessions for up to 7 days without requiring re-authentication. After 7 days, users need to log in again.
WonkaChat uses JSON Web Tokens (JWT) for secure, stateless authentication. JWTs are cryptographically signed to prevent tampering and verify authenticity.
This dual-token approach balances security (short-lived access) with user convenience (session persistence).

Authentication Providers

Multiple authentication methods are available to integrate with your existing identity systems:
WonkaChat currently supports these authentication providers:
  • Local Authentication: Username and password authentication
  • OpenID Connect: Integration with OpenID-compliant identity providers
  • Azure AD / Entra ID: Direct integration with Microsoft Azure Active Directory
Choose the authentication method that aligns with your organization’s identity management strategy.

Rate Limiting & Abuse Prevention

WonkaChat implements rate limiting to protect against brute force attacks and system abuse. Rate limits are applied across critical operations including login attempts, registration, password resets, administrative actions, and general API usage.
Rate limits protect your organization from automated attacks while allowing normal user activity.

Data Privacy

Your data remains secure and private throughout all interactions with WonkaChat.

Privacy Guarantees

Multi-Tenant Isolation

Complete data isolation between organizations through subdomain-based routing (https://.wonka.chat). No accidental data exposure across tenants.

No Model Training

Your conversations and data are never used to train AI models. Model providers process requests temporarily without retention. Your data stays in WonkaChat where you control it.

Encrypted in Transit

All data transmitted to and from WonkaChat is encrypted using HTTPS/TLS protocols for secure API communications.

Encrypted at Rest

Data stored in WonkaChat’s MongoDB databases is protected with encryption-at-rest support to secure your information.

Data Encryption

HTTPS/TLS for all communications:
  • All API calls use secure HTTPS/TLS protocols
  • Data is encrypted during transmission between your browser and WonkaChat servers
  • Secure connections to AI model providers (Azure, AWS Bedrock)
MongoDB encryption and secure storage:
  • Passwords: Hashed with bcrypt using salt rounds (never stored in plain text)
  • Tokens: JWT signing with strong cryptographic secrets
  • Database: MongoDB encryption-at-rest support for all stored data
  • API Keys: Never logged in plain text
Sensitive data protection in logs:
  • All logs automatically redact sensitive patterns (passwords, tokens, keys)
  • API keys and authentication tokens are never logged in plain text
  • Token rotation prevents long-term exposure
  • Passwords are hashed with bcrypt before any storage
Even system administrators cannot access your passwords or sensitive credentials in logs or databases.

Multi-Tenant Data Isolation

WonkaChat ensures complete separation between organizations:
Every piece of data in WonkaChat is scoped to your organization:
  • Conversations and chat history
  • AI agents and configurations
  • User accounts and permissions
  • MCP connections and tool settings
  • Audit logs and activity records
Data from one organization is completely isolated and inaccessible to other organizations.

Model Provider Security

WonkaChat connects to AI models through secure Azure and AWS Bedrock APIs. Your data is processed in real-time and never stored or retained by model providers.
When you interact with an AI model, your prompts and responses are sent to the model provider, processed in memory, and immediately discarded by the provider after generating the response.Your conversations are securely stored in WonkaChat for you to access your history, but model providers (Azure, AWS) never retain, store, or use your data for training or any other purpose.
Your conversation history is securely stored in WonkaChat where you control it. Model providers only process requests temporarily without any data retention or reuse.

Privacy Policy

For comprehensive details on how WonkaChat handles, processes, and protects your data, please review our Privacy Policy.

WonkaChat Privacy Policy

Read our complete Privacy Policy to understand data collection, usage, storage, and your rights as a WonkaChat user.

MCP Security Controls

WonkaChat supports MCP (Model Context Protocol) servers with granular security configuration and multi-user isolation.

Multi-User Isolation

Each user’s MCP authentication tokens are stored separately and securely:
  • Tokens are isolated per user account
  • No cross-user token access or sharing
  • Automatic token cleanup on user deactivation
Your MCP credentials are never accessible to other users, even within the same organization.
MCP connections use session-based authentication for security:
  • Automatic user identification via request headers
  • Session validation on every MCP operation
  • Timeout enforcement to prevent stale sessions
WonkaChat supports multiple MCP authentication methods:
  • in-tool: User authenticates directly within the connected tool
  • oauth: OAuth 2.0 flow for secure, delegated access
  • api-key: API key-based authentication for service integrations
The authentication strategy is determined by the MCP server provider and cannot be changed by your organization.

No Permission Escalation

Inherit Your Permissions

MCP connections inherit your exact permissions when accessing connected tools. They cannot access anything you couldn’t access manually.

No Admin Bypass

MCP connections cannot be used to override, bypass, or escalate permissions in connected systems. Your security policies remain fully enforced.
If you cannot access a resource or perform an action manually in a connected tool, the AI models cannot do it either (even if instructed to try).

What You Can Control

While WonkaChat provides robust built-in security, you control additional layers:
Combining WonkaChat’s built-in security with your organization’s access controls and practices creates a comprehensive security framework.