---
title: "Security"
description: "The guarantees Chickpea makes, how authority and confirmation work, what is stored where, and what leaves your infrastructure."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.chickpea.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Security

Chickpea's security model rests on a few rules that are checked in code: credentials never reach the model, conversation cannot expand authority, and consequential actions need confirmation. This section states each rule and the mechanism behind it.

- **Security model** — The guarantees a deployment enforces in code, the mechanism behind each, and the limits. [Read it](/security/security-model).
- **Authority and confirmation** — Where authority comes from, what applies immediately, and what waits for your explicit approval. [Read it](/security/authority-and-confirmation).
- **Data and storage** — Where deployment state lives on each target, how credentials are keyed, and retention. [Read it](/security/data-and-storage).
- **The shared Slack gateway** — What the Chickpea-operated Slack gateway sees, stores, never stores, and how to avoid it. [Read it](/security/shared-slack-gateway).
- **Product telemetry** — Six anonymous, content-free events, what they never carry, and the total opt-out. [Read it](/security/telemetry).
- **Recovery** — Repair a deployment that can no longer authenticate its own Slack app. [Read it](/security/recovery).

Source: https://docs.chickpea.co/security/index.mdx