Trust and security
Agents that recommend. People who decide.
Executive data is the most sensitive data a company has. Team Nexa is designed around least access and explicit approval from the first line of code.
Team Nexa is in private preview. This page separates what is in place today from what is still planned. We would rather be precise than impressive.
How the agents are allowed to work
Read-only by default
Connectors request read access only. Write actions stay off unless you enable them for a specific agent.
You approve every action
Agents recommend. Anything that leaves Team Nexa, like a message, a ticket or a file, waits for your explicit approval.
Every number cites its source
Figures link back to the system, report and period they came from, so you can check before you act.
Never used to train models
Your data is not used to train models, ours or our model providers'.
Scoped per agent
Each agent sees only the sources its role needs. The People agent does not read your ledger unless you allow it.
Full audit log
Every question, finding, memo and approval is logged with who, what and when.
Security and compliance status
Design partners can request our data processing agreement and sub-processor list, and review any item below with the founding team before sharing data.
- In placetrue in the product today
- Availableavailable on request today
- Plannedon the roadmap, not yet available
| Item | Status |
|---|---|
| Encryption in transit and at rest | In place |
| Read-only connectors by default | In place |
| Approval required before any outbound action | In place |
| No training on customer data | In place |
| Per-agent data scopes | In place |
| Audit log of agent activity | In place |
| Data processing agreement (DPA) | Available |
| Sub-processor list | Available |
| EU data processing option | Planned |
| SSO and role-based access | Planned |
| SOC 2 Type II | Planned |
Have a security questionnaire?
Bring it to the demo. We'll walk through it with you.