Attestation & receipts

Check the enclave's quote, the key that signs your transcripts, and the receipts it issues, with tools that do not depend on us. Then read what this page does not prove.

Where your audio and content go, and which companies handle them, is the trust and subprocessor disclosure.

Fetching a quote…

Is this a real enclave?

How to check it yourself

Paste the quote hex into the TEE Attestation Explorer, which checks Intel's signature chain and breaks the quote into its registers.

Or ask Phala's verifier from a terminal, with QUOTE set to the hex above; quote.verified is true for a genuine quote:

curl -s -X POST https://cloud-api.phala.network/api/v1/attestations/verify -H "Content-Type: application/json" -d "{\"hex\": \"$QUOTE\"}" | jq .quote.verified

Or check it offline with Phala's open-source verifier:
```
dcap-qvl verify --quote-hex "$QUOTE"
```

Is the quote fresh and bound to our signing key?

The server puts sha256(nonce ‖ its signing public key) into the quote's report data, so a quote carrying this page's fresh nonce was made just now, by the machine holding that key.

Which key signs your transcripts?

The same key is published at GET /v1/transcript-seal-key on the API host, together with any retired keys.

Check a receipt

Every transcript version and every redaction is sealed: signed by the key above in a receipt envelope (conclave-seal/v1 for transcript versions, conclave-redaction/v1 for redactions). Receipts are verifiable by anyone holding the public key.

What is signed is the canonical bytes of the payload: UTF-8 JSON, keys sorted, no whitespace, with a schema field as a first-class key.

The receipt verifier runs in your browser, nothing is uploaded, works for any Conclave envelope.

Where your words are processed

Summaries, knowledge and answers are generated by NEAR AI's confidential inference. Conclave fetched NEAR's attestation report with its own nonce and checked it; what follows is reported as received.

Fetching NEAR's report…

What this page does not prove

The registers are not checked against a published image digest or compose hash. The quote proves a genuine Intel TDX machine running dstack with this key inside it, not that the measured code equals this repository's source.
Summaries, knowledge and answers are generated by NEAR AI's confidential inference. Conclave checks NEAR's enclave quotes above but does not verify the signature on each answer, does not check the GPU evidence, and reports NEAR's gateway TCB status as NEAR's collateral gives it, without judgement.
Speech-to-text runs outside the enclave: words come back, a voiceprint never leaves.
The in-person recording stream's TLS certificate proves control of the domain, not the enclave.
This page is served from Vercel, not from the enclave. The published key id above comes from this page's source, which is why comparing it with the live key is a check and not a tautology.