SafePorter withholds results supported by too few people and suppresses detail that could identify an individual. These protections apply to aggregate survey reporting and insights from written feedback. Group size is part of the assessment, but it is not the only way a result can expose someone.
A report about one employee is still a report about that employee when their name is missing. A result about a very small group can also reveal more than participants expected.
SafePorter uses minimum reporting thresholds and withholds results that cannot be shown safely. The question is how many people support the particular result, rather than how many employees the organization has overall.
Illustrative arithmetic, not a description of SafePorter's reporting threshold.
Suppose a total is 20 and a visible subgroup is 18. Hiding the remaining subgroup does not conceal its count: subtraction reveals two.
SafePorter's reporting protections therefore include withholding related results where they would expose a suppressed group. Hiding a cell is not enough when the rest of the report supplies the answer.
An insight about a unique role or recognizable incident may identify someone even when many people completed the survey. Free-text protection must address what the insight says as well as how many responses exist.
SafePorter aggregates written feedback and suppresses identifying specificity. An organization receives the protected insight rather than the individual comment.
Combining reporting categories can narrow a group. Comparing releases can also reveal information if a change can be attributed to one person's arrival, departure or response.
SafePorter constrains reporting combinations and publishes protected snapshots rather than exposing a live feed of individual changes. A snapshot by itself does not establish anonymity; the disclosure controls still matter.
A withheld result does not mean that nobody had the experience, that a category is empty, or that the underlying concern is unimportant. It means that the result cannot be disclosed safely in that form.
That distinction is especially important for rare experiences. Aggregate reporting cannot always preserve both detailed information about a rare event and the privacy of the person who experienced it. Keep a separate route for concerns that require individual attention.
See how written feedback is handled or read the explanation for respondents.
---
Bring the question your organization needs answered.
Request a demonstration