Data handling
OpenGa^3in is an inference gateway operated by Ga^3in Ventures LLC. Your requests pass through it on the way to a model provider. Prompts and completions are never stored. This page states exactly what is recorded, where it lives, and how you can verify it yourself.
01What we record, and what we do not
Recorded, per request
- Timestamp and duration
- Model requested and provider used
- Token counts: prompt and completion
- Cost in USD
- A hash of the API key used, and your organization id
- Success or failure, and the error class on failure
- The user agent of the calling SDK, for example node or python-httpx
Never recorded
- Prompt text, of any kind
- Model output text
- System prompts and tool definitions
- Files, images or documents you send
- Your end users' identities or content
- Your IP addresses, or your users'
- Anything that would let us reconstruct what you asked
This is enforced in the gateway's configuration, not by policy alone: message logging is disabled at the proxy layer and prompt storage is switched off in the spend database. The payload fields in our request records are empty objects, by construction.
On IP addresses. Your calls reach the gateway through our own edge, so the only network address our engine ever sees is that edge's internal address, identical for every customer. We do not receive your IP address or your end users', and we have chosen not to forward them: for an invite only gateway, per key budgets, rate limits and instant revocation cover abuse without holding anyone's location data.
02How to verify it yourself
Every field we hold about your requests is shown back to you in the portal. Sign in and open Activity: the request log there lists time, model, key label, token counts, cost and latency. That view is the whole record. There is no second, hidden store behind it.
03Where the data lives
- Gateway and usage database — Fly.io, United States (Newark, New Jersey). Holds key hashes, budgets and the per request metadata above.
- Portal and API edge — Netlify, United States. Serves the pages and forwards API calls; stores nothing itself.
- Sign in — Clerk. Holds your email address and session records. We do not set or store passwords; sign in is Google or an emailed code.
- Payments — Stripe. Card details go to Stripe directly and are never seen by Ga^3in. We hold the invoice amount and reference only.
- Account records — Airtable. Organization name, contact email, budget, credit ledger entries.
All traffic is TLS encrypted in transit. Provider credentials held on your behalf are encrypted with AES-256-GCM before storage; the decryption key is held separately from the stored value.
04Model providers, and what they see
Your prompt necessarily reaches the model provider you selected: that is the service. What the provider does with it is governed by that provider's own terms, not ours, and we do not represent otherwise. Today:
- Anthropic (Claude models) — United States. The default for every organization. Anthropic's commercial API terms apply.
- DeepSeek direct — servers in China. Off by default and never enabled silently. It appears in the catalog labelled "CN data path" and only carries traffic if you deliberately call one of those model names. If you would rather it not be reachable at all from your organization, say so and we remove it from your allowed models.
Model names in the portal carry their data path, so you always know which jurisdiction a call will reach before you make it.
05Who can see what
- You see your own organization only: your keys, spend, budget and request metadata. Organizations cannot see each other, and this is enforced on the server, not in the interface.
- The Ga^3in team can see organization level usage and spend, and can create, suspend or revoke access. We cannot see your prompts or outputs, because they are not stored anywhere to see.
- Your API keys are stored as hashes. A key is displayed once at creation and cannot be retrieved afterwards, by you or by us. Revocation takes effect immediately.
06Retention and deletion
Request metadata is retained for 12 months for billing, reconciliation and capacity planning, then deleted. Account and invoice records are retained as long as required for tax and accounting purposes. On written request we will delete your organization's metadata ahead of that schedule, subject to records we must keep for accounting, and confirm when it is done.
07What we do not claim
Stated plainly, because you will ask and because we would rather you heard it from us:
- OpenGa^3in is not SOC 2 certified. It is a pre-production service, invite only, run by a small team. If you need a certified vendor for this workload today, we are not it yet.
- We offer no uptime SLA at this stage. The gateway is monitored continuously and we alert on outage, but that is a practice, not a contractual guarantee.
- We are happy to sign a mutual NDA before you send production traffic, and our standard data processing agreement is published and ready to execute.
08Contact
Questions, a security review, or a deletion request: team@gain.ventures. Security issues reported to that address are acknowledged within one business day.