Data flow
What stays in a Breno instance, the one class of traffic that leaves it, and the optional services (email, payments, error tracking) that can also receive data.
Who else sees what I put in? This page answers it.
What stays#
An instance keeps everything on its own infrastructure: your documents, their passages and embeddings, the graph, memory records, the audit log, and connected-source credentials (encrypted at rest).
What leaves: model providers#
Exactly one class of traffic carries your content out: the text a model needs.
| When | What is sent | To whom |
|---|---|---|
| You ask a question or search with an answer | The retrieved passages the answer is built from, and your question | The configured model provider, so it can write the answer and cite it |
| An item is captured | The item's text, to compute the embedding that makes it searchable | The configured embedding provider |
| Extraction and checking | Passages, to extract entities and to check an answer | The configured model provider |
Which provider that is is a configuration decision of whoever operates the instance: a hosted service, or a model running on their own hardware. With a model on your own hardware, nothing leaves.
If you add your own Claude, ChatGPT or compatible account, answers use it first, and that usage goes to your provider. Embeddings and extraction still use the instance's own models. See Use your own AI model.
What leaves: optional services#
These are only used when configured, and carry only what their job needs.
| Service | Used for | What it receives |
|---|---|---|
| Email provider | Verification, password reset, invitations, and the receipt for a deletion | The recipient's address and the message |
| Payment processors (Stripe, Paystack) | Buying coins | Payment details, handled by the processor |
| Error tracking (opt-in) | Diagnosing failures | Error events only. Request cookies, headers, bodies and query strings are stripped before sending; no traces and no session replay |
| Connected sources | Reading from the tools you connect | Their API calls, authenticated as you chose |
What this site and these docs send#
The marketing site and this documentation load no analytics, tags or advertising, and write nothing to localStorage or sessionStorage. Docs search runs in your browser against a local index, and sends nothing. The contact page's map is a third-party embed, and loads only if you press its button. See the privacy notice.
Where data is stored#
A hosted instance runs in a region chosen by its operator; cross-border transfers of personal data are covered in the privacy notice.