Poco runs inside your coding sessions. This page covers what leaves your machine, what we keep, and the controls you have.

Local and remote.

The Poco client runs on your machine: it counts tokens, applies your organization's redaction policy, and installs the editor hooks. The compression itself - and command filtering and document conversion - runs on our server, which is why prompts and commands are transmitted.

Everything Poco sends travels over TLS, authenticated with your account's API key. Nothing is sent anywhere else.

No surprises.

Four things leave your machine, always over an encrypted connection and only ever to our server. What we keep once it arrives is governed by the retention control below.

Want secrets stripped before they ever leave? An org admin can switch on client-side secret masking, which redacts known secret patterns from prompts on your machine. It is off by default.

You decide what is retained.

Poco never has to keep your content. One organization setting - Store prompt payloads in Settings - controls it, and your admins decide.

Off: prompts, commands, documents, and transcripts are processed and dropped; only metadata and counts (project name, working directory, model, token totals, active AI tools) reach our database.

On: content is kept for your dashboard history. Prompt text is masked, and everything stored is deleted after 30 days.

Nothing hidden.

The binary ships unsigned today, and the installer clears macOS's quarantine flag so it can run. We would rather you know that than find it yourself: the install script is plain and readable, and the hooks Poco adds to your editor are readable commands, not obfuscated blobs.

Don't want curl | sh? Install the binary alone with POCO_NO_SETUP=1, or authorize non-interactively with POCO_API_KEY instead of the browser. Your key is stored only in ~/.poco/config.toml, readable by you alone.