Configure logging and ZDR in the Requesty Console.
What Gets Stored
Every API request produces two categories of data: telemetry (metadata about the request) and payload (the actual prompt and response content). These are handled independently.Telemetry (always stored)
Regardless of your logging or ZDR settings, Requesty stores operational metadata for billing, analytics, and debugging:
This data powers your analytics dashboards, cost tracking, and alerting. It contains no prompt or response content.
Payload (only stored when logging is enabled)
Request and response content is only stored when both of the following are true:- The API key has
loggingenabled - The organization does not have ZDR enabled
Even with logging enabled, message and response content is truncated before storage. Full raw request bodies are stored separately in encrypted object storage.
Logging Controls
Logging is controlled at two levels: per-API-key and per-organization.Per-API-Key Logging
Each API key has alogging boolean that determines whether payload data is captured for requests made with that key.
Default behavior: New API keys inherit the organization’s default_logging setting. Admins can toggle logging on individual keys at any time (unless restricted by organization policy).
Organization Logging Policy
Organization admins can configure two settings that govern logging behavior across all API keys:
These settings are available under Admin Panel > Settings for organizations on the Enterprise plan.
- Default Configuration
- Privacy-First Configuration
- Enterprise Lockdown
Suitable for most teams:
default_logging = true: New keys log by default for observabilityallow_logging_change = true: Users can turn logging off on keys handling sensitive data
Who Can Change Logging
Zero Data Retention (ZDR)
ZDR is an organization-level compliance mode that provides a hard guarantee: no request or response content is ever stored, and this cannot be reversed.What ZDR Does
When an admin enables ZDR, four things happen atomically:1
Organization flag set
The organization is permanently marked as ZDR-enabled. There is no disable endpoint.
2
All existing API keys updated
Every API key in the organization has logging and debugging set to
false.3
Org defaults locked
The organization’s
default_logging is set to false, so all future API keys are created with logging off.4
Logging changes blocked
allow_logging_change is set to false. No user, including admins, can re-enable logging on any key.ZDR vs. Logging Off
How ZDR Is Enforced
ZDR enforcement happens at multiple independent layers, so even a bug in one layer cannot cause data leakage. Layer 1: Router (data plane) The router checks both the ZDR flag and the API key’s logging setting before attaching any payload data to the insight. If either condition blocks logging, the messages, choices, and tools fields are never populated. They are not sent to any downstream service. Layer 2: Raw request storage Full request bodies are only sent to encrypted object storage when the API key has logging enabled. Since ZDR forces logging off on all keys, raw request bodies are never stored. Layer 3: Accounting service (control plane) The accounting service receives insights from the router. When payload fields are absent (as they always are under ZDR), the service takes a telemetry-only ingestion path. No message content reaches the database. Layer 4: Configuration lockdown ZDR prevents re-enabling logging at every level: individual API key updates, organization config changes, and new API key creation. The API returns403 Forbidden for any attempt to enable logging on a ZDR organization.
What This Means in Practice
With ZDR enabled:- Requesty cannot see your prompts or responses. The data is never attached to internal messages, never written to any database, and never stored in object storage.
- Your analytics still work. Token counts, costs, latency, model usage, error rates, and all operational metrics continue to function normally.
- Audit trail is maintained. All ZDR and logging configuration changes are recorded in your organization’s audit log.
- Debug logs excluded. ZDR also disables the debug flag on all API keys, which prevents request/response bodies from appearing in application logs.
Enabling ZDR
ZDR can only be enabled by an organization admin.- Navigate to Admin Panel in the Requesty Console
- Locate the Zero Data Retention section
- Enable ZDR
Provider-Side Data Policies
ZDR and logging controls govern what Requesty stores. Your requests still travel to the upstream LLM provider (OpenAI, Anthropic, Google, AWS Bedrock, etc.), and each provider has its own data retention and training policies. To achieve end-to-end data privacy, you need to consider both layers.How Requesty Helps You Choose
Every model in the Requesty catalog is tagged with provider-level data policy metadata:
These fields are visible in the Model Library, on individual model cards, and in the Approved Models admin panel. Models tagged “Zero retention” and “Not for training” are highlighted in green.
Filtering by Data Policy
Use the Data Policy filter in the Approved Models panel to restrict your organization to providers that match your compliance requirements:- Data Retention = No: Only show models where the provider does not retain your data
- Data Used for Training = No: Only show models where the provider does not use your data for training
Quick Start Presets
The Approved Models panel offers one-click presets for common compliance configurations:
These presets filter and pre-select matching models. Review the selection and confirm to apply.
Enabling Requesty’s ZDR mode does not automatically restrict your approved models to zero-retention providers. These are independent controls. ZDR prevents Requesty from storing payloads. Approved Models controls which providers your team can send requests to. For maximum data privacy, enable ZDR and restrict approved models to zero-retention providers.
Layered Privacy Strategy
For organizations with strict data handling requirements, combine multiple controls:Enterprise Plan Features
Organizations on the Enterprise plan have additional configuration options for fine-grained control over data handling.Available Controls
Default Logging Policy
Set whether new API keys are created with logging on or off by default
Logging Change Restrictions
Prevent non-admin users from toggling logging on their own API keys
Zero Data Retention
Irrevocably disable all payload logging organization-wide
Audit Logging
Full audit trail of all configuration changes, including who changed what and when
Compliance Matrix
FAQ
Can Requesty employees see my prompts?
Can Requesty employees see my prompts?
No. When logging is off or ZDR is enabled, prompt and response content is never stored. There is no data to access. When logging is on, payload data is stored in your organization’s encrypted storage, accessible only through your API keys and the Requesty Console with appropriate RBAC permissions.
What happens to existing logs when I enable ZDR?
What happens to existing logs when I enable ZDR?
ZDR applies to new requests only. Historical log entries with payload content remain accessible. ZDR prevents any new payload data from being captured going forward.
Can I enable ZDR for specific API keys instead of the whole organization?
Can I enable ZDR for specific API keys instead of the whole organization?
ZDR is organization-wide. For per-key control, toggle logging off on individual API keys. This achieves the same result (no payload storage) but is reversible and key-specific.
Does disabling logging affect my analytics?
Does disabling logging affect my analytics?
No. Token counts, costs, latency, model usage, and all operational metrics are always captured regardless of logging settings. Only prompt/response content is affected.
Is ZDR reversible?
Is ZDR reversible?
No. ZDR is intentionally irreversible to provide a compliance guarantee. If you need flexibility, use per-key logging controls instead.
How do I verify ZDR is working?
How do I verify ZDR is working?
After enabling ZDR, check the Logs view for any new request. You will see telemetry data (tokens, cost, latency, model) but the Messages tab will show no content. This confirms payload data is not being captured.
Does ZDR prevent the LLM provider from seeing my data?
Does ZDR prevent the LLM provider from seeing my data?
No. ZDR controls what Requesty stores. Your prompts and responses still travel to the LLM provider for inference. To control provider-side data handling, use the Approved Models data policy filters to restrict your organization to zero-retention, no-training providers. For the strongest guarantee, use BYOK with a custom data processing agreement with your provider.
Does enabling ZDR automatically restrict which models I can use?
Does enabling ZDR automatically restrict which models I can use?
No. ZDR and Approved Models are independent controls. ZDR governs Requesty-side storage. Approved Models governs which providers your team can send requests to. For end-to-end privacy, enable ZDR and restrict approved models to zero-retention providers using the data policy filter or the “ZDR Only” quick-start preset.