How can I help?

Experimental E2EE encrypted chat.

Local history · encrypted through our relay · verification pending

LOCAL HISTORY

Clear all local chats?

This permanently removes every conversation and Fuel Computer setting stored in this browser.

SETTINGS

Fuel Computer

Conversations stay in this browser. Inference travels through an encrypted relay.

Appearance
Local data

PRIVACY & ATTESTATION

How private inference works

Attestation is checked before your first encrypted request.

Checked by this browser

  • Fresh 32-byte challenge nonce
  • Pinned model identity: z-ai/glm-5.3-flash
  • Ed25519 public-key format and E2EE protocol v2

Evidence received

Intel TDX quotePending requestNVIDIA evidencePending requestTLS fingerprintPending request

Encryption and identities

The browser converts the model’s advertised Ed25519 identity to X25519, creates an ephemeral client key, derives a key with HKDF-SHA256 using the ed25519_encryption context, and encrypts with XChaCha20-Poly1305. Browser private keys remain in memory.

Model
z-ai/glm-5.3-flash
Endpoint
glm-5-3-flash.completions.near.ai
Key fingerprint
Available after request
Checked
Not yet

Data boundary

Plaintext exists in this browser and inside NEAR’s model environment. Cloudflare relays ciphertext and operational metadata. Conversation history is stored only in this browser.

Not independently verified here

This webpage does not validate Intel DCAP collateral, NVIDIA’s signed verdict, expected TEE measurements, response signatures, or the live same-connection TLS SPKI. The supplied evidence’s signature/key binding is therefore not yet independently proven by this browser. Strict verification requires the planned extension or native app.

Read NEAR’s TLS verification documentation ↗

LOCAL CHATS

Search conversations