Trust
Privacy and data
What Cairva stores about requests, what it doesn't, and who can see requests, quotes and usage.
Cairva is built so the deal stays between the two parties and the request content stays between the buyer and the route that serves it. This page lists what's stored and who can see what. The privacy policy is the binding document.
Prompts and completions
Prompts and model outputs aren't stored. They pass through the gateway to the supplier route that serves your allocation and back to you. Cairva's logs redact fields that carry message content, keys and secrets.
For each request Cairva stores metadata only:
| Stored | Not stored |
|---|---|
| Allocation, key, model, whether it streamed | Messages |
Your x-request-id and the provider's request id | Completion text |
| Status, error code, latency, timestamps | Reasoning or any other model output |
| Tokens held, and tokens booked as a usage event |
The supplier's own systems receive your messages, because that's how inference is delivered. Their handling is governed by your agreement with them. Use the request's privacy requirements field to state what you need before you accept a quote.
Requests and quotes
| Who | Sees |
|---|---|
| Your organization | Your requests, every deal room on them, your agreements |
| An invited supplier | The request it was invited to, and its own deal room. Never other suppliers' quotes |
| Other suppliers and the public | Nothing |
| Cairva operations | Everything, to run the market and resolve disputes |
Drafts stay private to your organization until you send them. A supplier can quote without disclosing its name until you accept.
Usage
The buyer and the supplier on an agreement see the same usage events and the same remaining allowance. Nobody else outside Cairva operations does.
API keys
Only a keyed hash of each key is stored. The secret is shown once when it's created and can't be retrieved later.
Audit trail
State changes on requests, quotes, agreements, allocations, keys, lots, routes and suppliers write an audit event with the actor, time, the state before and after, and any reason. The agreement page shows its history to both parties. Cairva operations can see the full log.
Public pages
The market shows active lots, not buyers or deals. The status page shows route health, request counts and incidents, not who made the requests.