Pura LLM
Pura LLM
OverviewQuick start SDKReact UIConnect with PuraLifecycle webhooksCredentials and encryptionOfficial SDKsDelegated inferencePlans and shared usageTesting and launchIntroductionDeveloper documentation (opens in a new tab)How the Gateway WorksEU Data ResidencyZero Knowledge RetentionAuthenticationQuickstartOpenAI SDKModelsSupport & FAQ

Zero Knowledge Retention

We do not store, log, or retain the content of your prompts, completions, or uploaded files.

Zero retention policy

Prompts and responses pass through the gateway in transit only. They are never written to persistent storage, never used for training, and never shared with third parties beyond the inference provider for that single request.

What zero retention means

Zero retention means your intellectual property, customer data, and conversation content remain yours. We process requests in memory and discard content immediately after the response is delivered.

What we do record

For billing, security, and support we retain only operational metadata:

  • âś“Token counts (prompt, completion, total)
  • âś“Model name and provider used
  • âś“Request timestamp and duration
  • âś“Cost in credits for billing purposes

What we never store

  • âś—Prompt text and message content
  • âś—Model responses and completions
  • âś—Uploaded files, images, or documents
  • âś—Your data is never used for model training

Billing metadata

Usage metadata is retained for the period required by billing and tax regulations. This metadata contains no prompt or response content.

Inference traceability: compliance_metadata v1

Contract for the compliance-enabled gateway. Each deployment must pass the conformity gate before activation; the current catalog is not yet certified.

The v2 contract guarantees provider, actual model, EU data_zone, ingress_region, original upstream_request_id, gateway_request_id and UTC timestamp. The ingress region does not identify the execution region: Azure Data Zone Standard and Bedrock geographic profiles can distribute requests across certified zone regions. The region field remains reserved for regional v1 deployments.

provider_raw is best effort: its presence, structure and completeness are not guaranteed. It contains only metadata permitted by provider-specific allowlists. Do not use it as a contractual dependency.

Read the gateway contract and examples

For completed requests we record stable traceability fields without prompts, responses or provider_raw. Details are available in Logs after activating the integration. Historical logs and failed deliveries may lack this metadata.