Everyone – Security, privacy, and trust center

Related

• Accounts and keys: Users – Accounts, keys, and your data
• Self-host: Platforms – cloud and Docker

Public documentation hygiene

These pages target a broad audience. Do not embed: live API keys, LLM provider secrets, database or Redis connection strings, Clerk or payment-provider live secrets, webhook signing keys, CI or deploy tokens, private production hostnames, customer debate text, or screenshots of real usage. Prefer placeholders and synthetic JSON.

Threat model in plain language

You send topics to LLM providers you configure. Those providers process content under their terms.

What Consilium stores

Hosted deployments typically persist debates and metadata in Postgres; queues use Redis. Self-hosters control both.

Secrets

Never paste keys into public chats. Rotate keys if leaked. Prefer scoped provider keys where available.

Monitoring

Production may use Sentry or similar — check your deployment notice.