Privacy policy.
AgentMeter is designed to collect cost-shaped telemetry, not prompt content. This policy summarizes the public launch posture; contractual terms may add product-specific details for paid customers.
The core privacy principle is simple: application code should report usage facts needed for attribution, rules, and billing. Prompts, completions, raw user messages, emails, documents, and payment card numbers should stay in the builder's system and not be sent to AgentMeter telemetry.
Data We Collect
AgentMeter may process account details, API key metadata, billing records, support messages, and SDK telemetry such as provider, model, token counts, customer ID, step name, status, latency, and configured usage metrics.
Data We Do Not Need
Do not send prompts, completions, emails, raw user messages, payment card numbers, or sensitive personal data in telemetry metadata. The SDK and public API are built around usage facts rather than message content.
How We Use Data
We use data to provide cost attribution, rules, billing workflows, reliability, security monitoring, support, and product analytics.
SDK Telemetry
SDK telemetry is intended to include operational fields such as customer_id, step_name, provider, model, token counts, metric names, metric values, status, latency, and timestamps. Builders should use opaque customer identifiers rather than email addresses or direct personal identifiers.
Retention And Access
Access to production data is limited to operating, securing, supporting, and improving AgentMeter. Retention periods may vary by plan, workspace configuration, and legal requirements; customers can request deletion or export support by email.
Service Providers
AgentMeter may use infrastructure, payment, email, analytics, security, and support providers to operate the service. Enterprise, DPA, and subprocessor questions can be directed to the support address above.
Builder Responsibilities
Builders are responsible for choosing safe customer identifiers, configuring SDK metadata carefully, and preventing their own application code from attaching private message content to usage events.
Contact
Questions or deletion requests can be sent to support@pylva.com.