Privacy model
Privacy is the core of intenthybrid AI, not a setting. Everything the agent does, ask, predict, and act, runs through the private channel described on this page. If you read one page in this documentation, read this one.
Privacy is one of the always-on layers, which means it is a property of the whole product rather than a single setting. This page states exactly what stays with you and why.
The three commitments
History stays local. Your chat and its history live in your browser. There is no server-side copy on intenthybrid AI infrastructure.
Prompts run on infrastructure you control. Your questions are not logged to a third-party prompt service. Inference runs on infrastructure under your control, with no third-party prompt logging.
No account to start. You do not need an email or a sign-up to begin. You can read and converse without creating an identity first.
What "clear your browser, clear everything" means
Because the conversation lives client-side and is not mirrored to a server, clearing your browser storage removes it for good. There is no remote record to outlive the local one. This is a deliberate consequence of the design: the only copy is the one you hold, so you are the one who can erase it.
Why this matters for a risk tool
How you read risk, which markets you watch, and what you would do about them is sensitive. A tool that ships all of that to a server asks you to trust that server with your edge and your intentions. intenthybrid AI is built so that the sensitive parts, your conversation and your history, never leave your machine in the first place, which removes the question rather than asking you to trust an answer to it.
What does involve a server
Being honest about the boundary matters. Reading public market and liquidation data, settling an x402 payment through a facilitator, and executing an agent action onchain all involve systems beyond your browser, because they have to. The privacy commitments are specifically about your chat, your history, and your prompts. Public market data is public, onchain settlement is onchain by nature, and an agent acts from a wallet you connect. See Always-on layers for where each property applies.
Authentication and privacy together
When you choose to sign in, for example to connect a wallet so an agent can act, you take on an identity for that purpose. That does not move your chat history to a server. Authentication and the privacy of your conversation are separate concerns, and signing in to arm an agent does not change what stays local.