Identity boundary
SimpleX Chat avoids global user identifiers, which changes contact discovery, support, and recovery workflows.
private messaging app
Privacy-first messaging changes the operating model, not just the app icon.
Use the planner to turn upstream SimpleX Chat concepts into a concrete rollout, support, relay, and data-boundary decision.
Unofficial boundary
AGPL-3.0 source
v6.5.5 release noted
Workflow
What this page helps decide.
Data boundary
Messages and local profile data are device-owned; teams need backup, device-loss, and passphrase guidance before launch.
Metadata boundary
Relay choices, link previews, group discovery, and business workflows should be reviewed before inviting real users.
Decision matrix
What the planner checks before a rollout.
| Area | Question | Planner output |
|---|---|---|
| Identifiers | How will users connect without phone numbers, handles, or global IDs? | Invitation, address, and group workflow map. |
| Relays | Do preset servers satisfy the pilot, or does the team need self-hosted SMP relays? | Relay posture, domain checklist, and operations tasks. |
| Data ownership | Who owns backups, device loss, passphrases, and profile recovery guidance? | Device-owned data policy and support script. |
| Business support | Does customer support need business addresses, broadcasts, or bot handoff? | Support conversation model and moderation checklist. |