Your data,your rules.
Team reads across your whole release: files, messages, money, plans. That only works if it stays private, permissioned and yours. Here is how we make sure it does.
Your organisation · sealed
- Masters
- Threads
- Budgets
- Plans
- Contacts
Where's the final master?
v10, approved by Maya on Tuesday.
→Answers, only to you- ✕Model training
- ✕Other customers
- ✕Anyone else
Your release is neveranyone's training data.
TeamMate reads your release to help you, and only you. Answering a question means sending it to a model provider (Anthropic for reasoning, OpenAI for search embeddings) and neither trains on data sent through their APIs. Nothing is pooled with other customers, and nothing is sold.
- ✓
Works for you only.
Your masters, threads and numbers answer your questions, nothing more.
- ✕
Never trains a model.
Not ours, and not our providers'. Both exclude API data from training under their commercial terms.
- ✕
Never shared across customers.
Your data is isolated to your organisation.
- ✓
Gone on your say-so.
Disconnect or delete and it is removed from Team.
Protection built in, not bolted on.
The controls underneath every connection, so Team only ever sees what you allow, and you can prove what it did.
Encrypted in transit and at rest
Your data is encrypted in transit and at rest. Credentials for your connected tools live in a dedicated secrets vault, never in plain text.
Permissioned and revocable
You decide what each connection can see, and you can cut any of them off in one click. Team only ever reads the scopes you have granted.
Granular access
Role-based controls decide who on your team sees what. The right people get the whole picture, everyone else gets exactly their slice.
A full audit trail
Every action Team takes is logged, so you can always see what changed, when, and where the answer came from.
Enterprise controls, when you need them.
Running at scale means stricter requirements. Team is built to meet them, with the controls and paperwork procurement teams expect.
Explore Enterprise →- SSO and SAML sign-on
- Role-based access control
- SCIM provisioning
- DPA on request
- Data residency options
- Exportable audit logs
FAQs
01Does TeamMate train on my data?
No. TeamMate uses your connected data to answer your questions and do work for your release. We do not train models on it, and neither do our providers. Your data is never pooled with other customers.
02Who on my team can see my data?
Only the people you invite, at the access level you set. Role-based controls let you give the right people the whole picture while limiting everyone else to their slice.
03Can I disconnect a tool or delete my data?
Any time. Every connection is revocable in one click, and when you disconnect a tool or delete your data, it is removed from Team. Everything you build stays portable and yours to keep.
04How are my connected accounts protected?
Connectors are made through each provider's official, permissioned access, and the credentials are held in a dedicated secrets vault. Team only ever reads the scopes you have granted.
05Where is my data stored?
Your data is encrypted in transit and at rest with a reputable cloud provider. Enterprise plans can discuss data residency options. Request our security documentation for the full detail.
