Yaarbal — privacy notice.

What seed-node operators see when you use the public reference network.

What's transmitted

Prompts you submit through chat.yaarbal.app or yaarbal run are sent to a public seed-node operator selected by the tracker. The operator's seeder process sees the full prompt text, model name, and output tokens. There is no end-to-end encryption between your client and the seeder — only Cloudflare edge TLS up to tracker.yaarbal.app.

What's stored

The tracker logs an ephemeral peer ID (a random uuid4 generated in your browser, stored in localStorage as yaarbal-ephemeral-peer-id-v1) alongside the credit-ledger entry for each inference request. The peer ID is not tied to your identity. Clearing your browser's localStorage rotates the ID and resets your browser-side credit balance.

Running your own seeder

If you don't want to send prompts to the public reference network, run a local seeder with yaarbal seed --model qwen2.5-0.5b-instruct and point chat.yaarbal.app's connection settings at http://127.0.0.1:7001. The reference network is demo-grade infrastructure — not production, no SLAs.