This AI Privacy Notice explains how the Userpilot AI Features handle data. It adds to the Userpilot Privacy Policy and the Userpilot Terms of Use. Customer Data is also covered by the Customer’s DPA with Userpilot. If this notice and the DPA conflict, the DPA prevails.
1. The Two AI Features
Userpilot offers two AI Features. They work differently, so this notice describes each one separately:
- Lia, the Userpilot AI assistant (Section 4). Lia is built into the Web App and is run by Userpilot. It is currently offered as a closed beta.
- The Userpilot MCP Server (Section 5). The MCP Server lets an Authorized User connect an AI tool of their choice, such as ChatGPT, Claude, Microsoft Copilot or Cursor, to their Userpilot account. The AI tool’s provider runs that tool, not Userpilot.
| Lia | MCP Server | |
|---|---|---|
| Who runs the AI | Userpilot | The provider of the AI tool the Authorized User connects (for example OpenAI or Anthropic) |
| Where data goes | It stays in the same environment as the Customer’s Web App account | To the AI tool the Authorized User connects, under that provider’s terms |
| What it can do | Answer questions, analyze data, and prepare changes that an Authorized User approves before they run | Read data, and create or update segments, reports, dashboards and draft surveys, within the permissions granted |
| Availability | Closed beta: enabled only when a Customer’s Administrators request access and Userpilot grants it | Off unless an Authorized User connects an AI tool |
2. Definitions
Capitalized words have the meanings below. They match the Userpilot Privacy Policy and Terms of Use.
- Administrator means an Authorized User who has permission to manage the Customer’s Account users, settings, connections and AI Features.
- AI Assistant or Lia means the AI assistant built into the Web App, which Userpilot provides and operates.
- AI Features means the AI Assistant and the MCP Server, together and each one separately.
- Authorized User means an individual whom a Customer allows to access the Web App under the Customer’s Account.
- Customer has the meaning given in the Userpilot Terms of Use: the person or entity that has an Account and subscribes to Userpilot.
- Customer Data means data that the Customer submits to the Web App, including through the Userpilot snippet, SDK, API or integrations that the Customer installs and configures, and including data about the Customer’s end users. Userpilot does not collect Customer Data on its own; it only processes what the Customer chooses to send.
- DPA means the data processing agreement between Userpilot and a Customer.
- MCP Server means the Model Context Protocol server that Userpilot provides so that an Authorized User can connect a third-party AI tool to the Customer’s Account.
- Web App means the Userpilot web application that a Customer and its Authorized Users access after signing up, including its dashboard, its AI Features and its integrations.
3. Who Is Responsible for What
- Customer Data. Userpilot does not own Customer Data. The Customer owns it, and Userpilot processes it only on the Customer’s behalf and instructions, as the DPA describes. This includes Customer Data used by Lia, and Lia’s conversation history.
- Account and connection details. For the account details of Authorized Users and the MCP connection details described in Section 5, Userpilot decides how the data is used, as described in the Userpilot Privacy Policy.
- AI tools connected through the MCP Server. When an AI tool receives data from Userpilot, the tool’s provider handles it under its own terms and privacy policy. The provider is not Userpilot’s sub-processor, and Userpilot cannot see or delete data held by that provider. Check the tool’s data settings, including its retention and model-training settings, before connecting it.
4. Lia, the Userpilot AI Assistant
4.1 What Lia does
Lia runs only when a signed-in Authorized User asks it something. It works only within that user’s Customer Account and only with data that the user can already see in the Web App. Lia does not collect any new data about a Customer’s end users and cannot access the internet.
Lia can read and analyze data directly. Before anything in the Customer’s Account is changed, Lia shows a preview, and the change runs only after an Authorized User approves it. Lia cannot delete data or use administrative functions such as account and security settings, team management, billing or integrations.
Lia is currently offered as a closed beta. It is enabled only when a Customer’s Administrators request access and Userpilot grants it.
4.2 What data is involved
- Requests. What the Authorized User types or asks Lia.
- Account data Lia reads to answer. Customer Data and other data in the Customer’s Account that the user’s role allows them to see. Lia fetches it at the time of the request.
- Lia’s answers and the changes the user approves.
- Conversation history. The user’s conversations with Lia, so they can return to them. Conversation history is Customer Data.
- Related account context. Details Lia keeps about items in the Customer’s Account, such as flows, segments and reports, so it can give consistent answers. It does not include personal data about the Customer’s end users.
- Audit records. A record of each Lia run: the request, the steps Lia took, any actions, and the output.
4.3 How the data is used
Userpilot uses this data only to answer requests, prepare the changes the user asks for, show conversation history, protect the service (for example with rate limits and security monitoring), and find and fix errors.
4.4 Who receives the data
| Recipient | What they receive | Why |
|---|---|---|
| Amazon Web Services, including Amazon Bedrock | The data Lia handles, including requests and the account data sent to the AI model | To host Userpilot and run the AI model. Lia uses AI models from third-party developers (such as Anthropic) through Amazon Bedrock. Requests and answers are not stored by the model service, and the developers of the models do not receive them. |
| Authorized Userpilot staff | What a support, security or quality case needs | To help the Customer and keep Lia working |
| Others required by law, or in a merger or acquisition | As described in the Userpilot Privacy Policy | Legal obligations |
4.5 How long the data is kept
| Data | Kept for |
|---|---|
| Requests and answers, at the AI model | Not stored. The model processes them only to produce the answer |
| Conversation history, related account context and audit records | The same retention period that applies to the Customer’s Account data. There is no separate retention period for Lia |
| Other Customer Data | As set out in the DPA |
4.6 Controls
- Access on request. Lia is currently offered as a closed beta. It is enabled only when a Customer’s Administrators request access and Userpilot grants it. Userpilot decides whether to grant access, and may change, limit or end access to Lia at any time.
- Approval of every change. Nothing in the Customer’s Account changes until an Authorized User approves it.
- Roles still apply. Lia can never see or do more than the user’s Userpilot role allows.
5. The Userpilot MCP Server
5.1 What the MCP Server does
The MCP Server lets an Authorized User connect an AI tool that supports the Model Context Protocol, such as ChatGPT, Claude, Microsoft Copilot or Cursor. The tool can then read data in the Customer’s Account and make limited changes when the user asks it to, using the user’s identity and permissions.
The MCP Server is hosted by Userpilot (at mcp.userpilot.io) in the same environment as the Web App. The AI tool runs outside Userpilot and connects to the MCP Server over a secure, authorized connection. Userpilot does not run an AI model for the MCP Server and does not send data to any AI model; it only answers requests from the tool the user connected.
5.2 What data is involved
When a user connects. Userpilot keeps the user’s Userpilot account ID, the Customer’s account ID, the name of the AI tool, the permissions granted and the date they were granted. Userpilot checks the user’s name and email address at sign-in but does not store them as part of the connection.
What the AI tool sends to Userpilot. Only the details of each request: for example, which report to run, a date range, a search term, an analytics query, or the text of a survey the user asks it to draft. Userpilot does not receive the user’s conversation with the AI tool.
What Userpilot sends back to the AI tool. Only data that the user’s Userpilot role already allows them to see, and only within the permissions the user grants on the sign-in screen. There are six permissions: three to read data and three to create or update specific items. Results are limited in size.
| Permission | What the AI tool can receive or do |
|---|---|
| Read: analytics data | Flows, checklists, surveys, reports, dashboards, segments and events, with their settings and results. Survey, NPS and in-flow form answers, including written comments and the respondent’s name and email. Which users saw or completed a flow. Text of clicked buttons and links, and page addresses, captured in the Customer’s product. For reports and dashboards: the email addresses set to receive them, and the internal ID of the team member who created or last edited them. |
| Read: end-user records | End users’ names, emails, user IDs, companies, country, browser and browser language, device, operating system, app version, screen size, and first and last seen dates. Custom properties the Customer tracks about users and companies. Their sessions, activity, top pages and events, segments, and survey and NPS answers. |
| Read: session replays | Session lists, links to recordings, the pages and key events in each session, the Customer’s team notes, and the end user’s name, company, country, browser and device. Error and frustration statistics, including the affected pages. |
| Write: segments | Create and update segments. The AI tool receives the segment it saved. |
| Write: reports and dashboards | Create and update reports and dashboards. The AI tool receives the report or dashboard it saved. |
| Write: surveys | Create and update surveys and survey questions. Surveys are saved as drafts and go live only when a person publishes them in the Web App. |
With all three read permissions, the AI tool can also run analytics queries. A query can return any analytics field described above, and the result includes the query that ran. Results also include Userpilot record IDs. If a request fails, the error message can include the reason and a reference ID that helps Userpilot’s team find the failure.
The AI tool cannot read Userpilot API keys, passwords, billing details, team member lists or organization settings, and cannot delete data.
5.3 How the data is used
Userpilot uses this data only to sign the user in and keep the connection active until it is revoked, carry out the requests the AI tool makes on the user’s behalf, protect the service (for example with rate limits and security logs), and find and fix errors.
5.4 Who receives the data
| Recipient | What they receive | Why |
|---|---|---|
| The AI tool the user connects | The results of the user’s requests | To answer the user, under the AI tool provider’s own terms |
| Amazon Web Services | All data passing through the MCP Server | To host, run and protect the service |
| Authorized Userpilot staff | What a support or security case needs | To help the Customer |
| Others required by law, or in a merger or acquisition | As described in the Userpilot Privacy Policy | Legal obligations |
5.5 Controls
- Choose permissions. The user chooses which of the six permissions to grant on the sign-in screen.
- Revoke at any time in the Web App under MCP Connections, or in the AI tool’s settings. The connection stops working within 15 minutes.
- Administrators can revoke connections for other Authorized Users in the Customer’s Account.
- Roles still apply. The AI tool can never see or do more than the user’s Userpilot role allows.
6. Applies to Both AI Features
- Userpilot does not sell or share data processed through the AI Features, use it for advertising, or use it to train, fine-tune or otherwise change any AI model.
- Both AI Features are hosted in the same environment as the Customer’s Web App account, in the region where the Customer is hosted: the United States by default, or the European Union on request. Where Personal Data is transferred from the EU, the UK or Switzerland to the United States, the transfer follows the Data Privacy Framework section of the Userpilot Privacy Policy and the DPA.
- Every Lia run and every MCP request is checked against the user’s role and the Customer’s Account, and is recorded in an audit trail. Each Customer’s data is kept separate from other Customers’ data, and data is encrypted in transit and at rest.
- The AI Features are for business users aged 18 or over, as set out in the Userpilot Terms of Use.
7. Privacy Requests
- End users of a Customer’s product. If a Customer has submitted Your data to the Web App, please contact that Customer. Userpilot will help the Customer respond, as the DPA describes.
- Authorized Users and everyone else. You can exercise Your privacy rights as described in the Userpilot Privacy Policy, or by emailing [email protected].
8. Changes to This Notice
Userpilot updates this notice when the AI Features or the data they use change, and updates the “Last Updated” date at the top. Material changes follow the same notice rules as the Userpilot Privacy Policy.
9. Contact
[email protected], or Userpilot, Inc., 7200 North MoPac Expressway Suite 300, Austin, Texas 78731.
10. Appendix: Actions Available Through the MCP Server
| Group | Actions | Permission |
|---|---|---|
| Workspaces | list workspaces | none |
| Product content | list and get flows, surveys, checklists, events, properties and other items | Read: analytics data |
| Reports | run reports, run saved reports, list and get reports and dashboards | Read: analytics data |
| Users and companies | list and get users, list and get companies | Read: end-user records |
| Analytics queries | run analytics query, get analytics schema | All three read permissions |
| Create and update | segments; reports and dashboards; surveys and survey questions (surveys are saved as drafts) | The matching write permission |