Kshitij ERP — Team chat terms (Mattermost)
Last updated 4 November 2026
Your staff get the app's alerts and talk to each other on a Mattermost chat server. What they write is the company's to answer for, and a chat administrator can read all of it — so the app never sends a code there.
- The service. The app sends the Customer's staff its alerts and approval requests as direct messages from the Customer's bot, and posts to the channels the Customer chooses, on the Mattermost server named in the Customer's settings.
- Who can read it. A Mattermost administrator can read every message on the server, direct messages included. So the app never sends a sign-in or approval code over chat, and the Customer should not post passwords, card numbers or customers' documents there.
- The Customer's people. The Customer decides who has a chat account, removes people who leave, and is responsible for what its people post, under its own workplace rules and the law.
- Kshitij does not read it. Kshitij does not read or moderate the Customer's messages. Where Kshitij runs the server, it looks at them only to keep the server working or when the law requires it, and tells the Customer when it can.
- Nothing waits on chat alone. The server taking a message is all the app can know about it. An approval request also waits in the app's Approvals screen, so nothing that needs a decision depends on chat being read.
- Charges. As set out in the Order.
- Limit of liability. Kshitij's liability for team chat is capped at the chat charges the Customer paid in the 3 months before the claim, and indirect loss is excluded.
- When chat ends. The app stops sending to the server. Where Kshitij runs it, the history stays exportable for 30 days, and then Schedule 1, clause 8 of the SaaS Subscription Agreement applies.
Version 1.0 · in effect from 2026-11-04