// SECURITY ARCHITECTURE

Security First, Always

Every design decision in ClawHost prioritizes security and isolation. Your bot runs in a private container with no access to other bots, our infrastructure, or your data outside the container.

// CORE PRINCIPLES
COMPLETE ISOLATION

Each bot runs in its own Docker container with a dedicated network. Bots cannot communicate with each other, access the host system, or reach internal services.

ZERO TRUST PROXY

Bots never have direct access to AI provider APIs. Every request is authenticated, moderated, and logged through our proxy. No API keys are ever exposed to containers.

CONTENT MODERATION

All AI requests pass through content moderation before reaching the provider. Harmful, illegal, or policy-violating content is blocked automatically.

DATA PRIVACY

Your conversations are private. We don't read, train on, or share your bot's conversations. Container data is isolated and encrypted at rest.

WHAT BOTS CAN'T ACCESS

Host filesystem and system resources
MongoDB, Redis, or internal databases
Other bot containers (ICC disabled)
ClawHost application server
AI provider API keys (only proxy tokens)
Internal network services

AI PROXY LAYERS

// PROXY SECURITY
GATEWAY TOKEN AUTHEvery request must include a valid gateway token unique to each bot
RATE LIMITINGRequests are rate-limited per bot to prevent abuse and runaway costs
CONTENT MODERATIONInput and output are scanned for harmful content before processing
TOKEN COUNTINGEvery token is counted and deducted from credits in real time
CREDIT CHECKRequests are rejected if the account has insufficient credits

WHAT GETS BLOCKED

Illegal content generation requests
Personal data extraction attempts
Prompt injection and jailbreak attempts
Hate speech and harassment
Content violating AI provider terms

YOUR DATA, YOUR CONTROL

Do you read our conversations?

No. Conversations pass through our proxy for moderation and billing but are not stored or reviewed by humans.

Is my data used to train AI models?

No. Your conversation data is never used for training. Each provider has their own data policies, which we enforce via API agreements.

Where is my data stored?

Bot configuration and metadata are stored in our database. Conversation data exists only within your isolated container.

Can I delete my data?

Yes. Deleting your bot removes the container and all associated data permanently.

ACCOUNT SECURITY

OAuth 2.0 via GitHub or Google (no passwords stored)
JWT session tokens with expiration
All API routes require authentication
Admin panel separated with role-based access

INFRASTRUCTURE SECURITY

HTTPS everywhere — all traffic encrypted in transit
MongoDB with authentication and encrypted connections
Redis with password authentication
Docker socket not exposed to containers