Daimond Daimond Guide

Safety & fixes

Your account is a passphrase

On first run Daimond generates a passphrase of eight random words and shows it once. It is the key to everything stored here. It is not sent anywhere, it is not stored in the clear, and nobody can reset it.

It unlocks everything encrypted here, meaning your provider keys, your mail credentials and the account's own signing key, and the key that seals the sync parcel is derived from it too. The signing key is what signs you in for credits. Forget the passphrase and the encrypted data is gone.

Once a passphrase is in place you can add a passkey for a faster unlock, by face, fingerprint or security key. It unseals the passphrase for you instead of replacing it, so the passphrase stays the fallback. The unlock happens on the device, and the credits service only ever sees a public key.

The account controls

Your name is at the top of the account area, at the foot of the rail.

Beside them, Syncing turns this device's sync on or off, and Diagnostics shows and copies the app's own log, which holds event names and a clock, with no keys, no message text and nothing from your files. That log is what to paste into a report.

Moving your account

Your account is a signing key held in this browser. The passphrase does not recreate it, and only decrypts the copy stored here. So the same passphrase in a fresh browser starts a separate account, with its own credits and no Pro.

The key itself has to travel, and three things carry it.

Do one of them before you retire a browser. Once its storage is gone, with no backup taken and no other device linked, the key is gone with it.

A backup holds your work in the clear and your key wrapped under your passphrase. Importing the file alone makes nobody you. Whoever holds the file and the passphrase holds the account, which is why the two should not travel together.

More than one person on one browser

One browser can hold several accounts, each with its own chats, keys, credits and files. ＋ Add another account makes a second, and the row above it switches between them. Switching locks the first and forgets its keys before opening the other. Nobody sees another account's data.

What Daimond asks before it acts

A chip beside the model says what Daimond does without asking. It has three settings, and they apply to the whole app.

Under Guarded, once a turn has read something written by somebody else, such as a web page, an email or a build log, anything it then wants to fetch or send is put to you first, and a command in that turn runs with the network refused. That is the case where text you did not write could talk Daimond into carrying your work somewhere.

Switching to Bypass asks once, and says what you give up. No mode moves the fence a command runs inside, a diamond's folders, the system-call filter, or the log you can read afterwards.

An agent working on its own is asked about separately. Clicking something on a page can spend money or submit a form, and none of that can be taken back, so a click by an unattended agent is put to you even under looser settings.

Money has its own brakes, and they are on Spending.

What stays private

Your passphrase, provider keys, mail credentials, chats, diamonds and files live in this browser and are not sent to us. What we hold is money and ciphertext, meaning your balance and licences and, for sync, a parcel we cannot open.

Your messages reach a model provider directly with your own key, or through our metered service when you spend credits. Fetching a page, and syncing or sending mail, pass through the gateway. So the honest claim is that with your own key nothing of your work reaches us in the clear, and that you can watch only ciphertext leave for our servers.

You need not take that on trust. The code running in this browser is public, it builds byte for byte from that source, and every build served is sealed into a published record. Verify this build, in the About dialog, checks the one you are running. Open your browser's network panel and watch where the calls go.

The protection has limits. A passphrase guards against someone opening the browser's developer tools, and not against a compromised browser, a malicious extension or a keylogger, which defeat any in-browser scheme. And what a remote server does inside itself cannot be proven from outside, which is why it is the client that is opened to you.

When something goes wrong

Still stuck? The rail holds a diamond called Neil, which answers from this build and this guide and says which page an answer came from. What it cannot answer belongs on Social, with the three things a note needs.