Message encryption
OMEMO sessions protect supported one-to-one and group conversations across registered devices. Server administration does not automatically provide message plaintext.
SecurePhone security architecture
Security boundaries
you can understand.
SecurePhone separates message encryption, device authority, customer administration, infrastructure ownership, and commercial licensing so each control has a clear purpose and a visible limit.
01OMEMO encrypted chat02Customer-controlled servers03Explicit administrator authority04Signed updates and entitlements
Five distinct boundaries
Do not confuse encryption with administration.
Encrypted conversations, managed endpoints, server operations, customer lifecycle, and licensing are related systems—but they grant different authority.
Device management
Android Device Owner enrollment can apply system-wide policy and remote actions. Ordinary application installs do not receive that authority.
Infrastructure control
The customer or chosen operator controls the appliance hosts, network boundary, storage, backups, DNS, and provider accounts.
Customer administration
Commerce Hub controls accounts, subscriptions, resellers, balances, service status, modules, and lifecycle operations—not endpoint encryption keys.
Licensing authority
Signed entitlements define approved modules and active-user allowances. License expiry does not erase customer data or encryption keys.
Administrator transparency
Say exactly what each action can do.
SecurePhone product pages distinguish immediate server revocation, endpoint commands that require connectivity, chat-data wipe, and whole-device reset.
Revoke server access
Disable credentials and future service access from the control plane without claiming that an offline phone has already erased local data.
ExploreClear Global Chat data
Supported app-level erase paths target Global Chat credentials and local application data, not every file on an unmanaged phone.
ExploreReset a managed phone
Whole-device reset requires properly enrolled Android Device Owner authority, whether triggered remotely or through Panic Wipe.
ExploreOperate through outages
Signed offline licensing grace and customer-run infrastructure keep temporary loss of the SecurePhone licensing service distinct from loss of the appliance itself.
ExploreOperational security
The architecture is only the starting point.
Secure deployment also depends on enrollment, administrator access, DNS, backups, monitoring, incident procedures, and replacement-device recovery.
Deployment architecture
Separate Core, Realtime, and Mail when isolation or scale requires it.
ExploreServer requirements
Provision supported hosts, public addressing, DNS, external backups, and only the ports each profile needs.
ExploreDevice lifecycle
Plan enrollment, policy assignment, loss response, wipe scope, replacement, and reactivation before issuing phones.
ExploreArchitecture review
Map authority to your actual threat model.
Define users, devices, data, administrators, providers, failure modes, and recovery expectations before selecting modules and infrastructure.
Open the configurator