Tag: Zero Data Retention

OpenRouter’s Unified API: The Hidden Routing Mechanics and How to Reclaim Control

A unified API does not mean a unified model. Default routing silently swaps infrastructure, precision, and data policy on every call.

The string "model": "meta-llama/llama-3-70b-instruct" looks like the point where engineering decisions end. You picked the model; the provider handles the rest. In practice, it is the start of a branch your integration is likely blind to: the same model identifier, in different seconds, routes to different infrastructure, with different weight precision, different latency, and different data retention policy. The model is nominally the same. The behavior is not.

Continue reading “OpenRouter’s Unified API: The Hidden Routing Mechanics and How to Reclaim Control”

How to Keep Customer PII Out of LLM Provider Logs

An in-flight anonymization gateway and Zero Data Retention contract as two lines of defense against GDPR violations through AI.

An employee pastes a customer's bank statement into an AI assistant to draft a reply. The statement contains a name, passport number, IBAN, address, and transaction amounts. The assistant calls a cloud model. From this point, the customer's PII has physically left the perimeter and sits in the provider's infrastructure — at minimum in active processing, and by default in abuse-monitoring logs for 30 days. The customer never consented to this transfer.

This is the single most common way companies violate GDPR through AI. Not through malice, but because nothing stood in the request path to strip the data before the model call.

Continue reading “How to Keep Customer PII Out of LLM Provider Logs”