No promises.

01Experimental status

This service is in active early-stage development. It is offered "as is" and "as available." Specifically:

• Behavior, endpoints, pricing, and the model catalog can change without notice.
• The service may have downtime, regressions, or full outages.
• The entire project may be discontinued at any time, with or without warning.
• Stored balances are best-effort. We backup, but if something catastrophic happens to our infrastructure, refunds are not guaranteed.
• The underlying compute (chutes / Bittensor / cloud / TEE chip vendors) may change, fail, or revoke us. We have no control over upstream availability.

If your work cannot tolerate any of these, do not build production reliance on Cloister.

02No warranty · no liability

If you cannot accept this, do not use Cloister.

03Privacy claims

We describe Cloister as "private by physics, not by policy" — the security model relies on hardware Trusted Execution Environments enforcing memory isolation. Specifically:

• The TEE security guarantee depends on the chip vendor (Intel, AMD, NVIDIA) being honest and the hardware not having undisclosed vulnerabilities. If a confidential-compute exploit is found, it could in theory expose plaintext.
• Cloister cannot independently verify each enclave's attestation chain in real time. We trust the upstream compute partner's attestation claims.
• We do not log prompts or outputs, but the TLS path between you and our gateway, and between our gateway and the compute partner, depends on standard internet plumbing. Network metadata (timing, request sizes) is not encrypted by the TEE.
• Side-channel attacks, traffic analysis, supply-chain compromises, and similar threats are outside the scope of what a TEE alone protects. If your threat model includes a nation-state adversary or a determined hardware attacker, this service is not sufficient.

The privacy pitch is strong but not absolute. Use Cloister for what it credibly delivers — a substantial improvement over plaintext model APIs — not for what it doesn't claim to deliver.

04$CLOISTER is not a security

05No financial advice

Nothing on this site — including pricing examples, oracle quotes, TAO/USD displays, or any commentary — constitutes financial, investment, tax, or legal advice. TAO, like every crypto asset, can lose value. Past prices are not predictive of future prices. Do your own research.

06Compute partners — chutes.ai

07Your responsibilities

By using Cloister you confirm that:

• You are of legal age in your jurisdiction to enter into binding agreements.
• Your use of the service does not violate the laws of your jurisdiction, including export controls, sanctions, and AI-related regulation.
• You will not use Cloister to generate content that is illegal where you live or where Cloister's compute partners operate — including but not limited to CSAM, content infringing third-party rights, content used to harm others, or output intended to facilitate violence.
• You are solely responsible for the content of any prompts you submit and any outputs you receive.
• You accept that the only proof of ownership over your account is the 16-character code you generate; if you lose it, the balance is lost forever and we cannot recover it. Treat the code like a seed phrase.

08Output is not factual

Models hallucinate. The outputs of any LLM, including those served via Cloister, may be inaccurate, misleading, biased, or fabricated. Do not rely on model output for medical, legal, financial, safety-critical, or otherwise consequential decisions without independent verification.

09Changes to this disclaimer

This page may change as the project evolves. The version you see is the version that applies on the date you read it. We do not maintain a separate changelog of disclaimer revisions; continued use of the service after changes are published constitutes acceptance.