Privacy Policy

Scope

This policy explains how Mucers handles data used in advertising operations, including Google Ads API data, OAuth authorization status, Google Ads report data, Amazon Attribution data, Amazon product data, and operator review artifacts.

Data we process

• Google Ads customer identifiers, account names, campaign metadata, keyword planning data, and report rows that an authorized user permits us to access.
• OAuth authorization state and non-secret configuration needed to connect an authorized Google Ads account.
• Amazon Attribution tags, product identifiers, ASIN-level operating data, keyword imports, and manual review decisions.
• Audit records, readiness checks, route confirmations, validation results, and operator notes used to document safety gates.

Credential handling

Developer tokens, OAuth client secrets, refresh tokens, access tokens, and other sensitive credentials are not displayed in the frontend, exported CSV files, public pages, or review artifacts. Production credentials must be stored in a secure secret store or equivalent protected runtime configuration.

How data is used

Mucers uses authorized data to prepare keyword planning, read-only reporting, attribution analysis, profit review, validate-only request packages, remediation queues, and manual operator decisions. Mucers does not sell Google Ads data or use it for unrelated profiling.

Retention and deletion

Operational artifacts are retained only as long as needed for account operations, auditability, troubleshooting, or legal obligations. Authorized users may request deletion of stored operational data or revocation of OAuth access by contacting support.

Security

Mucers separates public website pages from operator console workflows. Raw secrets are redacted from artifacts and logs. Account-changing workflows remain subject to manual approval and safety gates.

Contact

For privacy, API access, or data deletion requests, contact vip@mucers.com.