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

# Telemetry & Privacy

> What the KiteFrost SDKs collect, how to opt out, and your data rights.

<Warning>
  **SDK behavior corrected 2026-08-29** (verified against
  `sdk/{python,typescript}/packages/core/src/`): the current per-pack SDKs
  (`kitefrost-game-narrative`, `kitefrost-ttrpg-gm`) do **not** auto-send
  error telemetry. There is no `report_errors`/`reportErrors` config and
  nothing to opt out of - the sections below describing automatic collection
  and an opt-out mechanism described the earlier, retired unified `kitefrost`
  client, not what ships today.

  Every `KiteFrostError` (Python) / `KiteFrostApiError` (TypeScript) carries a
  server-issued `feedback_id` (`fbk_...`). The SDK never sends it anywhere
  automatically - if you want to report a specific failure, you can
  (optionally, manually) `POST` it yourself to `/v1/feedback`. See
  [SDKs overview](../sdks/overview#error-handling) for the full error model.

  **Retention/GDPR sections reviewed 2026-09-01**: the "Data Retention", "Who
  Can See Your Data", and "GDPR and Data Deletion" sections below describe
  policy for feedback data once submitted, independent of how it was
  submitted (SDK auto-collection or a manual `POST`). Confirmed against the
  backend enforcement job (`engine.workers.feedback_partition_manager`) that
  the retention periods below are accurate.
</Warning>

## What Is Collected

**Nothing, automatically.** The current SDKs make no telemetry calls on
their own. If you choose to `POST` a `feedback_id` to `/v1/feedback`
yourself after catching an error, that submission is the only telemetry
that exists - there is no separate background/fire-and-forget mechanism.

## What Is NOT Collected

The SDK does not send anything automatically - no conversation content, no
request bodies, no end-user data, no API keys, no file-system/OS metadata.
Nothing leaves your process unless you explicitly call `/v1/feedback`
yourself.

## Data Retention

Telemetry data is retained based on whether the request was authenticated:

| Signal          | Authentication               | Retention Period |
| --------------- | ---------------------------- | ---------------- |
| Error telemetry | Anonymous (no API key)       | 7 days           |
| Error telemetry | Authenticated (bearer token) | 90 days          |
| Bug reports     | Authenticated                | 18 months        |
| Quality ratings | Authenticated                | 18 months        |

After the retention period expires, data is permanently deleted. There is no archive or backup of expired telemetry data.

## Who Can See Your Data

Telemetry data is accessible to **KiteFrost internal engineering only**. It is used exclusively to:

* Identify and fix SDK bugs
* Monitor API error rates
* Improve error messages and documentation

We do **not**:

* Share telemetry data with third parties
* Use telemetry data for marketing or analytics
* Sell or license telemetry data
* Use your data to train AI models

## GDPR and Data Deletion

You have the right to request deletion of all telemetry data associated with your account.

**To request deletion**, email [privacy@kitefrost.ai](mailto:privacy@kitefrost.ai) with your account email address. We will delete all feedback records tied to your account and confirm deletion within 30 days.

After deletion, we retain only a minimal tombstone record (the feedback ID, a `redacted` flag, signal type, and timestamp) for audit purposes. All payload data, error details, and client metadata are permanently removed.

<Tip>
  There is no automatic collection to opt out of - every submission to `/v1/feedback` is a deliberate, manual call you make yourself. Simply stop calling it to stop all future data collection immediately.
</Tip>