CH Support Assist: Privacy Policy
- CH Support Assist is a work tool for a customer support team. Only team members who have been given access can sign in and use it.
- It reads the conversation that the signed-in agent has open in the team's support inbox, suggests a reply, and puts that reply in the reply box. It never sends anything on its own. The agent reviews and sends every reply.
- Conversation text is processed inside the agent's browser and is not stored by the extension.
- No data is sold, used for advertising, or shared with data brokers. The extension has no analytics or tracking code.
1. Who this policy covers
This policy explains how the CH Support Assist Chrome extension (the "extension") handles information. The extension is developed and maintained by Tushar Mali (the "developer", "we"). It is meant only for members of the support team it was built for. It is not meant for patients, customers or the general public, and it does not work without an account that the team's administrator has enabled.
2. What the extension reads
The extension runs only on the team's support inbox pages: the Helpdesk inbox (email and SMS) and Helpwise (chat). It does not run on any other website and it does not read browsing history.
When the agent opens the side panel on one of those pages, the extension reads the conversation shown on that page:
- the messages in the open conversation, and whether each was written by the customer or by the team;
- the subject line, and the customer's first name so the reply can greet them;
- the text the agent highlights, if they choose "use selected text".
Internal notes written by staff are skipped. Conversation content may include personal and health-related information that customers chose to write. The extension uses it only to find and fill in a suggested reply on the agent's screen.
3. How that information is processed
- On the device. Matching the customer's question to a suggested reply happens inside the browser. If Chrome's built-in on-device AI model is available, the extension may use it to choose or reword a reply. That model runs on the computer, and the text does not leave the device.
- Not stored. The extension does not save conversation content. It is held in memory only while the panel is open.
- Only with the agent's action. A reply is placed in the reply box only when the agent clicks Insert. Nothing is sent to the customer by the extension.
4. What is sent to the team's server
The extension talks to one server: the team's own back-end server, over HTTPS. It sends:
| Data | Why | How long it is kept |
|---|---|---|
| Agent's work email address | To send a one-time sign-in code and check that the agent has access. | Sign-in codes expire after 10 minutes. |
| Session token | To keep the agent signed in. The server stores only a one-way hash of it. | Ends after 4 hours idle, 12 hours at most, or at sign-out. |
| Usage events (which suggested reply was shown, inserted or rated, and a reason code) | To see which replies work and improve them. These contain IDs and counts, not conversation text. | 90 days. |
| A short question with personal details removed (optional) | When no suggested reply fits, the question (at most 200 characters) can be sent so the team can write a new reply. Names, emails, phone numbers and similar details are removed in the browser first, and the question is not sent at all if it still looks identifying. The server checks it again. Agents can turn this off with the "Help improve replies" switch. | 90 days. |
| Suggested reply wording with personal details removed (optional) | When an agent marks a reply "Not helpful", they can type the wording it should have. Names, emails, phone numbers and similar details are removed in the browser first and checked again on the server. A team reviewer reads it, and the reply library changes only if the reviewer approves. | 90 days. |
| Access log (which agent called which feature, when, the result, the extension version and a one-way hash of the IP address) | So the team's administrators can see who uses the tool and spot problems. It contains no conversation text. | 180 days. |
| AI usage records (which reply, the AI model, token counts, estimated cost, and whether the AI text was used) | So administrators can see AI use and its cost. They contain no conversation text and no AI output. | 400 days. |
| Administrator actions (granting access, publishing or approving replies) | Audit trail for the team's administrators. | As long as the tool is in use. |
The server sends back the team's approved reply library, which the extension may keep in the browser for up to 72 hours so it keeps working offline.
Optional AI replies. These work only if the team's administrator turns them on. Then the agent may choose "Reword with AI" or "Draft a reply with AI". Only then is a short excerpt, with personal details removed in the browser, sent to the team's server. The server removes contact details again and passes it to a cloud AI service run under the team's own data-processing agreements. The excerpt is used only to produce that reply. It is not stored and is not used to train AI models.
5. What is stored in the browser
- Settings: the agent's first name for sign-offs, an optional email, and on/off preferences. These are kept in Chrome storage. If Chrome sync is on, they sync to the agent's own Chrome profile.
- Session token: kept only in Chrome's session storage, which Chrome clears when the browser closes.
- Reply library cache (up to 72 hours) and a small queue of usage events waiting to be sent.
- Settings from the team's administrator, if the team manages Chrome centrally.
Signing out deletes the session, the cached library and the event queue. Removing the extension deletes everything it stored in the browser.
6. Sharing
We do not sell or rent any data. We do not share it with advertisers, data brokers or anyone else. Data is used only to provide the extension's single purpose: helping support agents reply to customers. Data reaches only the team's own server and, if AI rewording is turned on, the cloud AI provider that server uses to produce the reply. We may disclose information if the law requires it.
7. Chrome Web Store Limited Use
The use of information received through this extension follows the Chrome Web Store User Data Policy, including its Limited Use requirements. In particular:
- data is used only to provide or improve the extension's single purpose;
- it is not transferred except as described in this policy, as needed for that purpose, for security, or to comply with the law;
- it is not used or transferred for advertising, and it is not used to determine creditworthiness or for lending;
- no person reads user data unless the user agrees, it is needed for security or legal reasons, or the data is combined and anonymised.
8. Security
- All traffic uses HTTPS.
- Access requires an account that the team's administrator has enabled. Turning access off ends the agent's sessions straight away.
- Sign-in codes and session tokens are stored only as hashes, and sign-in is rate-limited.
- The extension contains no passwords or API keys. It loads no code from the internet, and it has no analytics or tracking libraries.
9. Your choices
- Turn off "Help improve replies" in the extension to stop sending even the redacted questions.
- Sign out, or remove the extension, to delete its local data.
- To have your sign-in data or usage events deleted from the server, contact the team's administrator or the developer at the address below.
10. Children
The extension is a workplace tool for adult staff. It is not directed at children.
11. Changes
If this policy changes, the new version will be posted on this page with a new effective date. A significant change, such as a new kind of data being sent, will be published before the extension starts doing it.
12. Contact
Tushar Mali, developer of CH Support Assist
Email: tushar.icarussolution@gmail.com