VAREXIS-INDEX ยท Free evidence
AI retained copies and observation evidence
Eight operator decisions: ZDR eligibility, stored and exported logs, cached replies, abuse retention, encryption scope and actual inference-region evidence. Complete documentary reviews; no live verification or new executable support. Existing trial guides remain unchanged.
Catalogue additions are available free through the exact HTTP JSON links below. Enhanced natural-language discovery is not yet qualified for these records. They are outside MCP search, MCP preview and paid saved retrieval. No search qualification, executable capability or entitlement is added.
Complete exact-ID manifest · Full catalogue · Existing MCP coverage
A ZDR key label is eligibility, not contract verification
Does marking a Vercel BYOK key ZDR-compliant enable zero-retention routing or verify its provider agreement?
Vercel treats a key mark as eligibility for ZDR routing, not activation. Team-wide ZDR or request zeroDataRetention must also be enabled. The mark relies on the owner's provider agreement, which Vercel cannot inspect. ZDR routing can fall back to eligible system credentials and fails if no eligible provider is available.
Documentation reviewed 2026-11-08. Primary source.
Boundaries
- Require the effective ZDR gate, eligible credential identity and applicable provider agreement; refuse to infer deletion or contract validity from a label.
- A marked key with applicable agreement and enabled ZDR can be eligible; an unmarked key can be skipped even when its owner separately believes it has suitable terms.
- No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
- No new product compatibility, positive fit rule or licence right.
Complete record JSON · Exact free preview JSON · Source review
Payload suppression still leaves defined metadata paths
Does a Cloudflare AI Gateway payload-log opt-out eliminate the full request log?
The payload header controls request and response bodies while metadata can still be logged. The collect-log header controls the wider stored entry and overrides gateway defaults. For Unified Billing, billing details are recorded even when collection headers are false. These controls apply to gateway-stored logs, not provider retention.
Documentation reviewed 2026-11-08. Primary source.
Boundaries
- Require gateway defaults, actual headers and billing mode; do not infer no retained data from absent prompt bodies.
- For an ordinary request with collection disabled, the normal stored log entry can be skipped; the documented billing exception must not be applied indiscriminately.
- No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
- No new product compatibility, positive fit rule or licence right.
Complete record JSON · Exact free preview JSON · Source review
Logpush exports are independent of gateway log opt-outs
Do Cloudflare AI Gateway collection headers prevent Logpush from exporting that request?
Cloudflare states that Logpush exports regardless of gateway log enablement and the collection headers. Export requires a public key, the gateway Logpush setting and an enabled destination job. Exported copies have a separate destination custody boundary; disabling gateway collection does not establish their removal.
Documentation reviewed 2026-11-08. Primary source.
Boundaries
- Require the Logpush job, destination and retained-copy evidence separately; do not use gateway log absence or one enabled toggle as an export or deletion receipt.
- Without an enabled destination job, enabling the gateway toggle alone does not start exports; configured independence is not proof that a particular export arrived.
- No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
- No new product compatibility, positive fit rule or licence right.
Complete record JSON · Exact free preview JSON · Source review
A cache response is not a fresh provider invocation
Does a successful Cloudflare AI Gateway response prove the current request reached the model provider?
Cloudflare documents returning a cached response until its TTL expires. A custom cache key makes requests sharing that key reuse the response, so the caller must group only equivalent requests. The skip-cache header bypasses that cache. Log collection and provider processing evidence remain separate questions.
Documentation reviewed 2026-11-08. Primary source.
Boundaries
- Require effective cache settings, key policy and hit/bypass evidence before claiming a fresh provider execution; a TTL is not an all-copy deletion receipt.
- A cache miss or explicit skip can contact the provider; an enabled cache does not mean every response is a hit.
- No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
- No new product compatibility, positive fit rule or licence right.
Complete record JSON · Exact free preview JSON · Source review
Missing legacy logs can reflect storage policy
Does no Cloudflare AI Gateway log establish that no request occurred?
Cloudflare distinguishes legacy logging eligibility from newer Workers Logs arrangements. Legacy logs persist until deletion; at capacity the gateway can stop saving or delete its oldest logs. The documented historical absence can therefore reflect capacity or deletion rather than no traffic.
Documentation reviewed 2026-11-08. Primary source.
Boundaries
- Require the account's logging cohort, capacity, deletion mode and relevant time interval; refuse a zero-activity conclusion from missing rows.
- An independently complete observation interval can support a narrower count; the existence of capacity limits does not prove a specific gap occurred.
- No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
- No new product compatibility, positive fit rule or licence right.
Complete record JSON · Exact free preview JSON · Source review
Invocation-log opt-out does not govern abuse-retention copies
Does disabling Bedrock invocation logging establish zero retained prompts and outputs?
AWS documents model-specific abuse retention separately from optional invocation logging, including flagged-traffic and all-traffic cases with stated exceptions. For affected cross-Region models, retained inputs and outputs are stored in the processing destination Region. The exact model, programme eligibility and applicable date govern the documented exception.
Documentation reviewed 2026-11-08. Primary source.
Boundaries
- Refuse zero-retention or source-region-only storage conclusions from invocation-log settings; require the exact model policy and account agreement, including expiry of any exception.
- A model or approved programme may have different documented treatment; do not generalize one model's retention interval to every Bedrock model.
- No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
- No new product compatibility, positive fit rule or licence right.
Complete record JSON · Exact free preview JSON · Source review
Responses storage encryption does not cover application-held copies
Does Foundry Agent Service storage configuration describe direct Responses API state and all client-held reasoning items?
Microsoft describes direct Responses API history as service-managed storage without bring-your-own-data storage, distinct from Agent Service arrangements. Resource CMK protection applies only where configured and applicable. That description does not cover application-retained material, including encrypted reasoning items returned for stateless requests.
Documentation reviewed 2026-11-08. Primary source.
Boundaries
- Require the exact API and storage owner for each copy plus applicable key coverage; refuse to infer client-copy protection or deletion from service encryption settings.
- Applicable CMK configuration can protect covered service-managed content; it is not evidence that all content lacks encryption.
- No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
- No new product compatibility, positive fit rule or licence right.
Complete record JSON · Exact free preview JSON · Source review
The recording Region is not always the inference Region
Which Bedrock event field identifies where a cross-Region invocation was processed?
AWS records cross-Region requests in the source Region and documents additionalEventData.inferenceRegion for processing location. Its streaming-completion example uses serviceEventDetails.AdditionalEventData.additionalEntries.inferenceRegion and parentRequestId. The event type and correlation matter; awsRegion identifies where the event was recorded.
Documentation reviewed 2026-11-08. Primary source.
Boundaries
- Require the matching endpoint, event type, selector coverage and correlated request; refuse to substitute a logging Region or missing region field for execution evidence.
- A request can be processed in its source Region, so the two values can agree; disagreement is not required for every cross-Region profile request.
- No live deployment, complete retained-copy inventory, verified deletion, sovereign processing or legal compliance is established.
- No new product compatibility, positive fit rule or licence right.
Complete record JSON · Exact free preview JSON · Source review