Privacy Policy

Last updated: June 2026

dLLM is built to know as little about you as possible. This policy describes, honestly, the little we do handle — and the places where, by design, we can't see your data at all.

No account, no personal data

No name, email, phone, or sign-up. Your account is just a random access key; we store only a one-way hash of it, never the key itself, alongside your prepaid balance. We never ask for or hold any personal information.

Your IP address

dLLM is a normal website, so — like any site — our servers receive your IP address to send responses back. We do not link it to your key, your balance, or your conversations, and we don't use it for tracking or analytics. If you want to hide your IP from us as well, reach the site over a VPN or Tor.

Two kinds of models — and what we can see

Every model is labeled in the picker so you always know which applies:

• E2EE · decentralized — served by an independent worker. Your prompt is sealed to that worker, so we, the relay, never read it (beyond the one safety screen below) and neither does anyone on the wire. The worker that runs it does process your prompt to generate the answer — today those are our own machines; hardware attestation (in progress) will let you require that even a community operator can't read it. The reply is sealed back to you.
• Anonymous — a hosted "big model" (e.g. Venice) we resell. To generate the answer, your prompt is sent to that third-party provider. It is never tied to your identity or account, but it is not end-to-end encrypted: the model provider, and our coordinator in passing, process it in plaintext. Choose E2EE models for anything you want sealed.

Your chat history

If you save conversations, they are encrypted on your device and we store only the ciphertext, keyed to your account hash. We cannot read them, and neither can anyone who breaks into our servers. Your 12 words sync them across your devices; delete them anytime.

What we store

Only what's needed to run a prepaid, anonymous service:

• A one-way hash of your key and the credit balance attached to it.
• Aggregate token counts for billing — never the content of a prompt or reply.
• The encrypted form of any chat history you save (we can't read it).
• For top-ups: a payment address or reference tied to your key-hash, and the IDs of transactions already credited (so a payment is never counted twice). We accept Monero, Solana USDC, and crypto swaps.

Cookies

Two functional cookies, no tracking or analytics: ck (your access key — your login and balance) and theme (light/dark).

The one rule

dLLM is uncensored on every topic but one: no sexual content involving minors. To enforce it, every prompt — including those bound for E2EE workers — is screened for this before it is dispatched. This is the only inspection we perform; blocked requests are never processed.

What we cannot do

Because we keep only a hash of your key and only the encrypted form of your saved chats, we cannot recover your key, read your saved history, or connect a balance to a real-world identity — for you, or for anyone who comes asking. For E2EE models we also cannot read the live prompt or reply (beyond the one-rule screen). The privacy isn't a promise we make; it's built so we couldn't break it even if we wanted to. (The exception is the Anonymous tier above, where you've chosen to send your prompt to a hosted provider to answer.)

Retention & changes

Billing records (your balance and credited transaction IDs) are retained as needed for accounting. We may update this policy; continued use constitutes acceptance.