ConceptZero

Zero and your data

How Zero grounds its answers and actions in your connectors, skills, memory, and the docs corpus — what it can touch, what it can't, and how every action is audited.

Updated 7/26/2026

To be useful, Zero has to read real things about your account and the product. This page explains what it draws on, where the limits are, and how its actions are recorded.

What Zero grounds its answers in

  • The documentation corpus — Zero searches connect0's own docs (the same content you're reading) and cites specific pages with deep links. The public MCP tool connect0_search_docs exposes this same search to external clients. If Zero finds no relevant doc, it says so rather than guessing.
  • Your connectors — to answer "is my Notion connector healthy?" or to set one up, Zero reads your connector list and their health status.
  • Its skills — a curated, first-party skill library encodes how to set up, operate, and troubleshoot connect0. A "problem → solution" skill routes your free-text request to the right one.
  • Memory — Zero remembers context across sessions (for example, that you use Notion, that your production project is acme-prod, that you care about cost), so you don't repeat yourself.

What Zero can and cannot touch

  • Account-scoped only. Zero reads and acts on the one account it belongs to. It takes no cross-account parameters and cannot see any other account.
  • Read tools are side-effect-free. Listing agents, runs, usage, connectors, credit balance, and spend caps changes nothing.
  • Writes are confirmation-gated. Any change is proposed as an action card and executed only after you approve it — see Chatting with Zero.
  • Role-bound. Zero can do exactly what your role allows. A viewer gets a read-only Zero; write actions need the same role the dashboard requires.
  • Injection-resistant. Zero reads account content (run outputs, connector data) that could contain adversarial text. Because tool calls are schema-validated and every mutation needs your explicit confirm, the worst injected text can do is propose a change you must still approve.

Every action is audited

Each action Zero takes writes an audit row under the zero.action audit kind, alongside the normal agent audit trail. You get a durable, reviewable record of what Zero did on your behalf, when, and at whose confirmation — the same accountability guarantee that applies to every agent on the platform.

Where to go next

Ask Zero

Ask a question about connect0 and get an answer grounded in the docs, with links to the sources. Signed in? Zero answers with your account in mind.