Privacy Policy

1. Overview

OpusLive ("the Service", "we", "us", "our") is an API gateway that provides managed access to AI language models. This Privacy Policy explains what data we collect, what we do not collect, and how we handle information that passes through our Service.

2. What we do not collect

We want to be explicit about what we do not store or log:

• Prompt content — The text of your messages, instructions, and system prompts is never stored. It passes through our servers in transit and is immediately discarded after forwarding.
• AI responses — Model outputs (text, code, analysis) are streamed through to you and not retained.
• Images and files — Any images, documents, or files included in your API requests are forwarded to the upstream model and not stored by us.
• Conversation history — We do not maintain any record of your conversations or message threads.
• Personal information — We do not collect names, email addresses, IP addresses, browser fingerprints, or any other personally identifiable information from API users.
• Cookies or tracking — The API does not set cookies or use any tracking mechanisms.

3. What we do collect

We store the minimum metadata required to enforce usage limits and provide usage dashboards:

• Token counts — The number of input and output tokens per request. Used to enforce per-key token budgets.
• Timestamps — When each request was made. Used for rolling window calculations and usage history.
• Model name — Which model was requested (for example "claude-sonnet-5"). No actual model output is stored.
• HTTP status code — Whether the request succeeded (200) or failed (400, 500, etc.).
• Response latency — How long the upstream model took to respond, in milliseconds.
• API key identifier — Which key made the request, for per-key usage tracking.

This metadata is strictly operational. It cannot be used to reconstruct your conversations.

4. How data flows through the Service

When you make an API request:

1. 1Your request arrives at our API gateway over HTTPS (encrypted in transit).
2. 2We validate your API key and check usage limits.
3. 3The request is forwarded to the upstream AI model provider over HTTPS.
4. 4The response is streamed back to you in real time.
5. 5We record only the metadata listed in Section 3.
6. 6The request and response content is discarded — it exists only in memory during transit.

At no point is your request or response content written to disk, logged to a file, or stored in a database.

5. API key data

API keys are stored in our database to authenticate requests. Each key has associated configuration (name, rate limits, token budgets, expiration date) set by your administrator. We store a prefix of each key for display purposes and the full key in hashed form for authentication. Key usage metadata (total tokens used, window usage, last used timestamp) is updated with each request.

6. Data retention

7. Third-party services

Your API requests are forwarded to upstream AI model providers to generate responses. These providers have their own privacy policies and data handling practices. We do not control how upstream providers handle your data once it leaves our servers. We recommend reviewing the privacy policies of the model providers whose services you use through OpusLive.

8. Security

• All communication with the Service is encrypted using HTTPS/TLS.
• API keys are validated on every request.
• Rate limiting and token budgets protect against abuse.
• No request or response content is written to persistent storage.
• Database access is restricted and credentials are securely managed.

9. Children's privacy

The Service is not directed at children under 13 years of age. We do not knowingly collect personal information from children. If you believe a child has used the Service, please contact your administrator.

10. Your rights

Since we collect minimal data and no personal information from API users:

• Access — view your usage data on the Check Usage page at any time using your API key.
• Deletion — contact your administrator to delete your API key and all associated usage data.
• Portability — the usage data visible on the Check Usage page represents all data we hold about your key.

11. Changes to this policy

We may update this Privacy Policy from time to time. Changes take effect when posted on this page. Continued use of the Service after changes constitutes acceptance of the updated policy.

12. Contact

If you have questions about this Privacy Policy or how we handle data, please contact your administrator or the OpusLive team through the appropriate support channels.