Your conversations.
Your access.

Preview information · October 30, 2026

Unbind is a small text chat service. Model availability can change during the preview. Real-money deposits are disabled.

A browser session is your identity

Unbind stores a random session cookie in your browser. The cookie is Secure, HttpOnly, and SameSite; the server stores a hash of its secret. Your conversations and credits belong to the server-side identity associated with that session, never to an IP address.

Clearing browser data or losing the session means losing access unless you linked a wallet first. There is no recovery code or automatic recovery by location, IP address, or device. Existing addresses and balances are never assigned to another guest.

What is stored

The service stores conversations, usage and token counts, credit ledger entries, deposit records, and an optional linked public wallet address. For Unbind API keys it stores a hash of each key, a short identifying prefix, its restrictions and usage records. Deleting a conversation removes it from your chat list; the current implementation retains its stored content and accounting records. It does not erase it from the database.

Model providers

A model provider receives the messages needed for a reply, including relevant conversation history. The selected model for this deployment is DeepSeek V4.1 Flash Uncensored, accessed through Experiential Labs. Unbind also used IFM during its preview. Provider availability may change.

When an uncensored model is used through Experiential Labs, Experiential says it retains a copy of every prompt and response even if prompt storage is switched off. These models do not offer zero-data-retention routing. Deleting a chat from Unbind does not delete the provider's copy. See Experiential's data controls for its terms.

Unbind does not promise zero retention, no training, or end-to-end encryption. Avoid sending information you do not want a provider to receive and retain.

Abuse protection

Server-side Cloudflare Turnstile checks and session/IP rate controls protect free usage. Creating an API key yourself requires a Turnstile check; an operator may also issue one for an existing user. Authenticated API calls use the key and server-side limits without a browser challenge on each request. IP information is an abuse signal, not proof of identity or permission to read an account. People on shared networks retain separate accounts.

Optional wallet access

Linking a wallet uses a domain-bound, expiring, single-use signed message. It does not request a transaction or access to the wallet's private key. Public wallet addresses and on-chain deposits are publicly visible on Solana.

Preview limitations

The service is a preview. An operator contact and final retention policy have not yet been published.