What we store, and what we don't
What BeeSensible keeps for analytics and administration, and what content is not stored.
Analytics
Detection activity across your organisation.
BeeSensible processes text to detect sensitive data. The full prompt, email, or chat message is not stored as an analytics record.
What is stored
For analytics and recognizing duplicate detections, BeeSensible stores detection metadata such as:
- organization;
- user;
- type of sensitive data;
- detection level;
- app or website;
- detection time;
- a non-readable check value for the detected value.
That check value is used to recognize repeated detections without storing the original value as plain text.
BeeSensible also stores account and organization data needed for login, roles, seats, subscriptions, email preferences, and administration.
What is not stored
BeeSensible does not store the full content of prompts, emails, chats, or documents as analytics records.
The extension does not request access to browser history or clipboard contents. It only uses permissions needed to run on supported pages, store settings, and sign the user in.
Retention
Retention periods for technical logs and detection events are covered in the legal documentation. For formal retention periods, the data processing agreement, or a DPIA, that documentation is authoritative.