TapNoiseIf you have installed a keyboard or typing app on your Mac, macOS may have asked you for Input Monitoring. The request can look alarming, because it sounds like something that watches everything you type. It is a sensitive permission, so it is worth knowing what it allows and how to judge an app that asks for it.
What Input Monitoring is
Input Monitoring is a privacy setting in macOS. You find it in System Settings > Privacy & Security > Input Monitoring. Each app you allow can watch your keyboard, mouse and trackpad across the whole system, even while you are working in other apps. You can switch access on or off for each app in the list.
Apple’s own warning on this page is the important part. If an app collects information from your input, that information is governed by the app’s own terms and privacy policy, not by macOS. Apple recommends checking those policies before you allow access.
So the permission itself is not the risk. The risk is an app that can see your input and does something with it you did not expect.
Why it is sensitive
An app with Input Monitoring can, in principle, see what you type. That is the reason macOS asks, and the reason you should not allow it casually. A keyboard sound app, a clipboard tool and a typing tracker can all want it, and their intentions are not the same.
What TapNoise uses it for
TapNoise needs Input Monitoring to hear key presses. Without it, it cannot play a sound for each key. The Settings page says so directly: “TapNoise needs it to hear key presses. It never sees what you type.”
Here is how that works, as far as the app’s code and its published notes describe it:
- It listens without changing input. TapNoise uses a listen-only event tap. It can see key presses, but it cannot change or block them.
- It reads key positions, not letters. It is told which key position went down, such as the third key on the second row, so it can pick a sound. It does not read the character, and it keeps only counts such as taps today.
- It makes two kinds of network call. One checks your license key with the payment provider. The other is a daily check for updates. There are no analytics.
What TapNoise does not use
TapNoise also has optional features that use Accessibility. This is a different permission. Knock commands can send keys such as play and pause, Clean Mode holds your input for a set time, and the shortcut cheat sheet reads the menus of the app in front of you. Each has its own permission and its own switch. You can decline Accessibility and still use the key sounds.
Check the privacy page for the full statement, since the policy is the thing to read.
How to judge any app that asks
You cannot audit every app. These questions cover most of the risk.
- Do you know what the app is for? If you cannot say why it needs to see your input, say no.
- Where did you get it? Download from the developer’s own site or a store you trust, not from a link in a message.
- Does it say what it reads and what it sends? A clear statement is a good sign. A vague one is not.
- Does it need the permission to do its main job? A keyboard sound app does. A calculator does not.
- Can you turn it off? You should be able to revoke the permission at any time.
How to check and remove it
To see which apps have access, open System Settings > Privacy & Security > Input Monitoring. Switch off any app you no longer use, or remove it from the list. Without the permission, TapNoise cannot hear key presses, so the key sounds stop.
If TapNoise is missing the permission, its Settings page says “Input Monitoring is off” and shows an Open Settings button. That is the same list, so you can switch it on there.
The short answer
Input Monitoring is safe when the app you give it to is one you trust, does what it says, and keeps your input to itself. TapNoise is built to listen only to key positions, keeps counts instead of text, and makes only two kinds of network call. You can read the privacy page and decide. If you are not sure about any app that asks, the answer is no until you are.