Skip to main content

Smart Privacy and employee anonymity

Why this mechanism

In 2026, the Beamy platform significantly expanded your analytical capabilities: multi-axis crossings from the scope, new charts and analysis metrics in the Dimension and Product pages, and open-ended analysis through Ask Beamy.

This new level of granularity called for a parallel strengthening of our safeguards.

Protecting personal data is not optional at Beamy. It is a founding principle, on the same footing as our ISO 27001 and SOC 2 Type II certifications. We therefore anticipated the need and deployed a mechanism we call Smart Privacy.

The principle

Smart Privacy adjusts the level of detail displayed in real time, so that no analysis can ever cover a group of users too small to remain anonymous.

The applicable threshold is based on the organizational mapping you build together with our teams.

Where does the mechanism apply?

Smart Privacy operates at three levels across your platforms:

1. When building a scope. For clients with a matrix-type organizational mapping, when you combine several domain axes, the platform assesses the headcount in real time. If the combination falls below the acceptable threshold defined with your Beamy contact, you are notified by an explicit message. You then need to broaden the analysis perimeter in order to access the data.

2. In the People Dimension. Rows corresponding to domains below the threshold are not displayed. A dedicated note at the top of the page lets you see the exact list of domains whose data has been hidden.

3. In charts broken down by domain. Some charts in the Product, Tech and People pages are split by domain (for example "Breakdown by dimension" in the Tech pages, or "Usage distribution by domain" across all pages). On these charts, Smart Privacy hides non-compliant entries and displays a note indicating that some data is protected.

A frequently asked question

"My mapping guarantees a minimum headcount per group, but a filter returns a lower figure. Is this normal?"

Yes, and this is precisely what protects anonymity. Smart Privacy relies on the declared mapping, not on observed activity. If a domain contains 7 employees and only 3 of them use a given application, you see "3 active users" without any way of determining which 3 of the 7 they are.

Active headcount fluctuates naturally; the reference group, however, remains stable and anonymous.

What this changes in practice

In the vast majority of cases: nothing noticeable.

The domains concerned are by nature the smallest ones. They are numerous, but account for very little of the actual population. Your portfolio analyses, entity comparisons and adoption tracking remain unchanged.

Going further

If you would like maximum assurance, your Beamy contact can support you in reviewing your organizational mapping to ensure a sufficient headcount in each group. Several approaches are possible depending on your organization.

For any question about your specific configuration, please contact your Beamy contact.

Did this answer your question?