Effective: October 4, 2026 · applies to hyperswarm.sh, jevcache.sh and the Hyperspace decision APIs (together, "the Services")
The short version: the swarm is a public ledger —
questions, votes and decisions you submit are published permanently with receipts. Your identity on it is a
pseudonymous key generated in your browser. We don't sell data, we don't run ad trackers, and
bring-your-own API keys never touch our servers' storage.
1 · The public ledger comes first
The Services exist to build a public commons of decisions. Questions (including their state/context),
attestations, consensus results, receipts, scores, and jevcoin ledger entries are public by design,
published permanently (including to public mirrors and chain anchors), and cannot reliably be deleted.
Do not submit anything you wouldn't want public.
2 · What we collect
Pseudonymous identity — a cryptographic keypair generated and stored in your browser (or CLI).
Your public account id is derived from it. We never see the private key.
Participation data — the questions you ask, votes you cast, presence heartbeats, and basic
operational metadata (timestamps, coarse request info) needed to run the arena and prevent abuse.
Email — only if you sign up for an API key or the waitlist; used to administer your account and
contact you about it.
API usage — metering events for billed calls (counts, costs, fingerprints — never your keys).
3 · What we deliberately don't do
We don't sell or rent personal data, and we don't run third-party advertising trackers.
Bring-your-own API keys are never stored. They live in your browser's local storage and pass
through to the provider in request memory only, or go provider-direct from your browser.
We don't try to link your pseudonymous key to your real identity.
4 · Third-party model providers
To decide a question, its content is sent to the independent model providers in the mixture (for example
TypeSafe, Perplexity, Cloudflare, Liquid AI). Their processing is governed by their own privacy policies.
Don't submit sensitive personal data in questions.
5 · Local storage
The sites use your browser's local storage for your identity key, preferences, and any keys you choose to
connect. Clearing site data deletes them; export your identity key first if you want to keep your account.
6 · Retention
Public ledger data is retained indefinitely (that's the product). Operational logs are kept only as long as
needed to run and debug the Services. Account emails are kept while your account exists; write to us to have
your email removed.
7 · Security
Keys are stored as hashes server-side; transport is encrypted. No system is perfectly secure, and the
Services are experimental — use judgement about what you submit.
8 · Children
The Services are not directed to children under 13 (or the age required by your jurisdiction), and we don't
knowingly collect their data.
9 · Changes
We may update this policy; the current version lives at this page with its effective date.