Skip to content
++++

Legal

Privacy Policy

Last updated: September 5, 2026

This policy covers the Unbar website, account console, and inference API. The console is the website for your account. This policy explains what information we keep and how we use it.

Zero prompt retention

Unbar does not store your API prompts or model completions. A prompt is the input that you send to a model. A completion is the output that a model returns. We process this content to serve your request. We discard the content after processing. We do not use your API prompts or completions to train models.

1. Information we collect

Account and sign-in information
We collect your email address, account name, optional profile image, and information about your selected sign-in method. A session records a period of account access. Session records can include an IP address, browser information, and sign-in times. An IP address identifies a device on a network.
API key records
A hash is a value calculated from data. A masked value shows part of the API key. We keep a hashed key identifier and a masked value. We also keep your key label, creation and revocation times, and key limits. Revocation stops an API key from authorizing requests. When you create an API key, we show the full key once.
Usage and billing records
We keep model identifiers, token counts, charges, request identifiers, and times. A model identifier selects a model. A token is a unit of model input or output. A request identifier labels one API request. These records support billing and service operations. They do not contain your API prompts or completions.
Payment information
We keep information that matches a payment to your balance. This information includes amounts and transaction references. Cryptocurrency networks record transactions on public blockchains. A public blockchain contains records that anyone can read. These public records are separate from Unbar account records.
Access requests and correspondence
We collect your email and estimated monthly model spend. We collect your model requirements and individual or business status. We also collect your message and optional website. We receive information that you send to support.

2. How we use information

We use account and operational information to control account access. We use this information to maintain balances, calculate charges, and enforce usage limits. We also investigate service problems and abuse. We respond to support requests. Access requests help us plan capacity and contact you about service access. We use sign-in email to make sure that you control account access.

3. Retention

Unbar does not keep API prompts or completions after processing. We keep account, payment, and usage records for account administration, billing, and service operations. These records are separate from API content. We keep access requests to plan capacity and contact you about access. We do not automatically erase access requests after a fixed period.

You can contact us to request erasure of an access request. You can also discuss your account records with us. Payment, security, or applicable legal requirements can require us to keep some records. We can explain which records apply to your request.

4. Service processing

We use hosting, authentication, email delivery, and payment services to operate the website and accounts. Authentication establishes who can use an account. These services process the information for their functions. When you select an external sign-in method, that service processes information under its own policies. When you make a cryptocurrency payment, that service also processes information under its own policies.

5. Account security

Account access requires email verification or a supported sign-in method. Email verification establishes that you control an email address. API keys authorize requests. You can revoke API keys from the console.

Keep your API keys private. Do not include API keys in access requests or support messages. Do not include passwords in these messages. Do not include private conversation content in these messages.

6. Cookies and browser storage

A cookie is data that a website stores in your browser. Unbar uses session cookies to maintain sign-in. A referral link can set a cookie that connects a later account to that referral. If you block these cookies, sign-in or referral attribution can change. Unbar does not store API prompt content in these cookies.

7. Access, correction, and removal

You can ask us about information associated with your account. You can request a copy or correction of this information. You can also request erasure of this information. Before we act, it can be necessary to make sure that you control the associated email address.

If possible, send the request from the associated email address. Do not include passwords. Do not include API keys.

8. Policy changes and contact

We will publish changes to this policy on this page with a revised date. For privacy questions or data requests, you can email support@unbar.sh.

++