Privacy by default

Discovery is public. Operational telemetry is summarized without publishing raw client IPs.

9192 is built to be discoverable by machines while keeping public reporting narrow: aggregate counts, anonymized client labels, route health and verification status instead of raw visitor identity.

Public reports

No raw IPs

Traffic summaries use hashed client labels such as ip_95c511c0a7d5. Public discovery snapshots expose route health and metadata status, not source addresses.

Local logs

Operator-local

Raw access logs are kept for security and abuse response on the operator machine. They are not part of the public repository or discovery package.

Sandbox

Anonymous test path

Free sandbox discovery and receipt verification do not require a funded account. Limits still apply to protect the service.

Paid execution

Explicit boundary

Paid execution is not anonymous: it uses quoted work, machine/account identifiers, funding state and receipts so clients can verify what happened.

What is published

route counts
status codes
latency summaries
user-agent summaries
anonymized client labels
discovery route health
DNS and metadata checks

What is not published

raw client IPs
TLS private keys
ledger internals
admin routes
operator secrets
raw access logs

Network anonymity

9192 does not claim to make a client invisible on the internet. It minimizes what is published and separates public discovery from private operations; clients that need network anonymity should use their own network privacy controls.