Controller input
PadProbe reads input from the physical controller the user selects while the app is connected to it. Live button, stick, trigger, and D-pad values are processed on the Mac so the user can identify, test, calibrate, and translate that controller.
PadProbe does not transmit raw controller input, gameplay input, macros, or live test activity to Gamertan or another service.
Local profile data
A saved profile can contain the controller's hardware identifiers, observed report layout, button assignments, axis calibration, inversion, deadzones, and user-created macros. Profiles are stored locally under the user's Application Support folder and can be backed up or removed by the user.
PadProbe does not put game accounts, Minecraft worlds, server addresses, Steam accounts, or gameplay history into controller profiles.
Network and third-party apps
PadProbe does not use the network for accounts, analytics, advertising, cloud synchronization, remote input, or controller-profile uploads. A user can ask it to launch another installed application such as Minecraft Launcher or Steam. Once launched, that application operates under its own privacy policy and network behaviour.
Apple may process App Store distribution, purchase, diagnostics, or storefront information under Apple's own terms. PadProbe does not receive live controller or gameplay input from Apple.
Children and family use
PadProbe does not create user accounts or intentionally collect personal information from children. Its original use case is family game time, which is one reason controller configuration remains local and separate from game accounts.
Changes and questions
If a future PadProbe feature needs network access or changes what data is stored, this page and the release notes will describe that boundary before the feature is presented as part of the public product. A support contact will accompany the first public App Store listing.