Telemetry Data
Exactly what data RelayPlane collects and sends to the cloud.
Event Schema
Each request through the proxy generates one telemetry event with the following fields:
1interface TelemetryEvent {2 // Device identification3 device_id: string; // Random anonymous UUID, generated once per install45 // Request metadata6 task_type: string; // Inferred task type (e.g., "code_generation")7 model: string; // Model actually used (e.g., "claude-sonnet-4-6")8 requested_model?: string; // Original model before routing910 // Token usage11 tokens_in: number; // Input token count12 tokens_out: number; // Output token count13 cache_creation_tokens?: number; // Anthropic prompt cache creation14 cache_read_tokens?: number; // Anthropic prompt cache reads1516 // Performance17 latency_ms: number; // Request latency in milliseconds18 success: boolean; // Whether the request succeeded1920 // Cost21 cost_usd: number; // Estimated cost in USD2223 // Timing24 timestamp: string; // ISO 8601 timestamp (auto-set)25}What Is NOT Collected
RelayPlane telemetry does not collect:
- Prompt text or message content
- Response text or completions
- File paths, code, or project names
- IP addresses
- Personal identifiers (name, email, etc.)
- API keys or auth tokens
- System prompt content
Local Storage
Telemetry events are stored locally before being sent:
~/.relayplane/telemetry.jsonl— Buffered events (JSONL format)~/.relayplane/history.jsonl— Request history (10K entry limit, 7-day retention)
Cloud Sync
When cloud telemetry is enabled (authenticated users), events are sent to https://api.relayplane.com in batches. This is:
- Non-blocking — telemetry never slows down your requests
- Failure-tolerant — errors are silently swallowed
- Opt-out available — see opt-out guide
The
device_id is a random UUID generated on first install and stored locally. It cannot be used to identify you personally.