Training
Lays the foundation: what is allowed, and why.
BeeSensible helps people apply that knowledge while they work, with the decision and a highlight right when it matters.
AI governance software
AI governance software: see which AI is in use and whether your policy is followed.
Which AI tools do your people use, and can you show that your policy is followed? Those are the questions AI governance software answers. Most vendors come from model management, data science, GRC or security. BeeSensible covers what happens in almost every organisation: the everyday use of ChatGPT, Copilot, Gemini and hundreds of other AI services. Which tools are in use, what has been decided about them, whether people know that while they work, and whether you can demonstrate it.
Prefer to try it yourself? 14 days free, no credit card.
app.beesensible.eu/insights/usage
AI tools in use
7
Newly discovered
2
The problem
You have an AI policy. Do you know what happens around it?
Most organisations have an AI policy and a tool they bought. What they lack is a view of what happens in practice: which other AI tools people use, which were never assessed, and whether the policy fits the working day.
The inventory is out of date
A list of approved tools describes the day it was written. New AI services appear daily, often as a feature inside a tool that was already in use.
The decision never reaches the employee
A policy on the intranet does not help when someone with a deadline opens a tool. The question "is this allowed?" is asked in the text field, not in the handbook.
Nobody can show it works
A regulator, auditor or works council does not ask for the policy. They ask what has happened since. Without figures, the answer is an assumption.
Features
Which features AI governance software needs, and what BeeSensible covers.
The category is broad. These are the features that matter for governing everyday AI use, and for each one, whether BeeSensible covers it fully, partly or not at all.
| Feature | What it does | BeeSensible |
|---|---|---|
| Discover AI tools | See which AI services are opened in the organisation, including the ones nobody requested. | Yes Through the browser extension. Only the tool's domain, counted anonymously. |
| See AI use | How many people use AI, how often, with which tools and for what. | Yes At organisation level, with no user ID in the figures. |
| Risk information per tool | What a tool does with input, where it processes data and which incidents are known. | Yes A catalogue of over 1,000 tools, scored out of 100 across six weighted dimensions. Meant as advice. |
| Record policy | A decision per tool: allowed, limited use, not allowed or no decision yet. | Yes Every tool starts at "no decision yet". BeeSensible never chooses for you. |
| Inform employees | Show the decision when someone opens a tool, with the allowed alternative first. | Yes A notice in the browser. People can still continue, unless the organisation has chosen otherwise. |
| Make sensitive data visible | Highlight names, national ID numbers, IBANs and other sensitive data as someone types. | Yes In the apps you already work in. Text is processed in memory and discarded at once. |
| Aggregated reporting | Three topics with two figures each per period, mapped to provisions of the GDPR, NIS2 and the AI Act. For each provision, it shows what the figures do not cover. | Yes The Accountability screen, switched on per organisation. |
| Model validation and bias testing | Assess whether a model you built or bought is fair and accurate. | No A different category, for organisations that build models or deploy high-risk systems. |
| Block or enforce | Make a tool technically inaccessible or rewrite text automatically. | Partly BeeSensible does not block on its own: the organisation chooses whether people can still go ahead with a tool that is not allowed, and how warnings and masking are set up. |
What it does not do
What BeeSensible does not do, so you know up front.
This is where BeeSensible stops and other software begins.
- No model validation, bias testing or conformity assessment of high-risk systems. That is a different category of software.
- No decisions on your behalf. A risk score is advice; which tools are allowed is up to the organisation.
- No per-employee view and no storage of typed text. Dashboards show counts, never who or what someone wrote.
The approach
From seeing what happens to showing that your policy works.
See, decide, help, substantiate: four steps that follow each other and then start again. Jump straight from seeing to evidence and you skip the employee.
1 See
Which AI is running
Every AI tool people open comes into view, counted anonymously, with a risk assessment attached.
2 Decide
A decision per tool
Allowed, limited use on a condition you write yourself, not allowed, or deliberately no decision yet. The organisation chooses.
3 Help
The decision, when someone opens the tool
Anyone who opens a tool the organisation has decided on sees that decision, with the alternative first. Sensitive data is highlighted as they type.
4 Substantiate
What happened next
The share of AI use through allowed tools and how often a notice was followed. Accountability maps those figures to the law for each period, and says what they do not show.
and again How the cycle works
Why this approach
How this fits with training, DLP and blocking.
Each of the three has a place. BeeSensible adds what they do not show: which AI is in use, and whether your policy is followed.
Classic DLP
Looks at files and network traffic, mostly after the fact.
Often sees a paste into an AI tool only once the text has been sent.
Blocking AI
Shuts off known tools.
Without a workable alternative, people find another route and you lose sight of it. A notice that points to the allowed alternative keeps the work moving and keeps it in sight.
Frequently asked questions
What people ask before they choose.
What is AI governance software?
Software that helps keep AI use responsible, and lets you show that it is. Which AI systems and services are in use, what has been decided about them, how that decision reaches people and whether it is followed. Some vendors focus on models and high-risk systems. BeeSensible focuses on the everyday use of existing AI services by employees.
Is this the same as an AI register?
An AI register is one part of it. In BeeSensible every allowed tool gets a register entry with use cases, the people responsible, documents and a review date. The Measured tab shows what BeeSensible sees in the organisation alongside that entry, so the register also shows what happened after the decision.
Does BeeSensible track individual employees?
No. The figures on AI use reach the servers without a user ID. An administrator sees that three people use AI daily, never who. Typed text is processed in memory and discarded at once.
Does it work with Microsoft Copilot?
Yes. Sensitive data is highlighted in Copilot, and Copilot is one of the tools you record a decision for. Many organisations use BeeSensible to see which other AI tools are in use besides Copilot.
Does it help with the AI Act and the GDPR?
It helps you with both. Accountability maps six figures to provisions of the GDPR, NIS2 and the AI Act, and shows, for each provision, what the figures do not cover. A missing figure is never shown as a zero. It does not certify compliance and does not replace a DPIA or a legal assessment.
Further reading
The next questions, answered in depth.
See which AI tools are in use, within a day.
Every module is included. Installing takes a few minutes per workstation, and employees keep working as usual.
14 days free, no credit card. Rolled out across your organisation within an hour.
