Privacy Policy

Last updated: June 2026

Our Privacy Promise

Poly was designed with privacy as a first principle. Your API response data never leaves your machine. We never see your payloads, user data, PII, business logic, auth tokens, or API keys.

What We Collect

The Poly SDK sends only schema metadata to Poly Cloud for drift analysis:

  • Field names and data types (e.g., "name": "string")
  • Schema structure (nesting, arrays)
  • Drift type classification (rename, remove, type_change, etc.)

We never collect: actual field values, response payloads, user data, authentication credentials, or any PII.

How We Use Data

Schema metadata is used exclusively for:

  • Detecting API schema drift
  • Generating field mappings via AI
  • Improving detection accuracy

Data Storage

Schema metadata is stored in Supabase (PostgreSQL). We retain incident history for dashboard analytics. No response payloads or user data are ever stored.

Third-Party Services

We use Mistral AI for generating field mappings. Only field names and types are sent to Mistral — never values. We use Supabase for database storage.

Contact

Questions? hello@poly.dev