Privacy policy
Creekside Compute operates an inference API that runs open-weight language models on GPUs we rent from cloud and marketplace providers. Requests reach us either directly, with your API key, or through a marketplace such as OpenRouter, Poe, NanoGPT, Hugging Face or Vercel. We are an independent controller for the operational data described here and a processor for the content you send.
This policy is issued by Creekside Compute. It covers the API at api.creeksidecompute.ai and traffic that reaches us through a marketplace.
Two service tiers
Zero retention (default)
We do not store, log, or forward the content of your requests or responses anywhere except to the GPU worker that serves the request, in memory, for the time it takes to generate the answer. Content is never written to disk. Because no copy exists, there is nothing to train on, license, disclose or lose. This guarantee is structural rather than a statement of intent. This is the tier behind our default API keys and our zero-retention marketplace listings.
Two things pass through the router's memory on this tier, and neither is written to disk. If you send an Idempotency-Key header, the router holds that response in memory for up to ten minutes so that a retry after a dropped connection returns the same answer. To route related requests to the same worker, the router keeps a short hash of the start of a conversation for fifteen minutes; the content cannot be recovered from it.
Retained (discounted)
Where you choose the retained tier, by retained API key, retained marketplace listing, or the request header x-creekside-retention: store, we store the request and the response for up to 90 days in a private cloud bucket in the United States, encrypted at rest, with access limited to named staff. By choosing this tier you grant us a licence to use that content, which may include improving our service, evaluating model quality, and licensing it to third parties including for model training. The discount is the consideration for those rights. If that is not acceptable, use the default tier, which is zero retention and costs more for exactly this reason.
The header always wins, in both directions. x-creekside-retention: none on a single request prevents storage even under a retained key, and x-creekside-retention: store opts a single request in under a zero-retention key.
What we always keep
For every request, regardless of tier: a request id, the API key id, timestamps, token counts (prompt, completion, cached), latency, the worker that served it, and status or error codes. No content. Retained for 13 months for billing, abuse prevention, and capacity planning.
Where processing happens
GPU workers run on rented machines from marketplace suppliers, currently Vast.ai hosts, which have been located in South Korea, Thailand and the United States. Content passes to those machines over an encrypted tunnel and is processed in memory.
Your rights
- Deletion on request. Retained records for your key are deleted within 7 days of a verified request to the address below; zero-retention traffic has nothing to delete.
- Access and export. On request, we provide the operational records associated with your key.
- Breach notice. We notify affected customers within 48 hours of confirming a breach involving their data.
Marketplaces
When you reach us through a marketplace, that marketplace is the controller of your account and payment data; we receive only the request content and, where the marketplace provides one, an anonymised user id. Poe informs its users that API bots may store conversations; our Poe bot runs on the zero-retention tier unless its description says otherwise.
Changes
We post changes on this page with a new effective date.
How to reach us
Write to hello@creeksidecompute.com for deletion or access requests, breach questions, or anything else about how Creekside Compute handles your data.