本文档尚未翻译成简体中文，现显示英文原文。
Data collection
What we store, and what we never store
This page describes, plainly, what MyIP OpenRouter actually writes to its database. The legal notice lives in our Privacy Policy; this page covers only the technical facts.
The short version
We do not store the prompts or responses you send through the API. What we keep per request is the metadata that billing and troubleshooting require: token counts, cost, model, timing, and outcome. Conversations held in the website's Chat page are the one exception, and you can turn that off.
Always recorded for an API request
Each finished request appends one usage record. The fields below cannot be turned off — they are what makes a charge computable and reproducible.
| Category | Fields |
|---|---|
| Identifiers | Generation id (gen-…), request id, user id, the API key used |
| Model | Requested model id, model that actually answered, provider name, endpoint called |
| Tokens | Prompt, completion, reasoning, cache-hit, cache-write, and total token counts |
| Money | Amount charged (KRW), the prompt and completion unit prices applied, exchange rate, margin |
| Timing | Time to first byte, total generation time, creation timestamp |
| Outcome | Success / error / cancelled, finish_reason, error code and message |
| Routing | Which fallback candidates were tried, how many attempts, and how each ended |
You can read all of it back yourself with GET /api/v1/generation?id=gen-….
Never recorded for an API request
- The contents of the
messagesarray — system, user, and assistant message bodies - The text the model generated
- The contents of attached images or files
- Tool-call arguments and tool results
The usage record table has no columns for any of that. Request bodies are relayed upstream, responses are streamed through to your client, and once the tokens are counted the content is gone.
The two things you control
/settings/privacy has two toggles. Both default to on.
Chat history (store_chat_history)
Controls whether conversations held in the website's Chat page are stored.
- On: the room and its message bodies are saved, so you can come back and continue.
- Off: no room is created and no message is written. Model responses still render normally, but they are gone when you reload.
This setting has nothing to do with the API. Prompts sent to the API are not stored regardless of its value.
Request metadata (store_request_metadata)
Controls whether HTTP-Referer, X-Title and User-Agent are kept on your usage records. These are what identify which of your apps made a request; see App attribution.
Turning it off means requests can no longer be attributed to an app, but token counts and costs are still recorded. Billing is unaffected.
Account and payment data
| What | Why |
|---|---|
| Email, name, profile image | Received from the OAuth provider you signed in with (Naver or Google) |
| Credit ledger | One row per top-up, bonus, deduction, and refund. It is an accounting record, so rows are never edited or deleted |
| Payment records | Order id, amount, supply amount, VAT, payment method, approval time, receipt link, and the raw approval response from the payment gateway |
| API keys | Only a SHA-256 hash — never the plaintext. The full key is shown once at creation and cannot be retrieved again |
Card and bank account numbers never reach us; TossPayments handles all payment credentials.
Administrator actions
Administrative operations — price changes, key suspensions, ledger corrections — are written to an audit log: who, when, what, the before and after values, plus the originating IP and User-Agent. This is the evidence trail for any billing dispute.
Where the data lives
Everything is stored in PostgreSQL on our own servers in South Korea. That is what data_region: "kr" in the GET /api/v1/generation response means.
Requests served by a local GPU model (google/gemma-4-26b-a4b, lgai/exaone-4.0-32b) never leave our infrastructure. Requests routed to an external provider become subject to that provider's policies as well — see Provider logging.
Managing your data
- See your usage —
/settings/activity, orGET /api/v1/generation - Delete a conversation — deleting a chat room in the Chat page deletes its messages with it
- Revoke a key — revoking at
/settings/keyspermanently stops that key from authenticating - Account deletion and access requests — follow the process described in the Privacy Policy
最后更新于 2026年9月5日