Scoped API keys
Telemetry documents read, write, and read-and-write scopes. Use separate keys for ingestion, querying, and automation when responsibilities differ.
Queryable event storage
Incoming JSON is checked for schema compatibility, buffered for fresh queries, and written as compact Parquet history used by the DataFusion query layer.
Retention and deletion controls
Table APIs expose configurable retention, row deletion, and table deletion. Treat deletion as irreversible and restrict write-capable credentials.
Payment-data boundary
Telemetry's privacy policy states that payment card details are provided directly to the payment processor and are not stored or collected by Telemetry.
Instrumentation boundary
Data to keep out by default
- Passwords, API keys, auth headers, cookies, and session tokens
- Private keys, wallet mnemonics, signatures, and credentials
- Raw prompts, completions, webhook bodies, and job payloads unless specifically reviewed
- Payment-card data and unnecessary personal or customer content
Safer event design
Prefer categories and identifiers
- Record error_type and failed_step instead of a raw sensitive payload
- Use route templates rather than URLs containing identifiers
- Store accepted, saved, retried, or discarded outcomes without raw AI content
- Keep environments, services, owners, and stable event names consistent
Public documentation and policy
This page is a product overview, not a contractual security addendum. The privacy policy and terms govern their respective subjects; contact Telemetry for current answers to requirements not covered publicly.