Problem: Netigate surveys sent via personalized/individual links carry embedded data (name, email, customer ID, etc.), which is essential for closed-loop follow-up. But some respondents want their specific response de-identified before it's stored.
Use case: Respondents need to be able to anonymise their own answers, if they choose to, even when they've received the survey via a personalized/individual link. Whether driven by internal policy, sector standards, or simple respondent trust, they should be able to opt into submitting a response with no personal data attached, without the admin having to pre-build this per survey.
Proposed solution: A native "Allow respondent to choose anonymity" setting at the survey level:
One toggle in survey settings that adds a standard, translatable question ("Would you like your response to be anonymous?") at for example the point the admin chooses (start or end of survey).
If the respondent opts in, Netigate automatically strips embedded/personal data and association from that specific response before it's stored.
Admin-configurable placement and wording, but the anonymization logic itself is handled by the platform, not custom flow-building.
Why it matters / benefit:
Removes a manual, error-prone workaround and makes anonymity-by-choice a supported, auditable feature, useful across any industry where trust, sensitive topics, or privacy expectations make respondents hesitant to answer honestly under a fully identified link.
Differentiates against the "you have to build it yourself" experience customers get today on competing platforms.
Reduces compliance risk: a built-in feature is easier to document and defend in DPIAs/security reviews than a bespoke flow.
Who's affected: Admins running individual-link surveys where response honesty depends on perceived confidentiality, e.g. employee/HR-adjacent surveys, sensitive customer feedback, whistleblowing-adjacent channels, or any programme where some respondents will only answer candidly if they can choose anonymity themselves.
