A private AI chatbot is defined by what the service keeps. On this key the answer is on the privacy page: no prompt or reply bodies, one usage row per request with token counts and a hash, and for the account an email, a balance and where your first visit came from. This post quotes that page, shows the chat that runs with no sign-up, lists the uncensored builds so private does not also mean filtered, and puts Venice, Lumo and Duck.ai in a dated table next to it.
What a private AI chatbot means on this key
"Private" is a claim about what the service writes down. The privacy page, last updated 2026-11-04 and read for this post on 6 November 2026, lists it. These are the rows a chat touches; the processors, retention and each cookie are on the page itself:
- Prompts and replies
- Not storedRequest and response bodies pass through and are not written anywhere, unless you turn on replay for a key, which keeps that key’s request bodies for 7 days.
- Per request
- One usage rowRequest id, model, token counts by class, the source of those counts and the charge; next to it a SHA-256 fingerprint of the request and the response, never the text. Fingerprints of large system prompts are kept 7 days, to find prompts many accounts send and cache them for everyone.
- Account
- An email and a balanceThe email address you sign in with; sign-in is a 6-digit code that expires and is not kept. Checkout stores the email address and the amount paid as the payment processor or the crypto checkout reports them. The card number never reaches this site. A ledger records balance changes: top-ups, charges, refunds and disputes.
- First visit
- Where you came fromThe referring site, the link’s campaign tags and the page you landed on. A cookie holds them for 90 days, and they are saved with your account when your first sign-in creates it.
- Keys
- A salted hashThe key is shown once and not stored; the hash, its name, status, limits and timestamps are.
- Site visits
- Measured, never the chatGoogle Analytics measures visits to the site: the page address and title, the site that sent you, your browser and device, and an approximate location from your IP address. It sets its own cookies (named _ga) for up to two years, does not run in the console, and never sees prompts, completions or keys. Page views are also counted without cookies.
- Who sees the text
- The model hostEvery model is served by third-party hosting providers under contract with us; they receive the request and response for the calls they serve.
On that last row: the text of your chat reaches the machine that runs the model; nothing else can answer it. What this service adds is that the text is not kept on the way through, and that the record it does keep per request is a usage row you can audit. A signed receipt per request and a signed monthly statement are built from those rows.
What the page does not claim, this post does not claim either. It says nothing about training, because the gateway stores no text to train on and the hosts' own terms are theirs. The about page repeats the storage facts and explains what the daily model check can and cannot catch.
Anonymous AI chat: no name, no sign-up for the first turns
The playground runs a chat on these builds in your browser with no account. A few turns a day are free on the builds marked free; after that you paste a key. The chat, the system prompt and the key stay in your browser; each reply is one request through the API, which keeps the usage row above and not the text.
A key needs an email address and either a top-up from $10, by card or crypto, in the console, or a usage plan from the pricing page: one payment for a month of usage, no renewal. There is no name field, no phone number and no subscription. A top-up balance does not expire. A crypto top-up sends the checkout the email, the amount and the payment, per the privacy page.
From code the same key works with the OpenAI SDK; the Python below uses the openai package with the base URL changed.
from openai import OpenAI client = OpenAI(base_url="https://api.uncensoredllm.ai/v1", api_key="sk-ullm-live-…")reply = client.chat.completions.create( model="deepseek-v4.1-flash-abliterated", messages=[{"role": "user", "content": "Summarize this contract clause for me: ..."}],)print(reply.choices[0].message.content)# The gateway keeps one usage row for this call (model, tokens, charge) and a hash of the body, not the text.What the gateway writes for that call, in shape. The hash lets a signed receipt prove what was billed without holding the text.
{ "request_id": "req_3f9c…", "model": "deepseek-v4.1-flash-abliterated", "input_tokens": 1482, "output_tokens": 391, "charge_usd": 0.0019, "body_sha256": "a7c1…", "body_stored": false}Private does not have to mean filtered
A private chat app can run a stock model behind an encrypted pipe. The pipe is private; the model still declines. The builds here are abliterated or uncensored: the refusal behavior is edited out of the weights, so a medical, legal, security or drug-safety question gets an answer. Four general assistants, with prices from the live catalog on 2026-11-09 and the daily check verdict from /proof:
| Wire formats | |||||
|---|---|---|---|---|---|
| DeepSeek V4.1 Flash Abliterated | Abliterated | $0.8488 | $1.6975 | — | |
| GLM-5.3 Uncensored | Uncensored | $0.282 | $0.846 | — | |
| Qwen3.8 27B Uncensored | Uncensored | $1.25 | $3.75 | 33K | |
| Llama 3.3 70B Abliterated | Abliterated | $2.80 | $2.80 | 33K |
| Model | Daily check | 600 messages a month |
|---|---|---|
| DeepSeek V4.1 Flash Abliterated | Steady since Oct 19 | $1.17 |
| GLM-5.3 Uncensored | Steady since Oct 12 | $0.46 |
| Qwen3.8 27B Uncensored | Steady since Oct 29 | $2.03 |
| Llama 3.3 70B Abliterated | Steady since Oct 29 | $3.19 |
161 of the builds this site lists passed the daily check at render. All 172 builds this site lists are on the models page; the difference between abliterated and uncensored is one page, abliterated vs uncensored.
Best private AI server: self-hosting against a prepaid API
The fully private answer is a model on your own machine. Nothing leaves it, there is no host, no usage row, no email. The costs are the hardware and the model size: a 7B or 8B runs on a laptop, a 70B wants 40 GB-plus of VRAM, and the current 100B-plus open models do not fit a consumer card at all. Ollama, llama.cpp and Open WebUI are the usual stack; the Open WebUI guide shows that front-end on this key, and the two set-ups share a picker.
| Row | Self-hosted server | Prepaid API (UncensoredLLM) |
|---|---|---|
| Who sees the text | Nobody but you | The model host, in transit; not stored by the gateway |
| Model size | What your VRAM holds | Any build in the catalog, 70B and up included |
| Record kept | None, unless your front-end logs | One usage row per request, no body |
| Identity | None | An email, a balance and where your first visit came from |
| Cost | Hardware and power | Per token, table above; from $10 |
| Model identity check | The file on your disk | Daily fixed prompt, verdict on /proof |
A reasonable split: a small local model for anything you would not send anywhere, and the API for the questions that need a 70B or a current base. The same OpenAI-compatible front-end talks to both. The developer side, all four ways to run private AI and the open-weight builds you can later move in-house, is its own page.
Venice, Lumo and Duck.ai: the comparison, dated
The page-one results for "private ai chatbot" on 27 October 2026 were Lumo, Duck.ai, Privatemode, Venice, xPrivo, Confer, NoTrack and Bearly, plus a r/degoogle thread. Three are worth a row. Venice's cells were read 2026-10-19 and link rather than quote a figure. Lumo and Duck.ai describe their own storage on their own pages, linked in the first row.
| Row | UncensoredLLM | Venice AI | Lumo | Duck.ai |
|---|---|---|---|---|
| Billing | Prepaid from $10, per token, or one payment for a month of usage with no renewal | Subscription with daily credits, plus API prices (read 2026-10-19, pricing) | lumo.proton.me | duck.ai |
| Chat bodies stored | No, unless replay is on for a key (7 days) | See venice.ai | See its page | See its page |
| Account | Email, balance and first-visit source; playground turns need no account | See its site (read 2026-10-19) | See its page | See its page |
| Uncensored builds | 172 on the models page | Private chat app with an API (read 2026-10-19) | See its page | See its page |
| Model identity check | Daily, on /proof | See its site | See its page | See its page |
The longer Venice comparison, with a roleplay month costed on both sides, is the Venice page. The no-restrictions side of the question, every route to a model that does not decline, is AI with no restrictions.
Questions
This site cannot say. Venice publishes its own privacy policy and pricing at venice.ai, and the honest answer is to read those. What this key stores is listed in full on the privacy page; for a chat that is no bodies unless replay is on and one usage row per request. See the Venice comparison.
Fully private means the model runs on your own hardware; nothing leaves the machine. The next step down is a service that does not store the text: here prompts and replies pass through to the model host and are not written anywhere unless you turn on replay for a key, and the record kept per request is a usage row with token counts and a hash. The host that runs the model sees the text in transit in both the service case and any cloud case. See the privacy page.
A local model through Ollama or llama.cpp for anything that must not leave your machine, and for the rest a service whose storage you have read. On this key the playground runs with no account for a few turns a day, and a key needs only an email and a top-up from $10 or a usage plan. See the playground.
Yes, in the sense of a model that does not decline: the abliterated and uncensored builds above answer medical, legal, security and drug-safety questions. The limits that remain are the acceptable use rules, which are enforced on the gateway and listed in plain language. See AI with no restrictions.
The playground gives a few free turns a day with no account on the builds marked free. A local model is free after the hardware.
The one your VRAM holds: a 7B or 8B on a laptop, a 70B on 40 GB-plus of GPU memory. Open WebUI or a similar front-end talks to Ollama locally and to this API through a second connection, so a small local model and a large hosted one can share one picker. See the Open WebUI guide.
Every model above is on the uncensored model list with its live price per million tokens. Per-token pricing sets the whole catalog side by side, and the family directory groups the builds by base model.