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 [email protected].
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
The application, database, and storage run on Scaleway in the Amsterdam region; the models on a dedicated server at Hetzner in Germany. These are European companies, not a European region of an American cloud: Scaleway is 96% owned by the French Iliad group, Hetzner is a German company. Both are ISO 27001 certified.
Typed content is processed in memory for detection and not kept afterwards; never written to disk and never used for model training.
Reporting shows patterns by period, app, category, and level. The behavioural data carries no user id and the dashboard has no per-employee view.
Intended for security and leak prevention, not for performance or disciplinary monitoring of staff.
Logs hold the address, path, status, and duration of a request. Request bodies and typed text are not in them.
Request the DPA, product DPIA, and customer DPIA template from [email protected].
Procurement, privacy, or security
Email [email protected] 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.
