IR Remote Tester — Privacy Policy
Last updated: 2026-10-27
This privacy policy applies to the mobile app "IR Remote Tester" for Android:
- Google Play: package com.simonj.irtester, 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
IR Remote Tester does not require an account, and we do not sell personal information. The app uses your phone's camera to look for the infrared flash of a remote control, turns the test into a verdict (for example remote working, batteries or button contacts suspected, or the TV side), lets you test single buttons, and, on phones with a built-in IR blaster, can send a few TV codes so you can check whether the TV reacts. Your results and settings 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.
INFORMATION STORED ON YOUR DEVICE
For each saved result the app keeps an ID, the date and time, the remote type, an optional remote name you type, the verdict and its confidence, the flash pattern that was seen, whether the result was confirmed by eye, how many tested buttons worked out of how many, and the answer you gave in the Phone IR TV check. The app keeps up to 50 results; when a new result would go over this limit, the oldest one is removed. If the saved results cannot be read when the app starts, the app keeps a copy of that unreadable data in its storage before it saves new results.
For each camera (back and front) the app records whether it has seen an infrared flash, the strongest detection value and when it was recorded, and which camera you last used. It also stores your settings (beep, vibration, detection threshold and the TV brand you last picked), whether your phone reported a built-in IR blaster and its supported carrier frequency ranges, whether the introduction has been shown, counters used to space out ads and the in-app review request, an app-launch count, cached advertising settings, and a cached More Apps list.
A check that has not reached a verdict, and button results you collect on the Buttons tab without an open result, are kept only while the app is running.
The developer does not run a server that receives your results. When ads can be requested, the app reads developer-controlled advertising settings from Google Cloud Firestore, and when you open "Developer's other apps" in the menu it reads a list of the developer's apps (the cached list is refreshed when it is more than 24 hours old) and loads app icons from the web addresses in that list. The app does not upload your results, remote names or camera frames.
CAMERA, IR BLASTER AND PERMISSIONS
Camera: the app asks for camera access when you tap "Allow camera" on a camera screen (the test step of Diagnose, or the Buttons tab). While a test runs, the app takes low-resolution still pictures one after another, reads only the centre area of each picture on your device to measure brightness, and uses the picture's orientation data to place the detection marker. Each still is written to the app's cache and deleted right after it has been analysed; if that deletion does not complete (for example if the app is closed at that moment), a still can remain in the cache until Android clears it. Stills are not saved to your photo library or uploaded. The flash is turned off during tests. If you deny camera access, the camera tests do not run, and the app shows a button that opens Android settings; the History, Phone IR and other screens still work.
IR blaster: the app uses the Android IR transmit permission, which Android grants at installation without a prompt. When the app starts, it asks Android whether the phone has a built-in IR emitter and which carrier frequencies it supports. The app sends an infrared code only when you pick a brand and tap a key (power, volume up or mute) on the Phone IR tab. Phones without a built-in IR emitter cannot send codes.
The app does not request microphone, location, contacts, Bluetooth, or notification permissions, and it does not ask for access to your photos. It uses internet access and the Android advertising ID permission for the services below, and vibration for haptic feedback.
ANALYTICS, CRASH REPORTING, AND ADS
Google Firebase Analytics may process limited app-usage and technical information, such as app launches with a launch count, and screen and tab views; the remote type you pick and when a camera test starts, finishes (flash pattern, frame-rate and frame-count ranges, a false-alarm flag), fails or is abandoned; answers in the by-eye check and the number of follow-up questions; the verdict, its confidence and whether it was saved; actions on the verdict screen; camera permission results, camera switches, camera start errors and the first infrared detection on a camera; single-button tests (button, result and whether the camera was confirmed); the working-remote comparison (step and strength band); whether the phone has an IR blaster and how many frequency ranges it reports, the TV brand and key you send, whether sending worked, and your answer whether the TV reacted; setting changes (beep, vibration, threshold range); result deletions, opened FAQ items, the introduction, shares and their outcome (image, text or failed); menu and More Apps opens and in-app review steps; when a full-screen ad was due, when the launch ad step ran, and when an ad on return to the app was skipped (with a reason); ad revenue events (ad format, value, currency and precision); app version, device type, and app-instance identifiers. These events do not include remote names, camera pictures or detection values.
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 Diagnose start and result screens, the Phone IR tab and the History tab. Full-screen ads may appear when the app opens or returns to the foreground, and occasionally when you act on or leave a result or switch tabs, after a result has been saved while the app is open (not after the first result you save in the app). Ads are played muted. AdMob may also request ads from the InMobi mediation network. Google and InMobi 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.
ADVERTISING CHOICES
When the app opens, it checks Google's consent message (UMP) before it requests any ads, and the Google Mobile Ads SDK is started only after this check and only if ads can be requested. If you answer the consent message (for example in the EEA and UK), personalized ads are requested only if your choices allow them. Where Google reports that consent is not required, ads may be personalized. In other cases, ads are non-personalized. If the consent result does not allow ad requests, the app does not request ads in that session unless you change your choice through "Privacy choices". If the consent check fails (for example the message cannot be loaded), the app still requests non-personalized ads, and "Privacy choices" is not 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. Firebase Analytics and Crashlytics are not controlled by this choice. The app works whatever you choose.
STORAGE AND YOUR CONTROL
On the History tab you can delete a saved result after a confirmation; if that result is still open on the Diagnose screen, later changes to it are not saved. You can rename a result on its verdict card or clear its name. On the Buttons tab, "Clear results" clears the current button results, and in the History tab settings you can turn the beep and vibration off and reset the detection threshold. The camera records, saved settings and the other stored information listed above have no separate delete button; you can remove them, together with the results, by clearing the app's data in Android settings or by uninstalling the app. The app is configured to exclude its data from Android cloud backup and device-to-device transfer.
When you share a result, the app saves a picture of the result card in the app's cache and opens the system share sheet so you can choose a destination. The picture shows the remote type, the remote name if you entered one, the verdict, its confidence, the date and time, the evidence, notes and next steps. If the picture cannot be made, a short text with the app name, verdict, confidence, remote type and date is shared instead. When the app starts, it removes shared pictures in its cache that are more than 24 hours old, and unfinished temporary files; a file that cannot be removed may stay. The app does not delete copies you shared elsewhere.
Because we do not receive your results, we cannot delete them for you; the controls above remove them from the app. For questions about data processed by Google or InMobi, 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 ensure that third-party service providers with whom we share user data provide the same or equal protection of that data as stated in this policy.
- 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
- InMobi Privacy Policy: https://www.inmobi.com/privacy-policy
SECURITY
Your results, settings and cache files 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. 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 collects to what is described in this policy.
IMPORTANT NOTICE
A verdict is a likelihood, not a certainty. Many phone cameras filter infrared, so a camera may not see a working remote; distance, angle, lighting and flickering lamps also affect the result, and the comparison with another remote only gives a rough relative value. The app cannot read a remote's code or measure its signal strength, and it cannot test Bluetooth or radio remotes. The TV codes sent from the Phone IR tab cover a few brands and may not match every model. Handle batteries as their maker instructs, and stop using a remote with leaking or swollen batteries.
CHILDREN
The app is intended for users aged 18 and over and is not directed to children. 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