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

# Data controls and parameter filtering

> Distinguish request fields, channel filtering, upstream storage, and deployment logging.

## Default field handling

These are the behaviors of `RemoveDisabledFields` in `relay/common/relay_info.go` when called without global/channel request passthrough. They are not a universal retention contract for every upstream, plugin, and configuration.

| Field | Default handling | Configuration boundary |
| - | - | - |
| `service_tier` | Removed | Requires channel permission and upstream support for the tier |
| `inference_geo` | Removed | Claude region extension; forwarding permission does not prove residency |
| `speed` | Removed | Claude speed extension; requires channel permission and upstream support |
| `safety_identifier` | Removed | Requires channel permission; avoid raw personal information |
| `store` | Forwarding allowed by default | `DisableStore` removes the field; it **does not force false** |
| `stream_options.include_obfuscation` | Removed | Requires channel permission; separate from enabling streaming |

Global or channel passthrough skips this filter. Other conversions, parameter overrides, and upstream defaults can still affect the effective request. Sending a field alone cannot establish its effect; the deployment must verify its path and configuration.

## What `store: false` establishes

It requests that a supporting upstream not store the corresponding response resource. It does not establish no gateway logging, disabled caching, no training, or end-to-end zero data retention. In particular, deleting `false` through `DisableStore` restores upstream default behavior; this setting does not enforce non-storage. Logs, proxies, channel providers, caches, and task artifacts have separate lifecycles to verify.

Stateless [conversation history](/en/guides/conversations.md) reduces reliance on saved response IDs, but the replayed history still reaches the upstream. Search queries, PDFs, and tool inputs also reach their executing services. OpenRouter's ZDR filters, BYOK, service-tier options, and training-policy parameters are not end-to-end guarantees in this project.

## Integration checks

1. Identify native versus converted paths and channel parameter overrides or filtering.
2. Select content permitted by deployment policy; retain only necessary diagnostic fields in application logs. See [observability](/en/guides/observability.md).
3. Obtain deployment-specific retention, deletion, and third-party service details. Local fixtures and a successful request do not verify those policies.

This guide does not change channel settings. See `store: false` in [PDF input](/en/guides/file-inputs.md) and [web search](/en/guides/web-search.md). Local checks verify the sending intent, not upstream retention.

Implementation sources: `relay/common/relay_info.go`, `relaykit/dto/channel_settings.go`, and channel adapters.

[阅读中文](/zh/guides/data-controls.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.