> ## Documentation Index
> Fetch the complete documentation index at: https://docs.pylva.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Pylva Privacy and PII Controls

> Send cost-shaped telemetry without prompts, completions, raw messages, personal data, API keys, or raw tool arguments.

Pylva does not need customer prompts, model completions, raw tool arguments, or user messages to calculate cost.

## 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:

```json theme={null}
{
  "customer_id": "cust_abc123",
  "step_name": "retrieve_context",
  "metric": "search_requests",
  "metric_value": 1
}
```

## 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.

## 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.