- Shared responsibility: what MITHUNAI runs and what your organisation controls.
- Deployment modes: what the hosted service supports, and what is not offered.
- Subprocessors: the services your data is sent to. The list is for information; it is not yet contractual and changes are not yet notified.
- Data handling: what is stored, for how long, deletion, backups and incident response.
- Security questionnaire: short answers to the questions a review asks first.
How your data is handled
- Your content is not used to train models. MITHUNAI does not train models on your content. To answer a question, the relevant passages and the question are sent to the model provider your deployment is configured with, under that provider’s terms. See Models and providers.
- Your content stays in your organisation. It is used to answer your organisation’s questions and nothing else, and no other organisation’s request can retrieve it.
- Credentials in your content are redacted before indexing, so a key committed to a repository does not become searchable or reach a model.
- Deleting a source removes its documents from retrieval immediately.
- Conversations are stored so they can be listed and resumed, and can be deleted with Delete a conversation. There is no self-service export of an organisation’s data yet.
- Invitations are kept as a record. Each holds the invited email address, the role, who sent it, when it was sent, accepted or revoked, and a digest of its link, never the link itself. Accepted, revoked and expired invitations are kept, not deleted. The invitation email is sent through the email provider your deployment’s operator configures.
- Password-reset links are short-lived. A reset link’s digest is held for 30 minutes in the platform’s cache and then expires; it is not written to the database. The reset email goes through the same email provider.
- Saved connection tokens are encrypted. A token for GitHub, Confluence or Notion is stored encrypted with your organisation’s other records, alongside its name, its service, the Confluence site it is bound to, who saved it and when it was last used. It is never shown again, and deleting the connection destroys it. See Saved connections.
- Usage is counted without content. Every model call is recorded for your organisation with its surface, assistant, model, token counts, an estimated list-price cost where one is known, and whether it succeeded. The record holds no question, answer or person. Answers are also counted per calendar month against your allowance. These records are kept; nothing prunes them yet.
Controls in place
Not available yet
For security questionnaires, send them to your MITHUNAI contact. To report a security issue, see Security.