snowflake-create-privacy-policy

SkillDatabases & data

Consult Snowflake CREATE PRIVACY POLICY parameter reference before generating any CREATE PRIVACY POLICY DDL.

Available today. Use it from your connected AI after setup.

No other account needed.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the snowflake-create-privacy-policy skill

What this skill tells your AI

The instructions your AI receives, as published by gyrus-dev/frosty in skills/snowflake-create-privacy-policy/SKILL.md and read by ahel’s review.

Before writing a CREATE PRIVACY POLICY statement:

Read references/parameters.md to review all available parameters and their defaults.
For each parameter, decide whether the user's request implies a non-default value.
Include only the parameters that differ from the default or that the user explicitly requested — do not bloat the DDL with unnecessary clauses.
Never use CREATE OR REPLACE — always use CREATE PRIVACY POLICY IF NOT EXISTS.
The policy body must call either NO_PRIVACY_POLICY() (unrestricted access) or PRIVACY_BUDGET(BUDGET_NAME => '...' [, ...]) (differential privacy budget).
When using a CASE expression in the body, always include an ELSE clause — every role or user must receive either a privacy budget or unrestricted access; omitting ELSE causes a compilation error.
Use context functions such as CURRENT_ROLE() or INVOKER_ROLE() to conditionally apply budgets per role.
For cross-account scenarios, namespace BUDGET_NAME with CURRENT_ACCOUNT() to avoid budget name collisions.
Only override BUDGET_LIMIT, MAX_BUDGET_PER_AGGREGATE, or BUDGET_WINDOW when the user specifies non-default privacy constraints. Requires Enterprise Edition or higher.

Advanced