How the AI plugin works inside your current tools
How the AI plugin builds an answer
A person completes a behavioral assessment, rated 27 out of 30 in review by the British Psychological Society. That profile is the only thing the AI plugin draws on.
Our platform builds the answer from that person's profile and hands it to your assistant. Your assistant delivers it, so the phrasing can read a little differently from one to another. What it is built from does not change.
The plugin returns only what that person could see by logging into the platform in a browser. There is no privileged back channel and nothing extra for a prompt to reach.
Works with the assistant you already use
Who sees what
Three levels of access, set by us rather than by the assistant. Each one is enforced on our side, so what a person can ask about is the same in the plugin as it is in the platform.
Can see: their own profile, in full
Can ask: anything about how they work, and what their manager is able to see about them
Cannot see: anyone else
Can see: their own profile, and how each person in their team works
Can ask: how to approach a conversation, or how two people in the team work together
Cannot see: any one person's full profile, and nobody outside their team
Can see: their own profile, and patterns across groups such as a department, a level or a function
Can ask: where capability sits and where the gaps are
Cannot see: a named person's profile through the plugin
Four measures, not one verdict
Someone with no completed assessment
Anyone beyond your access
A group that is too small
Who is the best of these people
The answers your security team asks for
We do not train models on your people
Your data is not used to train any AI model of ours. What your assistant provider does with what passes through it is set by the agreement you already hold with them, the same as any other document your people use.
Inside the certifications you already ask for
We hold ISO 27001 and SOC 2, the two independent security standards a risk team asks about. The plugin sits inside that scope rather than beside it, so it is not a separate exception for anyone to approve.
Nobody else in the chain
No third party handles this data on our side. Once an answer reaches your assistant it is handled by the assistant you have already approved, under the agreement you already hold with them.
Encrypted in both directions
The data is unreadable to anyone intercepting it while it moves between systems, and unreadable while it is stored.
Where your data goes
Profile insight passes into your assistant so it can appear in the conversation, and nowhere else. It is read to answer a question, and that is the end of it.
Frequently asked questions
If it is not here, ask us. You will get a fast answer from an expert, not a form reply.
The leading AI assistants all work with it, because the plugin is built on MCP and they support that standard. ChatGPT, Copilot and Claude are the three we have tested.
Access changes at the same moment it changes in the platform, because both read the same permission list from your HR system. A leaver loses access to the plugin at the instant they lose access to everything else. Nobody maintains a second list.
Not today. What every employee can do is see their own profile in full, and ask the plugin directly what their manager is able to see about them.
It is built for development conversations, and we will not claim the system can police how a question is asked: we never receive the prompt, so we cannot see the context it sits in.
What is settled: it does not rank people, it does not open up an individual profile beyond someone's access, and a profile describes how someone works rather than how well.
Put it in front of your security team
Tell us what your reviewers need and we will bring the right people to the call, including the documents that do not sit on a web page.