Privacy Policy

Last updated August 2026

PulseMeter ("we") helps teams monitor their LLM API spend. This policy explains what we collect and how we use it. Our guiding principle is minimalism: we collect the least data needed to alert you about spend.

Information we collect

  • Account data: your email and authentication identifiers.
  • Provider usage and cost data: usage and cost figures (token counts and dollar amounts by day and model) retrieved from the read-only keys you connect.
  • Team member usage metrics: for enterprise seat providers (such as Claude Enterprise), the provider's analytics API reports usage and cost per person — so we store your team members' work email addresses alongside their token and dollar totals. Metrics only: never the content of anyone's conversations.
  • Configuration: budgets, alert rules, and notification channels you set up.
  • Product analytics: basic, privacy-respecting usage of the app to improve it.

What we do not collect

We never receive your prompts, completions, conversation content, or your customers' data. The provider keys you connect are scoped to read usage and cost data only.

How we use data

  • To calculate spend, detect anomalies, and send you alerts.
  • To provide, secure, and improve the service.
  • To communicate about your account and billing.

Storage and security

Provider keys are encrypted at rest with AES-256-GCM. See our security page for details. We use reputable subprocessors for hosting, database, payments, and email delivery.

Data retention and deletion

Disconnecting a provider hard-deletes its stored key. Closing your account removes your workspace data. You can request export or deletion at any time.

Your rights

Depending on your location you may have rights to access, correct, or delete your data. Contact support@pulsemeter.ai.

This document is a starting template and not legal advice. Have counsel review it before launch.