Security answers for large companies
What a security team asks, answered. Only what the product does today, read on 22 November 2026. What is not there yet is said as “not yet”.
AccessWhat AI may doConnections and MCPDataLog and resiliencePapers
Access
- Single sign-on
- Yes, OpenID Connect: Microsoft Entra ID, Okta, Google Workspace, Ping, OneLogin, JumpCloud, Keycloak, Auth0. You can require it for every person of a domain; a session that came another way then ends at its next request. SAML 2.0: not yet.
- Whose domain
- A DNS TXT record proves a mail domain. A domain belongs to one company, and it is checked again every day.
- People added and removed by your identity system
- Yes, SCIM 2.0 for people and groups. A removal ends the person’s sessions, membership, one-time links and the AI accounts they linked in the same moment. A role an admin set by hand is not overwritten.
- Second factor
- Yours: with your company’s sign-in required, your own policy decides. Without it a person signs in with a one-time link to their mailbox. A code app in Wanna itself: not yet.
- Session length and networks
- You set how long a session lives, how long it may stand idle, and from which networks people come.
- Roles
- Admin, Security, Billing, Manager, Member, Viewer, Guest, and your own from twelve rights. A role holds in a unit and under it. Nobody gives a right they do not have.
- Delegated administration
- A manager or admin of a unit runs the people of that unit and what is under it, and nothing about the whole company.
- Guests and contractors
- One unit, an end date, no people and no mail of the company.
- Your own staff’s access
- A small operations team runs the servers and can technically reach the database. We read a company’s data to do what it asked us or to keep the service running, never to look. A button with which you approve each look: not yet.
What AI may do
- Never more than the person
- A person’s chat is given what their role sees: money, other people’s mail and settings do not reach the model in a Member’s chat, and its tools refuse what the role does not allow.
- Whose chat
- A person’s chat is theirs. No admin reads it, and what they write in it does not become the company’s knowledge.
- Approval before anything goes outside
- You can put every unit in Suggest: every letter, post and reply waits for a person with that right, and nobody can switch it off.
- Text from outside
- Letters, pages and files are data, not orders. Invisible characters are cut out, what looks like an order is written down, and letters and events of that turn wait for a person’s yes. Measured results of injection tests: not published yet.
- What is never given to AI
- Your own words, as a rule over every task of every unit.
- Stop
- One press stops a company’s Wanna; the next step outside is checked against it before it happens.
- People decisions
- Hiring, pay, discipline and dismissal are only prepared. A named person decides.
- Do people know it is an AI
- Each person is told on their first visit.
- Training on your data
- Never. The AI services that read a task are named in the privacy policy; Wanna keeps no copy of what they read beyond the task itself.
Connections and MCP
- Who connects services
- Only admins and Security, or managers too, or everybody who works here: your choice. A refused person can ask an admin from the same page.
- Which services
- Any, only a list, or any but a list.
- MCP servers
- Never, admins only, or anybody who may connect. An address is https on the open internet, checked again at every connection, and no redirect is followed.
- What a service may do
- A connected service is only read; a tool that changes something is blocked. Each reading tool: Always allow, Needs approval or Blocked, and over them your own ceiling.
- Keys
- Sealed with AES-256-GCM with a key of your company alone, never shown again and never given to the AI. Wiped when you disconnect.
- Mail and calendar of everybody
- Connected once by your admin. Read: who, with whom, when, the subject and the provider’s short line; never the text of a letter. Leave out HR, legal or the leadership by group, unit, label or folder.
- Your own AI tools into Wanna
- A key with a list of tools, a budget of calls and an end date; revoked at the very next call.
Data
- Where
- Germany, the European Union: the data, the files and the copies. AI services may work outside the EU, including the United States.
- Another country
- A separate installation in a country you name can be a part of your contract. Not offered by a button.
- One company from another
- A signed-in request runs under row policies of the database, for your company’s units alone. A table without a decision fails our build.
- Encryption
- On the way: TLS. Copies and keys of your services: encrypted. Your own master key: not yet.
- How long
- Your rule for letters and meetings (30 to 365 days, or as long as you keep Wanna). The rest until you delete it.
- One person’s data
- Exported in one file or erased, from the console, with a line in the audit log.
- When you leave
- You download everything, then delete. Copies end by themselves within 90 days.
- Copies
- Every 6 hours, encrypted, separate from the servers; for 30 days nobody can delete one, us included; every week one is restored in full to check it. The live times are in your console.
Log and resilience
- Audit log
- Sign-ins and refusals, people, roles, connections, rules, budgets, approvals, exports. Append only, kept 12 months at least, each line chained to the one before; download it or stream it over https with a signature.
- How much can be lost, how fast it is back
- At most 6 hours of work between copies. The time of the last test restore is shown in your console.
- Uptime
- A number and its credits are a part of your contract. None is claimed here.
- Incidents
- Your privacy contact is told without undue delay; the hours and the contents are in the contract.
- Checks before a release
- Every change passes the automatic checks of the whole product before it goes live.
Papers
- Data processing agreement
- Signed before any of your data is connected: yours or ours. The companies that handle data are in the privacy policy, and a change is told in advance under the agreement.
- SOC 2, ISO 27001
- Not yet. No certificate and no audit report is claimed.
- Penetration test by an outside firm
- Not yet.
- EU AI Act
- Wanna is the provider, you are the deployer. Ranking candidates and employees and credit decisions are not done by Wanna on its own.
- Who makes Wanna
- TITLEMAN Inc., a Delaware corporation, 285 Fulton Street, 85th Floor, New York, NY 10006.
A question that is not here
Send your questionnaire with your request; a person answers it in your own form.
Security answers · Countries and personal data · How a company starts · Privacy · Terms