Trust starts with being clear.
This page explains how BeeSensible processes data, where it runs, and what we put in writing. For signed agreements, email trust@beesensible.eu.
Read next
Architecture & data flow
How the extension, API, dashboard, and detection service work together.
Privacy
Roles, responsibility, and what data BeeSensible keeps.
Security
Connections, access, logging, and support channels.
Compliance & vendors
Legal documents, vendors, and supporting compliance processes.
What happens to typed text
Detection runs on the user's machine, through the desktop app, or on BeeSensible infrastructure in the EU. The application, database, and storage run on Scaleway in the Amsterdam region.
In on-device mode, typed content never leaves the machine. In the cloud, it is processed in memory for detection and not kept; never used for model training.
Reporting shows aggregate patterns by period, app, category, and level.
Intended for security and leak prevention, not for performance or disciplinary monitoring of staff.
Logging is designed so request bodies and user-typed text are not written to application logs.
Request the DPA, product DPIA, and customer DPIA template from trust@beesensible.eu.
Procurement, privacy, or security
Email trust@beesensible.eu for the DPA, product DPIA, subprocessor list, privacy questions, and security questions. For general enquiries you can also use the contact page. We reply as soon as we can in Dutch or English.