Typing statistics vs keylogging: what is the difference?

Counts and speed estimates need less information than a record of typed text. Inspect the implementation and storage before trusting a typing utility's privacy claim.

A typing counter can count activity without storing the words you enter. A text logger records content. Both may use keyboard-related access, so the permission name alone does not distinguish their behaviour.

Ask what is retained

Useful questions include whether the app reads characters, stores key sequences, keeps timestamps, identifies apps or uploads a history. “Local” only describes location; a detailed local log can still be sensitive.

A speed estimate does not automatically require dictionary words. It can use a count convention, which is why a live WPM display may be less precise than a reference-text typing test.

TapNoise’s implementation

TapNoise passes key positions to its playback and counting logic and does not read typed characters. It stores local daily counts and progression data, with daily numbers retained for the documented 60-day window.

It does not turn those counts into a transcript of your work. Its agent messages likewise carry status information rather than the text of a conversation.

Keep the claim narrow

That is a description of TapNoise, not a guarantee about every app with a WPM badge. Review each utility independently and remove access when you stop using it.

For the number itself, read how WPM is calculated. For a broader permission review, use the Mac utility checklist, including network activity and the uninstall path.

Sources: TapNoise’s stored-data inventory, privacy policy.

About the author

Rudra Satani makes TapNoise. Spotted a mistake? Email support@tapnoise.com, or reach out at @rudraxx13.

Hear TapNoise on your Mac

Every sound is made by TapNoise itself. Try the sounds on the homepage first, then download the app.