Privacy policy

InputConfig never transmits anything. Everything it records stays on your Mac.

What stays on your Mac

Settings, presets, calibration data and usage statistics are stored locally, inside the app's own container. The usage statistics are counts the app keeps for its own Statistics panel: how long a controller was connected each day, which presets were activated and for how long, and how many times each button was pressed. They never leave your Mac, and Reset in the Statistics panel clears them.

What the app reads

To do its job the app reads the controls you have mapped: controller buttons and sticks, MIDI messages, and, for rows bound to them, keys and clicks from the Mac's own keyboard, mouse, and trackpad. Input is matched against your presets as it happens and is not recorded, apart from the per-control counts above and a short activity log of the actions it fired, which stays in memory and is saved only if you save it yourself.

The activity log and Save Report

The app keeps a short activity log of what it did, in memory only. It is written to a file only when you press Save Report. That file holds the app's actions (which button fired which output; any text it types, website it opens, or Shortcut it runs is counted in characters, not written out), your preset and device names, your settings, and when presets started, stopped, or switched. It goes only where you send it.

For automatic preset switching the app checks which app is in front, to compare it with the apps you listed. Which app it was is not stored or logged.

The tip jar

Tips in the tip jar are in-app purchases handled entirely by Apple. The app learns only whether a purchase went through, never your payment details.

Network access

The app makes no network calls in normal use. There are no analytics, no crash reporting services, no tracking, and no accounts. The only links that leave the app are the ones you click yourself, such as the source code on GitHub or the tip jar on the Mac App Store, which Apple handles.

Permissions

Accessibility lets the app send keyboard and mouse events to other apps, and read your keyboard, mouse and trackpad for rows that use them as inputs; without it, mappings cannot fire. Input Monitoring is needed only for a controller that also presents itself as a keyboard, such as some arcade sticks. Bluetooth is used only when you disconnect a controller from the app, and macOS may ask about it then. Controllers and MIDI devices are read without any permission prompt.

Contact

Questions go to the project's issue tracker.

Last updated October 3, 2026.