Anonymisation and thresholds

Two protections, not one

Plenty of tools say feedback is anonymous and mean that a name is not displayed next to it. That is weak protection. If a team has three people and one distinctive writing style, "anonymous" is a label, not a fact.

Vizuna uses two structural protections together.

Protection one: anonymise and aggregate

Colleague input is anonymised and combined with input from others before the receiver sees anything. What reaches you is a pattern across people, never an individual answer. There is no screen anywhere in the product, for any role, that shows who said what.

Protection two: thresholds

Aggregation alone is not enough when the group is small. An aggregate of two is barely an aggregate at all.

So team-level views only appear once privacy thresholds are met. Below the threshold, the view stays locked. This protects people in small teams, and it also protects people when a team shrinks: the view does not quietly narrow down to the two people who are left.

Why this is strict on purpose

The honest answer to "why should I trust this?" is that the product is more useful when people are honest, and people are only honest when they are structurally safe. Who sees what sets out the rest, and measuring trust without surveillance explains why the constraint is a feature. Every protection above exists so that the input stays real. Weaken the privacy and the data becomes polite, and polite data helps nobody.

Read next