Why messengers link phone numbers
Most mainstream messaging applications utilize your phone number as a primary identifier. While this design allows apps to easily scan your address book to show who is already online, it exposes your social graph, leaks account existence to anyone who saves your number, and links your digital conversations directly to a SIM card and real-world identity.
EmberChamber's invite-only model
EmberChamber replaces public phone-number scanning with an invite-only onboarding loop. To join a circle, an existing member must generate an invite code for you. You cannot sign up voluntarily without a valid, attested invite token.
Private email bootstrap
Instead of carrier-assigned phone numbers, EmberChamber utilizes email addresses during onboarding. This serves two roles:
- Session bootstrap: Delivering security magic links without relying on cellular SMS channels which are vulnerable to SIM swapping.
- Multi-device recovery: Enabling device linkage re-verification under a self-attested 18+ boundary.
Your email address is not searchable by other users in the system and is never used for public profile lookup.
No public user discovery surface
EmberChamber has no public user directory, search bar, or profile query endpoints. You are completely invisible to other members unless they share an active direct message channel or are joined in the same group chat.
What this does and does not protect
This approach protects you from bulk address book scanning, random spam invites, and identity correlation by third parties. However, it is not a shield against all metadata collection. The hosted edge relay still coordinates session tokens and email association, meaning the relay operator can verify that your account exists and is linked to a particular invite chain.
For more details on the data boundaries, review our Privacy Policy and Trust & Safety principles.