Legal
Silicon Network routes your request to a machine someone else owns. That shapes everything below, so this page says plainly who holds what, including where we are not private yet.
Last updated 30 July 2026.
We store the metadata needed to bill you and nothing you wrote. The machine that runs your request currently stores your prompt and the reply on its own disk. If that is not acceptable for your data, run your own node and point your client at it. The software is Apache-2.0 and the wire protocol is identical.
Your email address, a hash of your password, your organisation name, and, if you top up, the wallet address you bind to prove a payment came from you. We do not ask for a legal name, a postal address, or a card.
Organisation, the API key used, the model id, prompt and completion token counts, latency, status, the region of the serving node, and a timestamp. There is no field for your prompt or the reply anywhere in our control plane: not truncated, not hashed, not sampled.
The Silicon Network engine appends every internal event to a log on the operator's disk, and those events carry the messages you sent and every token generated back. The engine also serves that log over its own local API. So the operator of the machine that answered your request can read that request until the log rotates away. Only operators we have approved can receive traffic, and today that is hardware we run ourselves, but the retention is real and we would rather you knew than discovered it.
We are changing this. The intended behaviour is that X-Silicon Network-No-Retention: true suppresses it end to end. Today that header does less than its name promises: our gateway honours it by skipping verification sampling, so your prompt is never copied to a second machine, but the engine has no handler for it yet and still writes its log. The current state is documented in the API docs.
It holds the body in memory long enough to verify your key, resolve the model id, forward it, and count the tokens that came back. It does not write bodies to disk. Two optional features widen that when enabled: content moderation sends prompt text to a moderation service before serving, and verification sampling re-runs a sampled request on our own engine to score the node that served it. Both are currently off.
Our hosting providers process traffic and store our database on our behalf, and an Arbitrum RPC provider sees the public blockchain queries we make to detect your top-up. We do not sell your data, we do not use your prompts to train anything, and we run no advertising or analytics trackers on this site.
Usage records persist so that you and we can reconcile what was billed. Account records persist while your account exists. Ask us to delete your account and we will remove it and its keys; we keep the minimum billing record we need for our own accounts.
You can revoke an API key instantly, set a spend cap, ask for your data, or ask for deletion. Because Silicon Network is open source, you also have an option most providers cannot offer: run the engine on your own hardware and send nothing to us at all.
Write to support@fabriqnetwork.com. If you need a data processing agreement or a named sub-processor list before you can use Silicon Network, say so and we will tell you honestly whether we can meet your requirement yet.