Privacy Policy

Your wallet address is the account. To open the workspace you sign a message (Sign-In with Ethereum). That signature proves you control the address. We then keep a session so you stay signed in.

In the workspace we store what you put there: messages, files you attach (and extracted text from documents), personas you write, the model a conversation uses, pins and titles, reply ratings, the auto-delete window you choose, a quiet activity count per month, and which browsers are signed in.

We do not ask for an email, password, name, phone number or card. Credit top-ups, if you make them, are USDC transactions signed by your wallet; we keep the transaction hash and the credit balance. For each reply we also keep a usage record — the model, the tokens read and written, whether the reply was included or paid, and the conversation it belongs to — to compute the allowance and the balance. The monthly totals appear in Settings. If the address has an ENS name or avatar, the workspace may show it by looking it up on Ethereum.

Your chats are encrypted when stored. Diogenes unlocks them when you open a conversation or ask the AI to respond. This covers messages, chat titles and saved web excerpts. Attachments and shared JAR Knowledge are not yet covered. Encryption is managed by Diogenes; it is not end-to-end encryption.

We do not sell conversations. We do not use them to train a public model. We do not send what you write to a public AI provider by default. We do not run advertising or analytics products on the workspace. We do not claim that models run on your device.

The browser talks only to Diogenes. The Diogenes API sends the conversation to a model endpoint we control — DigitalOcean Serverless Inference — and streams the reply back. The model sees the text, images a vision model can see, and extracted text from documents. The reply is stored with your account. PDF bytes are not sent to a third-party reader.

Some models use confidential inference through NEAR AI. This protects model processing inside a hardware-isolated environment: the Diogenes API sends the conversation over a connection pinned to that environment's attested key, and checks cryptographic evidence for the service before and after each reply. Diogenes still processes your messages before sending them to the model and receives the reply in the clear, as with any model. This is separate from encryption of stored chats and is not end-to-end encryption. It does not cover the browser, stored files or JAR indexes, which stay with Diogenes. A model you pick says so in the model list; Settings → Models shows the current verification state.

When you ask about an address, a transaction or a token and on-chain reading is offered, the model calls read-only chain tools: the addresses and hashes in your question go to the RPC endpoints we run against (Ethereum and any other network we configure) and, for prices, to DefiLlama. Nothing else from the chat goes with them, nothing is signed or sent on chain, and your signed-in wallet address is included only when you ask about your own wallet.

When you ask for a picture and image generation is offered, the model writes a short description and sends it to DigitalOcean's image model over the same endpoint; nothing else from the chat goes with it. The picture comes back to Diogenes and is stored as an attachment on the reply, for your account only. Like other attachments, it is not yet covered by the encryption of stored chats.

Personal API keys (Settings → API) let your own scripts use the same models as this app. We store only a hash of each key, its name, and when it was last used. Requests made with a key are stored as chats in your workspace, encrypted like any other, and count against your included tokens, credits and spending limit. Browsing is not offered through the API, and a key never publishes to a JAR by itself.

In a JAR, the JAR's instructions and its shared Knowledge are included in each model request for a chat in the JAR and sent to the same inference provider. Shared Knowledge is stored for that JAR and readable by all current members, including members who join later. Member wallet addresses are visible within the JAR. Your chat transcripts in a JAR are stored with your account and shown to no other member; Diogenes processes them to answer, as with any chat.

Removing shared content deletes it live for every member, subject to the backup window below. It cannot retract information already included in another member's answers, downloads or exports. Leaving a JAR does not remove what you published; the owner can remove it.

If you turn on auto-save in a JAR chat, each completed answer in that chat is published to the JAR's Knowledge under your address, for all current and future members. Your own messages and attachments are not published, but answers may repeat information from them.

If you paste a public web link or a site name and ask about it, the Diogenes API fetches that page from its own servers — the site sees a Diogenes reader, not you. The extracted text is stored with your chat, shown to no one else, and deleted with the chat.

If you ask it to explore a site — its navigation, filters or a dashboard — an isolated browser on Diogenes servers opens the public page you asked for. The site sees Diogenes, not your wallet, cookies or JAR Knowledge. Observed excerpts and filters stay with that chat and are deleted with it. Models receive page text and structure only, never screenshots.

A page that needs an account is never signed into for you. You may sign in yourself through a live view of that isolated browser, shown to your session only over an encrypted connection. Keystrokes and pictures from that view are relayed and not stored; password, code and card fields are blanked in anything a model could see; the assistant does not act until you confirm. The browser, with the site's cookies, is destroyed when you stop, disconnect, leave it idle for ten minutes or reach 45 minutes. Replies drawn from a signed-in page, and later replies in that chat, are marked as such and are never auto-saved to a JAR; publishing one requires your review.

DigitalOcean hosts the API, the database, file storage, the inference endpoint and this website. Your wallet software stays on your side; we never see the keys. If you connect through WalletConnect, that service is used only for the connection. A public Ethereum RPC is used to verify the signed message and, when present, to resolve ENS.

For a model marked confidential, NEAR AI operates the hardware-isolated inference service that receives the conversation for that reply. Diogenes checks Intel and NVIDIA attestation evidence for that service; the check itself does not send your content anywhere.

DigitalOcean holds the stored workspace and the inference request. The others see only what that piece of the path requires.

We set one first-party session cookie: Secure, HttpOnly, and used only to keep you signed in. It is not used for advertising. Signing out, or waiting for it to expire, clears it.

Conversations stay until you delete them, or until they sit idle longer than the window you set in Settings — 7, 30 or 90 days. Pinned conversations are kept. Deleting a conversation removes its messages and images. Shared Knowledge stays until its author or the JAR owner removes it, or the JAR is deleted. Deleted content leaves live storage at once; copies may remain in backups for a short time. You can export your chats or delete the workspace from Settings. A signed-in browser session keeps nothing beyond its own lifetime: only the reply text you saw, and which citations required a login, stay with the chat.

Export your data. Delete one conversation or all of them. Disconnect the wallet. Set auto-delete. Rate a reply — that verdict stays with the message.

Diogenes is not directed at children under 16. Do not use it if you are younger.

If this page changes in a material way, the date at the top will change with it.

There is no account email — the wallet is the identity. Use Settings to export or delete what we hold. The Terms of Use sit beside this policy.