You have an AI policy, a record of processing, and a training behind you. But when something goes wrong, you have to show the control actually works. BeeSensible highlights personal data in the text people type and gives you numbers by category and app.
Who this is for
18
apps with a highlight while you type: AI tools, email, chat, and social
0 sec.
The text you type is processed and discarded at once
Local or EU
Detection runs on-device or on EU infrastructure
Everyone knows the rules. Under a deadline someone forgets them anyway. A name, an account number, or a health detail goes into an AI prompt before anyone thinks twice. BeeSensible highlights that data while it is typed, and shows you in numbers where the risk sits. Without reading what people write.
From the field
You have an AI policy, a record of processing, and a yearly training. GDPR accountability asks for more: show that the controls actually work. A policy on a shelf does not prove that. A warning at the moment someone types, plus numbers on what happens, does.
You are writing a DPIA on the use of AI tools. The risk of accidentally sharing personal data is clear. The question is which technical control you put against it. Without something that covers the moment of input, the mitigation stays a promise for next time.
A report comes in that customer data ended up in an AI tool. To weigh up notifying the regulator, you want to know what is happening: which categories of data, through which tools, how often. You have a policy and a training, but no numbers on what actually happens at the moment of input.
The catalog scores more than 700 AI tools on data governance, jurisdiction, and vendor trust, including whether a processing agreement is available. For more than 140 free tiers there is none. When someone in your organisation opens one, you see it appear, with the DPIA-relevant facts attached. Then the organisation decides: allow it, allow it with a condition of your own, or not allow it. Anyone opening the tool afterwards sees that decision in the browser, with the approved alternative leading.
Legal staff can clean up the text before privileged details are shared.
A DPIA draft, a data subject access request, a breach register entry: open it in the Mac or Windows desktop app, and data subject names, email addresses, BSN numbers, and special category data are marked for you to remove before you share the document or paste it into AI.
Why this is hard
People know the rules. When the deadline gets close, they forget them. Knowledge is no guarantee of behaviour. A training from six months ago does not help at the moment someone types a prompt.
ChatGPT, Copilot, and similar tools are already in use, often out of your sight. Without a signal in the browser, you cannot tell which categories of personal data end up in them.
Showing that a control works calls for numbers from real use, not documents on a shelf. You do not have those numbers if you cannot see the moment of input.
You want to make risk measurable, not look over a colleague's shoulder. Works councils and staff rightly expect insight to be about patterns, not about individuals.
Across your accountability work
The same evidence gap shows up in different tasks, from the DPIA to breach response.
Accountability
Numbers that show the control is active at the moment of input, for your record of processing and internal reporting.
DPIA
A technical control to point to against the risk of accidental sharing through AI tools.
Data breaches
Insight into categories and apps that helps you weigh up a notification.
Awareness
A highlight at the moment someone types, instead of a training that does not stick.
Oversight
Aggregated patterns by category and app, with no view into individuals or text.
How BeeSensible helps
Sensitive details get a highlight while staff write. They decide what to remove, replace, or mask.
Names, account numbers, BSN numbers, and health data get a highlight in the text field, in AI tools, email, and chat.
BeeSensible complements your policy, processing agreements, and training. Runs in the browser plus a desktop app for macOS and Windows, no proxy, no change to your setup.
On a highlight the user chooses: remove, replace with a realistic alternative, or mask. The extension never changes text on its own and never blocks sending.
The dashboard shows patterns by category, app, and action. What an individual user writes is never stored and cannot be read.
For DPO, privacy officer, and leadership
BeeSensible gives you the figures accountability asks for: how many markings were adjusted before sending and how many went out anyway, what happened after a tool notice, and what share of AI use runs through approved tools. All at organisation level, never per colleague.
Total detections
12,438
Top apps
Example dashboard. Counts and types only, never content.
Data protection officer
Back up your accountability with figures per period: markings adjusted or sent anyway, by category and app, a recorded decision per AI tool, and what people did with the notice. Prove the control sits at the moment of input, not just that a policy exists on paper.
Privacy officer
The dashboard shows no text and no single people: only aggregate counts, with no per-employee drill-down anywhere. Insight into patterns, not surveillance of people.
Leadership and IT
No proxy and no new application. The extension runs in Chrome and Edge. Detection runs on-device or on EU infrastructure, all traffic encrypted in transit.
Honest answers
Straight answers to the questions people actually ask before rolling this out.
The extension analyses text in the input fields of supported tools to highlight sensitive data. On the mechanics: in on-device mode, that text never leaves the machine; otherwise it travels to a BeeSensible server inside the EU, is processed in working memory, and is discarded at once. The content is never stored and cannot be read by anyone, not even an administrator.
No, BeeSensible blocks nothing. The user sees a highlight in the text and chooses what to do: remove, replace, or mask. The user stays in control, and you get aggregate insight into patterns.
No tool makes you compliant on its own. BeeSensible helps with GDPR by covering the moment of input and backing up your accountability with numbers. Your organisation stays the controller, BeeSensible is the processor, and a processing agreement is signed.
Yes. The detection engine handles Dutch and English reliably and recognises personal data common in European organisations, such as names, account numbers, BSN numbers, dates of birth, and health data.
Limited. There is no proxy to configure. The desktop app for on-device detection and document redaction is optional. The extension runs in the browser your organisation already uses and can be rolled out centrally through your management console. You see your first detections in minutes.
Compliance
GDPR
Supports accountability under article 5(2) and article 24 and covers the moment personal data is entered.
DPIA
Delivers numbers by category and app to substantiate the risk in a DPIA. A product DPIA is available on request.
Processing agreement
Your organisation is the controller, BeeSensible is the processor. A processing agreement is signed with every customer.
EU processing
Detection runs on the user's own machine, or on ISO 27001 certified EU infrastructure (API in the Netherlands, detection in Germany).
BeeSensible runs in the browser your organisation already uses. No rollout project, and you see your first detections in minutes.
Claude