submit-work-feedback

Data masking in internal feedback involves hiding sensitive personal details like names and contact information before submission. It uses a local rules engine to apply defined masking policies directly on the client device, preventing personal data leakage in both anonymous and non-anonymous workflows.

You need to apply data masking to an intranet feedback form when submissions contain sensitive coworker identifiers. This is required for both anonymous and non-anonymous internal feedback workflows to ensure policy compliance and prevent personal data leakage within internal systems.

Yes, feedback masking works for both anonymous and non-anonymous internal system workflows. It processes submissions through a local rules engine that enforces defined masking rules, ensuring privacy and policy compliance regardless of the submission type.

Client-side masking rules operate locally on the device using a defined rules engine, meaning processing happens before data reaches internal systems. This approach prevents leakage but relies entirely on the local environment to enforce compliance policies during the feedback workflow.