# Chutes.ai security/privacy questions

**URL:** https://discuss.privacyguides.net/t/chutes-ai-security-privacy-questions/35540
**Category:** Questions
**Created:** 2026-02-16T10:29:38Z
**Posts:** 42
**Showing post:** 25 of 42

## Post 25 by @anon61753997 — 2026-02-16T21:25:03Z

> [@wildcat253](#):
>
> My initial question was basically if anyone knows if it’s done correctly.

No. In their blog post, Chutes said that verifiability is “the end goal”. In other words, it’s not verifiable at the moment.

> [@Colter](#):
>
> If it run on a different machine then you can’t guarantee that they don’t access it.

[Confidential computing](https://en.wikipedia.org/w/index.php?title=Confidential_computing) has its upsides and downsides. You need two _hardware_ features for it to work:

- Remote attestation: For example, I give you a software binary, which you can hash and compare it with the hash that the hardware produces from the software that it is running.
- TEE: If being used correctly by software, it can deprive the hardware owners of access to some data. The most popular use case is for “premium content protection”. :upside_down_face:

Connect the two dots and you can roughly understand how confidential computing works.

> [@wildcat253](#):
>
> Do you (or anyone else for that matter) have a better recommendation for someone who needs an AI provider with SOTA models?

Out of the four (Chutes, Maple, Tinfoil, and Confer), Tinfoil is the best at transparency by virtue of being open source. I’m pretty sure that none are being audited by third-parties. You can read how their remote attestation works [here](https://tinfoil.sh/blog/2025-01-13-how-tinfoil-builds-trust). [Their blog](https://tinfoil.sh/blog) is also great if you want to learn more about confidential generative AI. But again, it has less LLM models than Chutes, which is unverifiable right now (but may in the future).

---

_[View the full topic](https://discuss.privacyguides.net/t/chutes-ai-security-privacy-questions/35540)._
