TapNoiseA keyboard sound app does not need to record your microphone merely to play a sound for a key press. Keyboard observation, audio output and microphone capture are separate capabilities.
Ask what the feature does
A recorder needs microphone audio. A sound player needs an output. A utility that stays quiet during calls may only need to know that input is active, depending on its implementation.
Read the specific explanation rather than assuming every audio-related permission is interchangeable. If an app asks for access you did not expect, pause and identify the feature requesting it.
TapNoise’s quiet mode
TapNoise checks microphone activity for Quiet during calls. It does not listen to or store microphone audio for that decision. Its required typing permission is Input Monitoring.
Knock commands can also change the default microphone’s mute or input level where supported. Controlling a device setting is different from recording a stream, so test the behaviour and inspect the documented requirements.
Review actual permission lists
System Settings › Privacy & Security › Microphone shows apps with microphone access. Input Monitoring and Accessibility have their own lists. Grant only the permission needed for a feature you trust.
For visible activity, the orange dot explains what macOS reports. For TapNoise’s stored data and network checks, use the local-data guide rather than inferring privacy from silence during a call.
Sources: TapNoise call behaviour, Apple’s Privacy & Security settings.