Always used
MITHUNAI does not train models on your content. Each provider processes what it receives under its own terms. See Models and providers.
Used only when switched on
Services you connect
When your organisation connects a source or gives an AI employee a tool, MITHUNAI contacts that service on your instruction, with your own saved token where one is needed, and sends that token nowhere else: websites and sitemaps, GitHub, Confluence, Jira, Notion, Zendesk, Discourse, and for AI employees helpdesks, CRMs, mailboxes, identity providers and monitoring tools. These are your own vendors, under your own contracts with them. See Saved connections and Connect your tools.Services that receive none of your content
Let’s Encrypt issues the TLS certificates, the documentation site is hosted by Mintlify, and the marketing site at www.mithunai.com is hosted by Vercel. None of them receives anything from your organisation’s use of the product.Related pages
- Where MITHUNAI runs: what a deployment calls outside itself.
- Data handling: what is stored and for how long.
- Compliance: what MITHUNAI can and cannot claim.