gamepadtest
gamepadtest
Gamepad Test — Privacy Policy
Last updated: 2026-11-21
This privacy policy applies to the mobile app "Gamepad Test" for Android:
- Google Play: package com.simonj.gamepadtest, developer "Global Utility App Maker"
The app is developed and operated by Kyu-Hee Jang (Google Play developer name: Global Utility App Maker).
Contact: wkdrb2100@gmail.com
OVERVIEW
Gamepad Test does not require an account, and we do not sell personal information. You connect a real game controller (gamepad) to your phone by USB or Bluetooth, and the app shows its buttons, sticks and triggers live, measures stick drift, stick range (circularity), dead zone, trigger travel, button response, polling rate and an input-delay estimate, and lets you test the controller's vibration, light, motion sensors, battery level and touchpad where Android makes them available. Results can be turned into a dated test report. Your results are kept in the app's storage on your device. The app also uses Google services and an advertising mediation partner for analytics, crash reporting, remote configuration, and advertising.
CONTROLLER INPUT AND DEVICE INFORMATION
What is read: only while the app is open in the foreground, it receives the button presses and stick, trigger and D-pad values that Android delivers to the app's own window from connected game controllers, with their timestamps. From Android's list of input devices it reads each controller's name as reported by Android, its vendor and product ID numbers, its controller number, the axes and buttons it reports, and whether Android exposes vibration motors, lights, motion sensors, a battery level or a touchpad for it. To estimate whether a controller is connected by USB, the app checks whether a USB device with the same vendor and product ID is attached and whether the phone supports USB host mode. For the touchpad test it may also read pointer or touch movement inside the app's window. Reports include your phone's model name and Android version.
How it is used: raw input samples are kept in the app's memory while a test runs and are used on your phone to calculate the results; they are not uploaded. The app does not read input sent to other apps, and when it goes to the background it stops reading controller input, stops any vibration and releases the controller's light. Motion-sensor readings come from the controller, not from your phone, and are used only to show them live and to calculate a resting bias.
Output to the controller: when you start the vibration test, the app asks Android to vibrate the controller's motors, and when you start the light test, it asks Android to set the colour of the controller's light. The app uses only standard Android functions for this; it does not write to the controller's firmware and does not calibrate or repair the controller.
Bluetooth: the app does not request Bluetooth permission and does not scan for, pair with or connect to devices. Pairing is done in Android's own Bluetooth settings, which the connection guide can open for you.
INFORMATION STORED ON YOUR DEVICE
Controller profiles: for each controller the app recognises, it stores the axis assignment from automatic detection or the axis wizard (which axes are the left and right sticks and the triggers, and whether an axis is inverted), the motor labels you confirm in the vibration test, and when the controller was last seen. A profile is identified by the vendor and product ID and a short code derived from the controller's device descriptor; this code is not included in analytics or in report images. The app keeps up to 20 profiles and removes the least recently seen one when a new controller would exceed that.
Current check: the results of the tests you run are saved as soon as each test finishes, so the checklist stays after you switch screens or restart the app. When the current check is more than 6 hours old, the app starts a new one when you continue testing.
History: reports you save are kept in History. A report holds its time, the controller's name, vendor and product ID and estimated connection type, your phone's model and Android version, the app version, the verdict and measured values for each test, and the data needed to redraw the stick maps (the measured edge of each stick and up to 60 resting points and 4 return points per stick). History keeps up to 50 reports; when you save more, the oldest is removed, and if the stored history becomes too large, the app keeps only the 30 most recent reports.
The app may also store basic operating information such as your settings (button label style, display refresh rate, whether test screens keep controller buttons from also acting on the app's screens, your dead-zone setting, haptics), the times ads were last shown and counts used to space ads, review request progress, a launch count, the remove-ads status described below, cached advertising settings and a cached More Apps list.
The developer does not run a server that receives your test results or reports. The app reads developer-controlled advertising settings and a More Apps list from Google Cloud Firestore. It does not upload your results, reports or controller profiles as saved records; the analytics events described below can include limited, mostly rounded values derived from your use of the app, as listed there. When you open "Developer's other apps" in the menu, app icons are loaded from the web addresses in that list.
SHARING AND EXPORT
From the report screen you can share the report as an image or copy a text summary. The image shows the date, your phone's model, the controller's name and vendor and product ID, the verdict for each test and the stick maps; the text summary contains the same kind of information. You can also export the raw input log (the most recent 200 events: button codes, axis values and times) as a CSV file and the report as a PDF. Image, PDF and CSV files are written to the app's cache and handed to the Android share sheet for the destination you choose; the app does not delete them, and Android may clear them later. The app cannot delete copies you shared elsewhere.
PERMISSIONS
The app does not request any runtime permission: no camera, microphone, location, contacts, photos, Bluetooth, health or notification permission. It declares internet access, the Android advertising ID permission and Google Play billing for the services and purchase described below, and vibration for short haptic feedback on your phone (which you can turn off in Settings).
ANALYTICS, CRASH REPORTING, AND ADS
Google Firebase Analytics may process limited app-usage and technical information, such as app launches and sessions (app_launch, app_session with a launch counter), splash and ad events (splash_ad_shown, splash_ad_skip, splash_timeout, splash_ad_late, interstitial_pending_show, and ad_revenue with ad format, estimated value, currency and precision), menu_open, back_pressed, privacy_policy_open, more_apps_open, review request events (review_prompt_shown, review_accepted, review_request_skipped, review_success_moment, review_from_menu, review_from_exit), and the purchase events listed below. For the app's features it logs: pad_connected (vendor and product ID numbers, connection type, number of controllers, Android version), pad_disconnected (whether a test was running), pad_none_view (seconds waited), connect_guide_open (guide type), bt_settings_open, first_input (time from connection), test_start, test_abort (test and step), test_result (test, verdict and a rounded value range), mapping_wizard (result and changed axes), vibrate_test (whether supported, number of motors, whether you felt it), report_view, report_share and report_save (number of tests done and controllers), history_open and history_compare (count), screen_view (screen), setting_change (setting and value) and module_unavailable (Android version), together with app version, device type and app-instance identifiers. These events do not include controller names, the descriptor code, raw input samples or report images.
Google Firebase Crashlytics may process crash reports and related technical information needed to diagnose app problems.
The app shows ads through Google AdMob. A banner may appear at the bottom of the app's screens, including the live screen and the test screens. Full-screen ads may appear when the app opens or returns to the foreground, and occasionally after you finish a test and return to the live screen, close the report share sheet or open History. The app does not start a full-screen ad while a test is capturing input or the axis wizard is running. AdMob may also request ads from the Liftoff (Vungle) mediation network. Google and Liftoff may process advertising identifiers and device, app, consent, network, and ad-performance information to provide and measure ads, and may use an IP address to estimate an approximate location even though the app has no location permission. Google Mobile Ads also collects the Android App Set ID for purposes such as analytics and fraud prevention. App Set ID is not used for personalized advertising or advertising measurement, and it is not linked to Android identifiers (such as the advertising ID) or to personal and sensitive data for advertising purposes.
ADVERTISING CHOICES
Each time the app starts, it refreshes Google's consent information (UMP) and, where required (for example in the EEA and UK), shows Google's consent message. For returning users, an app-open ad may be requested during that refresh using the consent stored from the previous session. Where consent is required, personalized ads are requested only if your choices allow them; otherwise ads are non-personalized. Where Google reports that consent is not required, ads may be personalized. After a successful check, ads are requested only if Google's consent framework allows ad requests. If the consent check fails (for example, the consent message cannot be loaded), the app still requests non-personalized ads, and "Privacy choices" may not be shown until the app is started again. Where Google requires it, the menu shows "Privacy choices", which reopens the consent message so you can change your advertising choice; the menu also links to this policy. Analytics and crash reporting are not controlled by these advertising choices. The app works whatever you choose.
REMOVE ADS PURCHASE
You can buy a one-time "Remove ads" purchase on Google Play (product gamepadtest_remove_ads), or one of two optional support tiers with the same effect (gamepadtest_remove_ads_2x and gamepadtest_remove_ads_4x). Payment is handled by Google Play; we do not receive your card details. After a purchase, banner and full-screen ads are no longer shown. Ads may still be requested before the app has finished reading your saved purchase at start-up, or if that saved purchase cannot be read. The app stores a remove-ads status flag on your device. The app talks to Google Play when you buy or tap "Restore purchases", and checks ownership once each time the app starts; if that start-up check reports that no "Remove ads" purchase is owned (for example after a refund), the app turns "Remove ads" off and ads return, while a failed check keeps the saved purchase. There is no server-side receipt check. Purchase events sent to Firebase Analytics are remove_ads_tap (tier), remove_ads_purchase_done, remove_ads_purchase_fail (error code), remove_ads_restore and remove_ads_auto_restore (whether a purchase was found), remove_ads_revoked, remove_ads_nudge (whether the one-time offer was shown) and remove_ads_nudge_tap (whether you chose to buy).
STORAGE AND YOUR CONTROL
Running a test again replaces that test's result in the current check, and running the axis wizard again replaces the controller's axis assignment. Old reports leave History automatically under the limits described above. To remove all of the app's data, clear the app's storage in Android settings or delete the app. The app allows Android system backup, so local data may be included in a Google or device backup depending on your settings, and uninstalling the app may not remove an older backup.
We do not receive your saved results, reports or controller profiles, so we cannot delete those local records for you; the controls above remove them from the app. Clearing them does not delete analytics events or crash reports already sent, older device backups, or copies you shared elsewhere. For questions about data processed by Google or Liftoff, or to ask us for help with a privacy request, contact us at the address below.
Data processed by third parties is retained according to their service settings and policies. We use these services under their applicable terms, and we choose service providers whose privacy policies (linked below) describe protection of the data they process; Google and Liftoff process that data under those terms and policies.
- Google Privacy Policy: https://policies.google.com/privacy
- Firebase privacy information: https://firebase.google.com/support/privacy
- Google advertising technologies: https://policies.google.com/technologies/ads
- Liftoff Privacy Policy: https://liftoff.io/privacy-policy/
SECURITY
Your test results, reports and controller profiles are kept in the app's private storage on your device, which the operating system protects from other apps; they are not separately encrypted by the app, so protect your device with a screen lock. Apart from the limited analytics events described above, the app does not upload your saved data or controller input. Communication between the app and Google services and the ad mediation partner uses encrypted connections (HTTPS/TLS). No method of storage or transmission is completely secure, but we limit what the app processes to what is described in this policy.
IMPORTANT NOTICE
Gamepad Test shows the values that Android receives from the controller on this phone and this connection. Results depend on the controller, its firmware, the connection and the phone; a controller's own dead zone can hide small drift, and the verdicts use the app's own thresholds, which are guidance rather than a manufacturer's diagnosis. The input-delay value covers only the part measured inside the phone and does not include the controller, the wireless link or the screen, so the delay you feel is larger. The app is a testing tool only: it does not repair or calibrate controllers, and it is not a replacement for a repair service or the manufacturer's support. When you buy or sell a used controller, also check it yourself before you rely on a report.
CHILDREN
The app is not directed to children under 13, and we do not knowingly collect personal information from children.
CHANGES
We may update this policy if the app or its services change. The date above shows the latest revision.
CONTACT
Kyu-Hee Jang (Google Play developer: Global Utility App Maker)
Email: wkdrb2100@gmail.com