Decided on the device. Every upload, listed.
Neo decides on the device, and user data stays local. The Neo cloud receives inventory, decision records, and the code and metadata a verdict needs, with secrets in AI tool settings redacted before upload.
- Applies to
- Neo Node and its connectors on macOS, Windows and Linux
- Trust Center
- trust.neo.ai (opens in a new tab)
What is collected, and where it goes.
Each row is one kind of data Neo Node handles: what it holds, where it is processed, what is redacted on the device before upload, how it travels, and what happens while the device is offline.
In the other direction, the device receives policy bundles, encrypted and integrity-checked, signed updates, and a named approver's answer when a policy asks for one.
| Data | What it holds | Where it is processed | Redacted on the device | How it travels | Offline |
|---|---|---|---|---|---|
| Inventory | Installed software, with extra detail for AI tools and their configuration (MCP servers, skills, plugins, permission rules, models), plus browser extensions, packages and libraries, and basic system details | Collected on the device by the inventory collector; matched against Neo's catalog in the Neo cloud | Secrets in AI tool settings, such as MCP environment variables | Outbound HTTPS from Neo Node to the Neo cloud | Kept on the device and sent when it reconnects |
| Decision records | Each policy decision: the action, the policy that matched, the outcome, and the chain from person to agent to process to action | Decided on the device by Neo Node; kept in the Neo cloud for the console and the audit trail | Secrets in AI tool settings | Outbound HTTPS from Neo Node to the Neo cloud | Queued on the device and sent when it reconnects |
| Code and metadata a verdict needs | Only what a verdict needs, such as the files and package metadata of an MCP server or skill Neo has no verdict for yet | Analyzed in the Neo cloud to reach a verdict. Private software never enters the public record | Secrets in AI tool settings | Outbound HTTPS from Neo Node to the Neo cloud | Queued on the device; the last policy keeps applying meanwhile |
| Secrets in AI tool settings | Values such as keys and tokens in MCP environment variables and other AI tool configuration | Found on the device | Always: each value is redacted before upload | Never sent as a value | Redacted on the device, online or offline |
| Neo Node health | Neo Node's version and status, and each connector's state | Reported to the Neo cloud for fleet reporting | Holds no user data | Outbound HTTPS from Neo Node to the Neo cloud | Queued on the device and sent when it reconnects |
| Agent Activity: full content | Each step of an agent session, including prompts and model reasoning | An audited admin setting, off unless an admin turns it on. While it is on, the content is kept in the Neo cloud for the console's Agent Activity; replaying a session needs admin rights and is itself audited | Secrets in AI tool settings | Outbound HTTPS from Neo Node, only while the setting is on | Queued on the device and sent when it reconnects |
-
Inventory
- What it holds
- Installed software, with extra detail for AI tools and their configuration (MCP servers, skills, plugins, permission rules, models), plus browser extensions, packages and libraries, and basic system details
- Where it is processed
- Collected on the device by the inventory collector; matched against Neo's catalog in the Neo cloud
- Redacted on the device
- Secrets in AI tool settings, such as MCP environment variables
- How it travels
- Outbound HTTPS from Neo Node to the Neo cloud
- Offline
- Kept on the device and sent when it reconnects
-
Decision records
- What it holds
- Each policy decision: the action, the policy that matched, the outcome, and the chain from person to agent to process to action
- Where it is processed
- Decided on the device by Neo Node; kept in the Neo cloud for the console and the audit trail
- Redacted on the device
- Secrets in AI tool settings
- How it travels
- Outbound HTTPS from Neo Node to the Neo cloud
- Offline
- Queued on the device and sent when it reconnects
-
Code and metadata a verdict needs
- What it holds
- Only what a verdict needs, such as the files and package metadata of an MCP server or skill Neo has no verdict for yet
- Where it is processed
- Analyzed in the Neo cloud to reach a verdict. Private software never enters the public record
- Redacted on the device
- Secrets in AI tool settings
- How it travels
- Outbound HTTPS from Neo Node to the Neo cloud
- Offline
- Queued on the device; the last policy keeps applying meanwhile
-
Secrets in AI tool settings
- What it holds
- Values such as keys and tokens in MCP environment variables and other AI tool configuration
- Where it is processed
- Found on the device
- Redacted on the device
- Always: each value is redacted before upload
- How it travels
- Never sent as a value
- Offline
- Redacted on the device, online or offline
-
Neo Node health
- What it holds
- Neo Node's version and status, and each connector's state
- Where it is processed
- Reported to the Neo cloud for fleet reporting
- Redacted on the device
- Holds no user data
- How it travels
- Outbound HTTPS from Neo Node to the Neo cloud
- Offline
- Queued on the device and sent when it reconnects
-
Agent Activity: full content
- What it holds
- Each step of an agent session, including prompts and model reasoning
- Where it is processed
- An audited admin setting, off unless an admin turns it on. While it is on, the content is kept in the Neo cloud for the console's Agent Activity; replaying a session needs admin rights and is itself audited
- Redacted on the device
- Secrets in AI tool settings
- How it travels
- Outbound HTTPS from Neo Node, only while the setting is on
- Offline
- Queued on the device and sent when it reconnects
What stays on the device.
- Secret values found in AI tool settings, such as MCP environment variables: each is redacted on the device before upload
- Prompts and model reasoning unless an admin turns on Agent Activity full content
- Traffic for inspection never routes through Neo's cloud: Neo inspects on the device, while network DLP inspects content only after shipping it off the device
Read next
-
Neo's security and compliance documentation. (opens in a new tab)
Neo's security program and compliance reports, including SOC 2 Type II.