Understand what end-to-end encryption requires, what Thumper-Run protects today, and which private E2EE guarantees remain gated.

What is E2EE?

End-to-end encryption (E2EE) is a security property in which authorized endpoints, rather than the service relay, hold the content-decryption keys. That property requires more than encrypted transport or the presence of cryptographic primitives: client custody, membership changes, recovery, revocation, persistence, and release evidence must all work together.

Current Thumper-Run Boundary

Current supported network workflows use encrypted transport and layered authentication and authorization. Relay-assisted sync and deployment workflows are server-assisted. They must not be treated as private E2EE or as proof that the relay cannot access service data needed to provide those workflows. Local-only workloads remain on the device unless you enable a network or cloud feature.

BeeKEM Design Work

Thumper-Run includes BeeKEM/CGKA primitives and default-dark integration work for group membership, key rotation, and device admission. Those components are being tested as part of a future endpoint-held-key design. Their presence in the codebase is not a shipping private E2EE guarantee.

The design must prove additive member changes, stable Ed25519 identity, rotating X25519 leaf keys, durable encrypted custody, anti-rollback floors, removal denial, and restart recovery before the corresponding product claim can be enabled.

Data and Sync Today

Local apps and outputs stay local until you choose a sync, sharing, or cloud action.
Network connections use TLS where supported, which protects data in transit but is not end-to-end encryption.
Relay-assisted sync may expose content or keys required by the current server-assisted protocol.
Models and public artifacts may be downloaded again from their configured sources.

Private E2EE, relay-zero-knowledge behavior, production encrypted FileSync, group-convergent deduplication, and verifiable franking remain gated. The E2EE design and status page and security overview describe the current boundary and the evidence still required.

Identity and Recovery

Device pairing and recovery can authorize identities or restore supported key material, but neither action by itself establishes private E2EE for synced content. Back up local data using the supported export or backup path for the feature you use.

Ready to try it? Download Thumper-Run free →