Skip to main content
Link’d DMR

Security and privacy

Access is enforced behind the radio

The operator experience stays simple because the service checks account, device, organization, site, and managed-channel authority before cellular communication is allowed.

01

Account and device authorization

A valid account session, registered Android device, active organization assignment, and channel membership must agree before cellular access is granted.

02

Scoped customer administration

Owners, managers, dispatchers, and employees receive different permissions. Customer Command users see only organizations and sites assigned to their account.

03

Immediate access changes

Suspending or removing a member revokes managed channel access instead of waiting for a future reporting cycle.

04

Bounded operational visibility

Command exposes coarse presence and current-speaker metadata. It does not provide location tracking, private keys, owner recordings, or silent customer-audio monitoring.

05

Audited management actions

Invitations, member lifecycle actions, organization profile changes, and other sensitive operations create an append-only Business audit trail.

06

Fail-closed communication

Unsupported or unverified RF, gateway, identity, and access paths remain unavailable instead of displaying a false successful transmission.

Privacy boundary

Operational visibility is not silent surveillance.

Customer Command is designed for scoped metadata: coarse online state, team membership, and the current authorized speaker. It does not add employee location tracking or expose passwords, session cookies, private keys, owner recordings, or a hidden customer-audio monitor.

Important beta boundary

Link’d Business is a communications beta, not a certified life-safety, emergency-dispatch, or guaranteed-coverage system. Organizations remain responsible for approved emergency procedures and required radio systems.

Read the privacy policy