Control over AI
Documentation
Security

Logging

What technical information BeeSensible logs, what never ends up in logs, and which notifications circulate internally.

BeeSensible logs technical information to keep the service reliable and secure.

What is logged

For each request to the API, the standard request logger writes one line with:

  • the client's IP address;
  • the method and the requested path, with any parameters in the address;
  • the status code;
  • the duration of the request.

Request contents are not logged. Typed text, documents, prompts, and detection results do not end up in application logs, monitoring, or tracing. Scheduled jobs, such as the daily cleanup, log only counts, never the contents of rows.

Internal notifications

Our service sends two kinds of notifications to our internal Slack channel: notices about how the service is running, with counts and technical status only, and a notice when a new organisation is created, with its name, email domain, number of seats, and plan. Messages from the contact form on the website arrive there too. The extension and the desktop app send nothing to Slack themselves, and no data about individual users of customers ever goes there.

Retention

The retention period for technical logs is stated in the privacy policy.

Reports

The dashboard shows figures in aggregate and is intended for overview, configuration, and risk management. It is not a log of what people type; that content exists nowhere.

Portrait of Rens Timmermans of BeeSensible

Would you rather someone showed you?

Rens, BeeSensible

I am happy to give you a twenty-minute tour. Leave your details and I will find a moment that suits you. Calling or emailing works just as well.

Rather talk to someone first? Book a call.

Want a live demo, or a quote for 100+ users? Leave your details and we'll be in touch within one business day.