AI and your data at a glance
- The agent reads the current page only when someone uses the chat or an assist. Apart from password, card, one-time-code, file-upload and hidden fields, that page view is not redacted.
- Before activity is stored, our servers scan its text and replace names, email addresses, phone numbers, IP addresses and card numbers. The scan is automatic and can miss some.
- The model provider doesn’t train on data sent through its API.
- The page the agent read is not saved to our database.
- Chat messages and assist text are kept for the window you set on Settings → Privacy Management, 1 year by default.
Why the agent needs your data
The agent answers questions about the page a user is on, and does tasks on that page. To do that, it has to read the page and know what the user is trying to do. Everything below is sent for that purpose, at the moment the user uses the chat or an assist.What HelpAlive reads, and when
Always, while the script runs: activity only. HelpAlive records which pages are viewed, what is clicked, which fields change and which errors appear. This is not a copy of the page. Before activity is stored, our servers scan its text and replace names, email addresses, phone numbers, IP addresses and card numbers. The scan is automatic and can miss some. Password, card and one-time-code fields are never collected. Only when someone uses the agent: the page. When a user opens the chat, asks a question or runs an assist, the agent reads the current page as text, the way a person would see it, so it can help. That page goes to our model provider and is not redacted, apart from the fields listed below, because it is what the agent works from. No copy of the page is taken at any other time.What is sent, and when
The model receives only what the current moment needs. That falls into five kinds of data:
Field values are sent as shown, except in password, card, one-time-code, file-upload and hidden fields, and in any field holding a card number. Apart from those fields, the page is not redacted, because it is what the agent needs to see. The
email field from identify() is never sent to the model. An email the agent can see elsewhere, such as in displayName, on the page or in a chat, is sent.
Your docs’ text and your users’ questions are also processed to find the right passages. Our model provider and a search-relevance provider do this work. See Subprocessors.
Where answers come from
Answers come from the sources you publish on Train. Drafts never reach your users. Where your docs are silent, the agent can use general knowledge of your product, and your docs win when the two disagree. See How HelpAlive works.Model training and retention
- The model provider doesn’t train on data sent through its API. That covers the pages, questions and docs HelpAlive sends it.
- We ask the provider not to store responses.
- The provider may keep requests and responses, normally for up to 30 days, to check for abuse.
- We may use the kept words of chats and assists, de-identified, to improve HelpAlive for all customers. To opt out, write to support@helpalive.com. See Privacy Management.
What we keep afterwards
- The page the agent read is not saved to our database. A running assist holds it only while the assist is in progress.
- Chat messages and assist text are kept in our database for the window you set on Settings → Privacy Management, 1 year by default.
- Our server logs can hold users’ chat questions and the page text assists read, never values typed into fields, for 30 days.
What you control
- Who gets the agent, and whether it does the steps or shows how, on Controls.
- What it answers from, on Train. Only published sources are used.
- How long chat and assist text is kept, on Settings → Privacy Management.
- Deleting a person’s or tenant’s data, on Settings → Privacy Management.
Privacy policy and terms
These pages explain how HelpAlive handles data in practice. The legal terms are in our Privacy policy and Terms of use.Next
Data we collect
Everything collected, redacted and kept.
Subprocessors
Who processes data, and for what.
Safety and hand-backs
Hand-backs and confirmations.

