What happens to your organisation's data, and where
This page explains how BeeSensible handles data, where processing runs and what we put in writing. For signed agreements, email trust@beesensible.eu.
Read next
Architecture & data flow
How the extension, the desktop app, the API, the dashboard and the detection service work together.
Privacy
Roles and responsibilities, the data BeeSensible keeps and how many users it takes before figures appear.
Security
Encryption, sign-in, roles and logging.
Compliance & vendors
What BeeSensible contributes for each regulation, the services we use and how to request documents.
What happens to typed text
The application, database and storage run on Scaleway in Amsterdam; the models on a dedicated server at Hetzner in Germany. European companies, not a European region of an American cloud: Scaleway is 96% owned by the French Iliad group, Hetzner is German. Both are ISO 27001 certified.
Typed text is checked in working memory and then discarded. It is never written to disk and never used to train models.
Reporting shows patterns by period, app, category and level. The behavioural data contains no user ID, and the dashboard has no per-employee view.
Built for security and data leak prevention, not to evaluate or discipline staff.
Logs record the IP address, path, status and duration of each request. They contain no request bodies and no typed text.
Request the data processing agreement (DPA) and the product DPIA from trust@beesensible.eu. The product DPIA includes a template for a short legitimate-interest assessment.
Questions about procurement, privacy or security
Email trust@beesensible.eu for the DPA, the product DPIA, the subprocessor list and privacy or security questions. For anything else, use the contact page. We reply as soon as we can, in Dutch or English.
