> For the complete documentation index, see [llms.txt](https://docs.solcis.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solcis.ai/the-solcis-guarantee.md). # The Solcis Guarantee No data, ever, leaves your environment or your control. What we guarantee, why, what makes it true, how you check it, and what backs it. No data produced by, passed through or held in a Solcis deployment leaves your environment or your control. Not your AI systems' prompts, tool calls or traces. Not your controls or policies. Not the decisions, the compliance receipts or the evidence ledger. Not the inputs to or outputs from the model that runs the inference check. Not billing, licence or metering data. Not usage, telemetry or diagnostics. Nothing goes to us, and nothing goes anywhere you didn't send it. Customers can choose an upgrade availability check. It is optional. For air-gapped deployments, we provide an alternative process to ensure this guarantee sticks.
We warrant this in the [Software Licence and Terms](/legal-centre/software-licence-and-terms.md). It's a guarantee you can hold us to, not a design principle we describe. ## Our mission, and why we hold to it Solcis keeps AI answerable to the people and institutions it serves. Accountability requires visibility and verification, not another black box. Your controls, decisions, and evidence remain yours. [Accountable by design](/design-principles/accountable-by-design.md) explain how. We build software that organisations run and verify themselves. We do not host software or offer software as a service (SaaS). There is no hosted version that routes your data to us. Our engineering effort focuses entirely on building software, not hosting it. ## What makes it true It isn't a policy we follow. It's a property of the software. No component of a Solcis deployment makes an outbound connection to us or to anyone else. Architecture describes the components and connections in a deployment. There's no licence server to call, no update check, no telemetry endpoint and no opt-in diagnostics that phone home. Compliance Studio licensing works from a signed entitlement inside your deployment. The model is one you host, so inference never crosses your boundary either. If a component needed to reach us, the air-gapped deployment couldn't exist. It does, and it's the same software as every other profile. ## How you check it You don't have to take our word for it, and we'd rather you didn't. It gives you the verification method for each. The network policy to apply, the egress logs to read, and the air-gapped install that proves the point by construction. Run it with a default-deny egress rule. It works. ## What backs it Two things stand behind the property. The [Software Licence and Terms](/legal-centre/software-licence-and-terms.md) warrants it, in the words that bind us: no data leaves your environment or your control by any act of the software or of Solcis. The warranty travels with the licence, whoever deploys it for you. The release process makes the software you run inspectable. A signed manifest, digest-pinned images and a key fingerprint published out of band mean what you verified is what you're running. [Security and Integrity](/legal-centre/security-and-integrity.md) describes the integrity controls. ## What it doesn't cover Precision is part of the guarantee. Solcis governs your AI systems; it doesn't contain them. An AI system that calls an external service sends data to that service, and the Solcis Policy Engine's job is to decide whether it may. Your deployment, your backups and your exports are yours to secure. And a partner who hosts Solcis for you holds your deployment under your agreement with them, not with us. In every case the boundary is one you drew, and nothing crosses it because of us. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.solcis.ai/the-solcis-guarantee.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.