Privacy Policy

metry_gle uses Google account sign-in for app access and Google Ads OAuth only when a user connects a Google Ads account. Google Ads data is used to discover accessible customers, run readiness checks, prepare PAUSED Performance Max actions, and display reporting snapshots.

OAuth tokens are encrypted at rest. MCP access tokens are stored only as hashes. Logs and reports must redact OAuth tokens, developer tokens, client secrets, Authorization headers, cookies, and payment details.

Users can disconnect Google Ads OAuth through the Console, revoke MCP tokens, and request tenant-scoped Google Ads data deletion. Deletion removes Google Ads connections, OAuth tokens, cached customers, jobs, logs, launch plans, approval requests, proof snapshots, Merchant readiness snapshots, operation policies, MCP tokens, and tool invocations while keeping a minimal deletion receipt.

Production high-risk writes remain disabled. Production PAUSED create beta is disabled by default and requires explicit allowlist, readiness, validation, approval, idempotency, and redacted audit evidence before any future execution.