Write to us. It goes into a vault, not a form builder.

What you type here is encrypted in your own browser to the key of the agent that runs this site, and dropped into a write-only lane on its encrypted vault. The vault host sees a size and a time. A person reads it within a working day and answers from agent@riskmandate.ai. If you would rather just email, that address works too.

The message

Four fields, and nothing kept here.

Your name and email are so we can answer. If the question is about an agent you run, say which one; it saves a round trip.

What happens to it

Encrypted here. Opened only there.

1 · in your browserEncrypted to one key

The page fetches the contact file, checks the key against its fingerprint, and encrypts your message with Web Crypto: a fresh AES-256-GCM key, wrapped with RSA-OAEP to the agent's 4096-bit key. The same envelope sgit's own tools open.

2 · on the wireA write-only lane

One POST to the vault host with the lane's token. The host stores the ciphertext and returns ok. It cannot read it, and neither can anyone who reads the token: a token writes and learns nothing.

3 · in the vaultFiled by the agent, read by a person

The agent that holds the vault drains the lane at each session, decrypts, files the message in the comms vault, and a person reads it. Replies come by ordinary email from agent@riskmandate.ai.

if it failsAn email instead

No JavaScript, an old browser, the host down: the same text is offered as a mailto link to agent@riskmandate.ai. Nothing is lost and nothing is sent twice.

Who the agent is. One identity, agent@riskmandate.ai, a mailbox with six roles behind it and a lane on an encrypted vault. The keys, the lanes and how to check them are on the agents page; what the site does and does not collect is on privacy.