Privacy

Last updated 17 October 2026

Keypop is made by chewingcode (Karim Hossenbux). It has no account, no analytics and no tracking inside the app. It reacts to your keys as you type, and that’s where it stays: on your Mac. This page lists exactly what Keypop does with what.

What stays on your Mac

• What you type. Keypop sees each key as you press it, to play an effect, and forgets it. It never saves or sends the text you type.
• Your typing stats. For the recap, Keypop keeps counts per day: keys, words, deletes, your longest streak, time spent typing, keys per hour, keys per app and per effect, and your fastest burst. Counts only, never the text. They’re stored in a file in your Mac’s Application Support folder and kept for a little over a year.
• The recap image is drawn on your Mac. It only goes anywhere if you copy, save or share it yourself.
• Your settings stay in the app’s preferences on your Mac.

Permissions

• Accessibility (required) lets Keypop see keys as you type and find where your text cursor is.
• Screen Recording (optional) helps find the cursor in a few apps that don’t report it, such as some code editors and terminals. Screen images are looked at in memory, to find the cursor and whether the background behind it is light, and are never saved or sent.
• Password fields turn on macOS’s secure input, which hides those keys from every app, Keypop included.

What is sent, and to whom

• To check for updates, the app fetches its update feed from GitHub (Sparkle). The request includes the app and macOS versions, as any web request’s headers would.
• If you buy Keypop, Polar processes your payment and email under its own privacy policy.

That’s all.

This website

chewingcode.com counts visits with a self-hosted instance of Umami, which uses no cookies and keeps no personal data. The effects you try on this page run in your browser; nothing you type here is sent anywhere.

Questions

Write to hello@chewingcode.com. If this policy changes, the date at the top will too.