What counts as ToS‑safe automation?

A practical checklist for building automations that won’t break platform rules.

Design automations that partner platforms will love, not fight. Use official APIs and events; avoid anything behind auth screens or brittle scraping. Prefer webhooks for reliability, document flows for auditability, and ensure users can opt‑out where applicable.

• Use official webhook events (e.g., Stripe charge.dispute.created).
• Keep processing inside your accounts (Zapier/Make + Drive/Docs).
• Avoid scraping logged‑in pages; prefer public APIs or exports.
• Keep logs so you can explain the flow when support asks.

This is the philosophy we bake into ChargeGuard Kit.