02 / MICROPHONE PROTECTION

The microphone follows trust, not just place.

Compare a customer-approved Teams meeting with an unknown background request from an installed app. Passive policy checks apply even while the screen is locked or off and the phone remains powered. This browser shows example decisions; deployment verifies the actual device result.

02 / MICROPHONE TRUST

Approve the meeting. Block the unknown request.

Microphone rules apply inside and outside protected zones. An install-time permission is not a permanent exemption: approved meetings may use audio, while social or other apps outside policy are denied. Niwaban watches permission events, not conversations.

01 / DEVICE CONTEXTChoose a request

Try an approved call or an unknown background request.

02 / MICROPHONE REQUESTApp identity matters

No request selected.

03 / POLICY DECISIONPermission rule ready

The configured rule checks which app is asking.

04 / DATA OUTCOMEAwaiting decision

This browser example does not inspect real audio or advertising data.

Choose a microphone request to see the policy decision.

Play a two-pulse vibration sound when a block occurs

Policy enforcement stays passive; the vibration sound is optional.

EXAMPLE DECISION RECORD

Choose a request to see the app, rule and outcome.

One policy across installed apps.

Approved meeting appAllowed during an authorised call.

Social app with an install-time grantDenied when it is not approved for microphone use.

Unknown background appDenied when it has no approved reason to use audio.

PASSIVE MONITORING AND BEHAVIOUR ANALYTICS Niwaban’s policy layer reviews supported app and permission events as a secondary security monitor, without recording conversation content. Behaviour analysis of unusual attempts is being added; configured permission rules make the allow-or-deny decision.

A targeted advert does not prove a phone listened. Screen-off protection applies while the phone is powered on; a fully powered-down device cannot run software policy. We verify per-app controls, optional haptics and device-reported outcomes on selected enrolled devices during deployment.

PAID DEPLOYMENT ENGAGEMENT

See the result on your devices.

We review your enrolled phone and watch, management service, locations and approved policy. We then configure the required integrations and stand up a demonstration for the agreed environment.

During the engagement, we inspect the command and device-reported result together. Available actions depend on the selected platform and enrolment mode.

Discuss your deployment ↗Read the enterprise FAQ →