How StreamFix handles your data. Short version: we don't store it.
| Data Type | Stored? | Details |
|---|---|---|
| Prompts & messages | Never | Processed in memory, immediately discarded. Never logged. |
| Model responses | Never | Streamed through and repaired in-flight. Not buffered to disk. |
| API keys (yours) | Never | Your OpenRouter/provider key is forwarded in-memory. Never stored. |
| Request ID & status | Always | request_id, repair status, credits used, timestamps. No content. |
| Credit balance | Always | Email, hashed API key, credit count. Required for billing. |
| Repair artifacts | Opt-in | Only if you enable artifact storage. Retrievable via /result/{request_id}. Auto-expires. |
StreamFix is a passthrough proxy. Your request goes in, gets repaired in memory, and the response goes out. No persistent state beyond billing metadata.
Your data is never used for training, fine-tuning, or any purpose beyond the immediate repair. We are a transport layer, not a model provider.
All traffic is encrypted via HTTPS/TLS in transit. Connections to upstream providers (OpenRouter) are also TLS-encrypted.
Every request requires a valid StreamFix API key. Keys are hashed at rest. Rate limits prevent abuse.
Every response includes provenance headers so you know exactly what was changed:
Repair names are stable. Safe to build alerts and dashboards against.
For security concerns, data handling questions, or vulnerability reports:
rozetyp@gmail.com