PolarBanner

Other

Privacy Policy

Understand what data visual automation workflows may process and how teams should handle account, asset, and render data.

View Pricing

Privacy Policy workflow

Privacy Policy is set up for teams that need repeatable, template-driven output instead of one-off manual design work.

  • ✓Connect privacy policy to uploaded assets, approved templates, and API-safe render jobs.
  • ✓Keep all remote image dependencies blocked so production renders use controlled assets only.
  • ✓Use idempotency keys when the same request can be retried by an automation tool.

What this page covers

Understand what data visual automation workflows may process and how teams should handle account, asset, and render data.

  • ✓Avoid sending secrets or private customer data inside template text.
  • ✓Use uploaded assets intentionally and remove anything no longer needed.
  • ✓Keep API keys private and rotate credentials when access changes.

Production checklist

Before using this workflow in a campaign, validate the template, expected dimensions, asset ownership, and output access path.

  • ✓Render the same payload three times and compare output hashes for deterministic behavior.
  • ✓Confirm local fonts are present in the approved whitelist before launch.
  • ✓Monitor completed and failed jobs from the logs page during rollout.