TapNoiseTapNoise uses key positions and timing to build activity feedback. It does not need to read the characters in your document to count taps or estimate recent typing speed.
What the data can show
Local counts can show how much keyboard activity occurred on a day. Recent eligible key timing can produce a live speed estimate. Progression uses those events to update levels, streaks and hats.
These are different measures. A count includes activity, while a WPM estimate applies a convention to selected typing keys. Neither reveals whether the resulting passage is accurate or useful.
What is stored
The documented local data includes daily activity, speed history and progression. Daily numbers are retained for 60 days. Motion and lid readings are used as they arrive rather than kept as a recording.
The license lives in Keychain, separately from preferences and activity. Agent configuration backups are another local data category, with their own purpose.
Interpret a quiet day fairly
Reading, reviewing and planning may produce few presses. Treat the charts as a personal activity view rather than an employer-style measure of output or a reason to type unnecessarily.
For the calculation, see how WPM works. For the privacy distinction, typing statistics versus keylogging explains why you should inspect implementation and storage rather than relying only on a permission label.
Sources: TapNoise local data inventory, Tappy Stats controls.