A policy is a set of rules you save together and reuse. Instead of picking the same rules one by one every time you run moderation, you select the policy — and every run or automation that uses it applies the same standard.
Why use policies
Consistency - everyone on the team applies the same checks, whether they run moderation manually or through an automation.
Reuse - the same policy works in one-time runs and in ongoing moderation.
One place to update - when your standards change, you edit the policy once. Automations that use it are restarted with the new version so future assets follow the updated standard.
How policies work
A policy has a name, an optional description, and a list of rules.
A policy covers one asset type - images or videos. If you moderate both, create a policy for each.
Rules can belong to many policies at once. For example, a Text Detection rule might appear in both your "Product images" and "Campaign assets" policies.
When a policy runs, an asset must pass all the rules in it to be approved. One clear failure rejects the asset; uncertain results send it to review.
When to create multiple policies
Create a separate policy whenever a different kind of content deserves a different standard:
By content purpose - "E-commerce product images" (white background, centered product, minimum size) versus "Social campaign images" (brand logo placement, no competitor logos).
By strictness - a strict policy for hero images, a lighter one for thumbnails.
By asset type - one policy for images, another for videos.
Ready-made policies
Depending on your plan, you may see ready-made preset policies when creating a new one. Choosing a preset copies it into your own policies, where you can rename and adjust it freely.