Lock the server address
Users cannot change the managed XMPP hostname or port, preventing an accidental or malicious move to a non-organization server.
Global Chat policy controls
SP-POLICY · SELF-HOSTED
One chat app. Different rules for every cohort.
Controlled without friction.
Create named policy templates for staff, contractors, field teams, kiosks, or high-risk users. SecurePhone applies the assigned posture when Global Chat returns to the foreground—without reinstalling the app or handing users a checklist of settings.
Named templatesPer-user assignmentRuntime enforcement
9:415G · 86%
Managed policySynced just now
ACTIVEServerchat.securephone.co
LockedScreenshotsNot allowed
OnRetention7 days
ActiveFederationOrganization only
ClosedSettings enforced by your organization
01Per cohortdifferent template for each population
02Foregroundruntime controls refresh when active
031 sourceadministrator-defined posture
04No reinstallcentral changes apply on refresh
Application posture
Close the settings that create data-leak paths.
Policy can lock identity, transport, capture, retention, and presence behavior while leaving the Global Chat experience familiar to the person using it.
Hide account-add controls
Keep the install single-account so personal XMPP identities cannot sit alongside the organization account inside the same app.
Restrict cross-org messaging
Limit conversations to identities in the same customer organization when a closed deployment is safer than open federation.
Block screenshots and recording
Android FLAG_SECURE blocks screenshots, screen recording, and readable recent-app thumbnails across managed chat surfaces.
Auto-delete after N days
Set a retention window so local message history older than the policy limit is removed automatically from the device.
Push a default status message
Apply a standard presence note for compliance language, on-call rotations, operational instructions, or brand tone.
Policy lifecycle
Define once. Apply continuously.
Policies become a reusable operational control instead of a setup document that drifts as users change settings.
Create a named template
Start from the threat model for a role or cohort and select the app controls that belong to it.
Assign users
Attach the template to each user or customer that should inherit the same posture.
Devices refresh
Global Chat retrieves current policy during its normal lifecycle and applies supported runtime controls.
Change without reinstalling
Edit the template centrally; assigned devices adopt the new posture on their next refresh.
App policy vs. device policy
Control Global Chat here. Control Android at the next layer.
These controls shape Global Chat itself. Camera, microphone, location, Bluetooth, screen-lock, and system-app restrictions require the managed-device layer provided by SecurePhone MDM.
See device managementNo Device Owner authority
Runtime app controls do not grant Android Device Owner permissions.
Refresh is required
A device must reconnect and refresh before receiving a changed policy.
Capture has physical limits
Screenshot blocking cannot stop someone from photographing an unlocked screen with another camera.
Archives are separate
Retention removes local history; server archive behavior is governed separately.
Turn requirements into posture
Build a policy people do not have to remember.
Map roles, retention rules, federation boundaries, and capture requirements into reusable SecurePhone templates.
Configure yours