Data handling and location

Prompts, outputs and training

We do not persist customer prompts, completions, tool arguments or tool results in request logs, databases, object storage or backups. We do not use customer content to train, fine-tune or evaluate models. Request and output logging are disabled for the serving engine.

This policy applies to requests received after its publication at the Hixtube inference endpoint, api.hixtube.com/v1, including Hixtube requests routed through TrustedRouter. It does not make a retention promise for a different provider selected by a router fallback.

In-memory processing and caching

Inference processes content in CPU and GPU memory. Prefix and KV caches can remain in volatile memory between requests until eviction or process shutdown. ZDR here means no persistent content storage; it does not mean that every memory allocation is erased immediately after each response.

We do not write these inference caches to disk. They are not a training dataset or a durable conversation history.

Operational metadata

Content-free operational records may include request identifiers, model identifiers, token counts, timings, status codes, capacity counters and charges. Such records support billing, reliability and abuse prevention. ZDR does not mean that billing or operational metadata is absent.

TrustedRouter maintains its own account, billing and gateway records under its privacy policy. A chat application or client may also save conversation history; this policy does not control that storage.

Finland inference

The current DeepSeek deployment runs on a Verda GPU node in Finland, rented through Spheron. There is no provider-side geographic failover configured. This is an operator-verified hosting declaration, not a hardware-attested country claim.

The endpoint has one serving location and no per-request region selector. To restrict TrustedRouter inference to Hixtube, set provider.only=["hixtube"] and provider.allow_fallbacks=false. Add provider.min_privacy="zdr" to require ZDR eligibility rather than relying on the provider selection alone. These settings do not pin the geography of TrustedRouter gateways, your client, internet transit or billing systems.

Future hosting changes require a review and an updated declaration before requests are sent to a different location. The current capacity is a finite lease, not a permanent availability guarantee.

Security boundaries

HTTPS protects network transport. The current node is not confidential computing, and the infrastructure operator could access workload memory. No CPU/GPU remote-attestation or provider-side E2EE claim is made.

A no-training commitment, a no-persistent-content-storage commitment and confidential computing are different protections. Hixtube currently offers the first two, not the third.

This website and contact

This website does not send your prompts to the inference service. It has no site-authored tracking pixels, analytics scripts or forms. Hosting infrastructure may retain access/security metadata or set security cookies.

For privacy, location or deletion questions, contact help@trustedrouter.com and identify Hixtube in the subject. Do not include API keys or sensitive prompt content.