Privacy and verification
This describes the actual state of the pipeline, not intentions. When stronger levels arrive, this section will change with them.
Privacy levels
Today P0 and P1 are active — transport encryption. P1 is not fully owner-blind yet: the gateway encrypts on your behalf and sees the plaintext itself, and sampled prompts may be revealed to verifier miners during checks. P2–P4 are locked in the selector and will open once the pipeline genuinely enforces them.
Answer verification
Answers are verified by the network selectively, so a request has honest statuses: pending — the check is in progress, verified — confirmed, flagged — a discrepancy was recorded, not_sampled — this request was not sampled. The status of a specific request is available by its id.
What analytics stores
Owner usage analytics is collected without content: counters, sizes, timings and response codes — request and response bodies are absent by construction. The request log is the same metadata.
Client IP
When checking a key’s IP allowlist, the client address is used only at the moment of the check in gateway memory: it is not written to logs and not passed on — neither to miners nor to analytics.