Skip to content
Beta terms

This beta is for controlled testing, not silent promises.

The current public site should set expectations clearly: capabilities will change, bugs are expected, and access is invite-only until the trust and recovery model is stronger.

Write the boundary plainly.
Keep the trust model specific.
Do not hide operational reality.

What beta access means

  • Access may be invite-only, delayed, revoked, or reset during testing.
  • Features may change quickly as the mobile, desktop, and relay layers are hardened.
  • Message history recovery after total device loss is intentionally limited in this architecture.

Operational limitations

Early builds may include degraded delivery, incomplete device-linking flows, or placeholder onboarding paths while the core secure-state logic is still being integrated.

Prohibited use

EmberChamber is not being built as a haven for malware, extortion, trafficking, CSAM, non-consensual abuse, impersonation, or platform attacks. Private by design does not mean permissive toward clearly illegal abuse.