> ## Documentation Index
> Fetch the complete documentation index at: https://docs.helpalive.com/llms.txt
> Use this file to discover all available pages before exploring further.
# HelpAlive subprocessors and data hosting
> What kinds of company process data for HelpAlive, the data each receives, where HelpAlive's servers are hosted, and where to find the full subprocessor list.
A subprocessor is an outside company that processes data on HelpAlive's behalf so that we can run the service. This page explains what kinds of company receive data when you use HelpAlive and whose data they handle. The legal list, with each company's name, is kept in one place: our [subprocessor list](https://helpalive.com/legal/sub-processors). It is for privacy and security reviewers, and for admins who list processors in their own notice.
The [subprocessor list](https://helpalive.com/legal/sub-processors) is kept current as companies are added or removed. Questions about it go to [support@helpalive.com](mailto:support@helpalive.com).
## Subprocessors at a glance
* Our servers and databases run in the United States (US East).
* Your users' data goes to the AI model provider, a search relevance service, our hosting, our network and our server logs.
* Your team's data also goes to payments, our customer records, team emails and website icons.
* Server logs are kept 30 days. The AI model provider may keep requests, normally for up to 30 days, for abuse checks.
* No analytics, advertising or chat-vendor scripts run in our script, the widget or the dashboard.
* The full list, with each company's name, is our [subprocessor list](https://helpalive.com/legal/sub-processors).
## Where HelpAlive data is hosted
Our servers and databases run in the United States (US East). Backups are kept with the same hosting company.
## What each kind of company receives
| Purpose | Data it receives |
| - | - |
| AI model for chat answers and assists | Chat messages, the page as structured text, and the profile fields and docs passages the answer needs. Requests may be kept, normally for up to 30 days, for abuse checks. |
| Search relevance: picks the passages from your docs that fit a question | The search query and passages from your docs |
| Hosting for our servers, databases and backups | Everything HelpAlive stores. Server logs are kept 30 days. |
| Network in front of our addresses | All traffic, including IP addresses |
| Server logs | Server log lines, which include chat text and the pages assists read. Kept 30 days. |
| Payments and billing | Company name, the admin's email and billable usage. Card details are entered on the payment provider's own checkout. |
| Our customer records | Your workspace's name and domain, its plan and usage totals, and team members' names and emails |
| Emails to your team | Team members' names and emails. It never emails your users. |
| Website icons on **Train**, and a font in our emails | Help site names and the viewer's IP address |
| Fetching the public help sites you add on **Train** | The addresses of your help sites. It reads those public pages for us, and no user data. |
## What is not on this list
* No analytics, advertising or chat-vendor scripts run in our script, the widget or the dashboard.
* The software that redacts usage events runs on our own servers, so no outside company receives that data for redaction.
## Privacy policy and terms
These pages explain how HelpAlive handles data in practice. The legal terms are in our [Privacy policy](https://helpalive.com/legal/privacy), [Terms of use](https://helpalive.com/legal/terms) and [subprocessor list](https://helpalive.com/legal/sub-processors).
## Next
What goes to the model provider, and why.
Everything collected, redacted and kept.
Keys, verified users and sign-in.
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.