Get help with your beta access.
Need to join
Use this if you have a beta invite or need help figuring out whether the invite path is still valid.
Need to recover access
Use this only if the account already exists. If the email does not match a beta account, the login flow will stop and point you back to Join Beta instead.
Need a build or product answer
Use this if the question is really about which client to use, posted builds, or current beta scope.
Can't access my invite code.
Invite codes expire and have limited uses. Ask whoever sent yours to confirm it's still active, then email us the code and we'll look it up.
Didn't get the magic-link email.
Check your spam folder first. If it still does not arrive within a few minutes, email support with the address you used so we can help confirm the request and restart sign-in.
Which client should I start with?
Use the web app when you need the fastest path or no install. Move to Android or desktop when you want the preferred daily experience.
What data stays on my device?
Private keys, DM history, private-content search, and new device-encrypted group history stay device-centered. Legacy group history, account metadata, and native attachment uploads still use hosted beta paths, so check the privacy page for the exact current boundary.
Still need help?
Email us directly — it's the fastest path. Expect a reply within 1–2 business days.
support@emberchamber.com
Invite or bootstrap problem
Include your invite code, the browser name you entered, and whether the problem happened before the email arrived or after you opened it.
Can't sign in
Email us the private email and browser name you used. We can confirm whether they match an existing beta account, help you restart sign-in, and tell you whether another session still looks active.
Broken page or in-app bug
Share the full URL, the last action you took, and a screenshot if the page rendered empty or partially. Note the approximate UTC time.
What to include
- The full URL where the failure happened.
- Approximate time (UTC if you know it).
- Any error code or digest shown on screen.
- Whether it reproduces after a page refresh.
Invite codes that aren't working
Codes can expire or run out of uses. Confirm with whoever sent yours that it's still valid, then email support with the code. We can look it up on our end.
Privacy boundary today
The shortest accurate answer is that private keys, DM history, private-content search, and new device-encrypted group history stay device-centered, while the hosted beta still keeps account metadata, signed attachment storage, and a few legacy compatibility paths. Browser and native attachment handling are not uniform yet.
Direct messages
Stays local: Private keys, DM history, and the private-content search index stay on the device.
Relay role: The relay stores account and conversation metadata plus ciphertext mailbox envelopes until they are acknowledged.
Current note: The relay does not serve plaintext DM history back to the browser.
Group history
Stays local: New groups are created with device-encrypted history and local client history.
Relay role: The relay coordinates membership, epochs, and mailbox delivery for new groups while legacy compatibility history still exists for older group and room paths.
Current note: Legacy relay-hosted group and room history still exists in compatibility paths and older data.
Browser attachments
Stays local: Browser encrypted-conversation flows can encrypt attachment bytes and keep file keys with the client before upload.
Relay role: R2 stores attachment blobs and signed access metadata so downloads can be delivered to authorized members.
Current note: This browser DM path is ahead of the native attachment path today.
Native attachments
Stays local: File selection, local cache, and local trust state remain with the client.
Relay role: Current mobile and desktop flows can still upload raw bytes to R2 through signed upload and download tickets.
Current note: Native attachment encryption is still being migrated and should not be flattened into the browser DM story.
Search
Stays local: Search over private message content stays local to the device.
Relay role: The relay exposes joined-space metadata search, not server-side search over private message bodies.
Current note: Search is local-first today, not a server archive feature.
Prefer to file a public bug report? Open a GitHub issue for reproducible bugs and technical problems.