Hosted service

Privacy

Effective July 29, 2026.

Hosted trace content

Metergraph SDK 0.3 sends the scrubbed provider request and normalized model response, including assistant content and tool calls, to the hosted service by default. This applies to free and managed workspaces. Provider credentials, authorization values, cookies, API-key headers, and transport headers are removed. Request and response are each limited to 100 KiB of UTF-8 and visibly marked when truncated.

Control

Applications can disable content globally with METERGRAPH_CAPTURE_TEXT=0 or an initialization option, and can disable it for a sensitive route or trace. An explicit opt-out is honored before durable hosted ingestion. Older SDK 0.2 clients remain metadata-only by default. Historical content that was never captured cannot be reconstructed.

Access

All authenticated roles in a workspace may inspect that workspace's trace content in the dashboard. The content-bearing trace endpoint requires a same-tenant dashboard session and returns Cache-Control: no-store. Ingest keys, coding-agent MCP keys, cross-tenant sessions, list endpoints, summary endpoints, and application logs do not expose prompt or response content.

Open-source server

The public open-source server remains content-blind and strips content at ingestion even if SDK 0.3 sends it. Pointing the SDK at that server does not store prompts, completions, tool arguments, or tool results.

Account data

We process verified email, workspace membership, API-key metadata, product usage, and upgrade requests to operate and secure the service. Raw API keys are displayed once; only a one-way hash is stored.

Infrastructure

Hosted data is tenant-isolated and encrypted in the existing Metergraph AWS account. We do not sell personal information. Contact privacy@metergraph.dev for access or deletion requests.