Snowflake’s native data masking lets you hide or transform data based on user roles or policies. Mercurial builds on this by making policy changes, deployments, and rollbacks near-instant. It is built for environments where data exposure cannot be tolerated and delays are costly.
Mercurial Snowflake Data Masking works at query time. When a column with masking policy is accessed, Snowflake applies the rule without changing the stored data. The underlying values remain. The view is masked. This makes it possible to preserve full fidelity for authorized analytics while shielding unauthorized eyes.
Policies define the transformation. Simple policies replace output with fixed text. Complex policies hash values or use conditional logic. Role-based execution ensures that each user sees only what is permitted. Mercurial lets teams version these policies alongside application code, pushing updates through CI/CD without manual intervention.
Speed matters. Traditional masking policy changes in Snowflake can require manual work, staging, and scheduled deployment windows. Mercurial skips that. It integrates directly with Snowflake’s policy framework, applies changes through automated pipelines, and handles rollbacks instantly if needed. That reduces risk while increasing agility.