Mercator Privacy

Mercator is operated by Tempo Labs and is covered by the Tempo privacy policy. That policy describes the information Tempo may collect, why it is processed, when it may be disclosed, retention, security, international transfers, and the privacy rights available in different jurisdictions. This page is a product-specific summary for Mercator and does not replace the governing policy. Privacy questions and rights requests can be sent to support@tempo.xyz.

The public website may receive ordinary request information such as IP address, browser and device characteristics, requested pages, timestamps, referring pages, and operational error data. Production pages use Google Tag and Ahrefs integrations, and Mercator sends bounded product analytics to PostHog. CLI setup telemetry is anonymous and limited to finite fields such as CLI version, platform, architecture, installation channel, interaction mode, selected client identifiers, bounded outcomes, and elapsed time. Set MERCATOR_TELEMETRY=off or DO_NOT_TRACK=1 to disable CLI telemetry; it is also disabled in CI and for custom MCP endpoints.

Using Account or paid execution may involve a public wallet address, signed authorization limits, balances, payment amounts, and blockchain transaction data. Blockchain records are public and cannot be deleted by Mercator. Mercator does not ask agents for private keys and does not expose hosted access-key private material through MCP. Provider calls receive only the selected endpoint’s schema-validated input, explicitly referenced dependency output, a provider-scoped idempotency key, and the credential required for that purchase—not the full workflow or wallet credentials. Do not submit secrets or personal data unless the selected external service explicitly requires them and you understand that service’s separate privacy terms.