Convurter
Sign in All tools

Trust

Trust starts with clear runtime boundaries.

Runtime, telemetry, API, and MCP boundaries.

Consent-gated Browser-local Read-only MCP
Runtime pathBrowser-local first

Use browser tools when the job can run locally. These tools are the default path for inspection, cleanup, formatting, metadata checks, and lightweight conversion.

Runtime pathTemporary when needed

PDF, OCR, Office, HEIC, and heavier image work may require temporary upload-backed jobs with clear limits and expiry behavior.

Runtime pathPublic lookup only

DNS, SSL, redirect, DMARC, WHOIS, and header tools inspect public records and public responses. They are not private scans or certifications.

Processing boundariesBrowser-local tools keep files and pasted text in the browser.

Browser-local tools keep files and pasted text in the browser.

Server jobs are labeled, capped, temporary, and deletable where supported.

Telemetry boundariesOptional Google analytics and advertising are consent-gated.

Optional Google analytics and advertising are consent-gated.

Product telemetry uses operational metadata only.

Account and API boundariesAccount pages use session cookies and CSRF checks.

Account pages use session cookies and CSRF checks.

API and MCP use scoped keys, credits, limits, and the same logging guardrails.

MCP boundariesThe current MCP surface is limited to read-only lookup and report tools.

The current MCP surface is limited to read-only lookup and report tools.

No uploads, billing actions, delete actions, automation, shell execution, or broad mutation.

Working practices
  • No raw content in analytics.
  • Narrow tools over broad actions.
  • Temporary artifacts for server jobs.
  • Public boundaries for files, API, and MCP.