Skip to main content
Pylva does not need customer prompts, model completions, raw tool arguments, or user messages to calculate cost. For the deeper security, key-handling, and Cloud versus self-hosting boundary, see Security And Data Handling. Customer portal visibility inherits this same boundary. Share cost-shaped usage facts with end-users, not prompts, completions, raw messages, or raw tool arguments. See Customer Portal.

​
Do not send

Do not send these values in customer_id, step_name, metric names, or metadata:
  • Prompts.
  • Completions.
  • Emails.
  • Phone numbers.
  • Raw names when an opaque ID is available.
  • Chat transcripts.
  • Tool arguments that contain user content.

​
Send instead

Use stable, opaque identifiers:

​
API keys

SDK-facing endpoints authenticate with X-Pylva-Key. Store API keys in your runtime secret store and rotate them if they are exposed. See Security And Data Handling for key handling details.

​
Logs and support

When sharing diagnostics with support, include:
  • Request IDs.
  • Batch IDs.
  • SDK version.
  • Timestamp.
  • Non-sensitive customer ID.
Do not include API keys, authorization headers, request bodies, prompts, completions, or raw messages.