earbudtest
earbudtest
Earbud Test — Privacy Policy
Last updated: 2026-11-21
This privacy policy applies to the mobile app "Earbud Test" for Android:
- Google Play: package com.simonj.earbudtest, 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
Earbud Test does not require an account, and we do not sell personal information. The app checks the earbuds or headphones connected to your phone: it plays short test sounds through them and listens with the phone's own microphone to measure the audio delay (in milliseconds, with a range), to check whether the left and right channels are correct, swapped or mono, and to compare the level of the left and right sides and the playback range of different earbuds. It also plays listening tests (left/right, phase, frequency sweep, reference tones, noise, stereo pan and short voice samples). Your earbuds list and saved 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.
MICROPHONE
When the app asks: on first use, a card explains why the app needs the microphone, and Android asks for the permission only when you tap to allow it on that card. If you deny it, the listening tests (left/right, phase, sweep, tones, noise, pan, voice) still work, but the delay measurement, the automatic left/right check, the balance check and the response sweep cannot run; you can allow the microphone later in Android settings.
How it is used: the microphone is used only while a measurement or microphone check that you started is running. The app keeps a few seconds of microphone sound in the app's memory for each round, compares it with the test sound it just played to find the delay or the level, and then discards it. The microphone can also pick up other sounds around you, such as voices, during those seconds; they are processed the same way and discarded. The app does not record audio to a file, does not save the microphone sound, and does not upload it. Only the results described below are saved.
AUDIO OUTPUT AND SOUND SETTINGS
To show which output is in use, the app reads the type of the current audio output (for example Bluetooth, wired or the phone speaker) and the device name that Android reports for it. It does not use the Bluetooth permission, does not scan for or connect to Bluetooth devices, and cannot read the Bluetooth codec. The app may also read, without any permission, your phone's media volume level and, where Android provides them, the mono audio and left/right balance accessibility settings, so it can tell you when mono audio is on or remind you to compare earbuds at the same volume. It does not change these settings; when it suggests checking mono audio, it can open the Android settings screen for you.
INFORMATION STORED ON YOUR DEVICE
Earbuds: up to 30 earbud profiles, each with a name (the output device name Android reports, or a name you type instead), the output name and type, and when it was created and last used. You can rename a profile.
Results: up to 300 results; when you save more, the oldest results are removed. A result holds its type (delay, left/right check, balance or response sweep), its earbud profile, the time, an optional mode label you choose or type (for example "game mode"), and its values: for delay, the median, range and number of rounds, the phone-speaker baseline and the added Bluetooth delay; for the left/right check, the verdict and level difference; for balance, the level difference and its spread; for the response sweep, the relative level of each frequency band. Each result also stores the audio sample rate and app version.
Baseline: one phone-speaker baseline measurement (median, range, number of rounds, sample rate, time and app version), replaced when you measure it again.
The app may also store basic operating information such as your preferences (sweep speed, automatic left/right repeat, whether the volume warning and introduction have been shown), counts of completed actions used to space ads and review requests, a launch count, the remove-ads purchase state, cached advertising settings and a cached More Apps list.
The developer does not run a server that receives your results or microphone sound. The app reads developer-controlled advertising settings and a More Apps list from Google Cloud Firestore. It does not upload your results, earbud names or labels 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.
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 count), screen views, splash events (splash_ad_shown, splash_ad_skip, splash_timeout, splash_ad_late, with timing and the reason an ad was skipped), menu_open, privacy_policy_open, more_apps_open, review_from_menu and review_from_exit, review prompt events (review_prompt_shown, review_accepted, review_request_skipped, review_success_moment), ad_revenue (ad format, value, currency and precision), and the app's own events: perm_mic (granted, denied or blocked); baseline_start and baseline_result (number of rounds, the baseline median and range in milliseconds, sample rate); latency_start (output type, whether a baseline exists); latency_result (output type, number of rounds, the delay, range and added delay rounded into bands, match quality); latency_fail (reason, round) and latency_abort (round); lr_check_result (verdict, level difference band); balance_result (difference and spread bands); response_sweep_result (number of usable bands, sample rate); listen_play (test type, sweep speed); mono_hint_open_settings; earbud_save and label_set (count, label type); compare_view (comparison type, whether the result was the same); share_card (card type, outcome); and the purchase events listed below; plus app version, device type and app-instance identifiers. These events do not include microphone sound, earbud or device names, or the labels you type.
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 screens above the tab bar, including while a test runs. Full-screen ads may appear when the app opens or returns to the foreground, and occasionally between tests, for example when you switch tabs. The app asks the ad SDK to play ads muted. 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.
REMOVE ADS PURCHASE
You can buy a one-time "Remove ads" purchase on Google Play (earbudtest_remove_ads), or one of two optional support tiers with the same effect (earbudtest_remove_ads_2x, earbudtest_remove_ads_4x). Payment is handled by Google Play; we do not receive your card details. The app stores an ad-free 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. When ad-free, the app stops requesting banner and full-screen ads; the More Apps list is still 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. Purchase analytics events: remove_ads_tap (tier), remove_ads_picker, remove_ads_purchase_done (tier), remove_ads_purchase_fail (error code), remove_ads_restore and remove_ads_auto_restore (whether a purchase was found), remove_ads_nudge and remove_ads_nudge_tap (shown, tapped), and remove_ads_revoked.
ADVERTISING CHOICES
Each time the app starts, it refreshes Google's consent information (UMP) and, where consent is required (for example in the EEA and UK) and a choice is needed, shows Google's consent message. For a returning user whose stored choice from an earlier session allows ad requests, an app-open ad may be requested with that stored choice while this refresh is still running. After the refresh, ads are requested only if Google's consent framework allows ad requests; personalized ads are requested only where Google reports that consent is not required or your choices allow them, and otherwise ads are non-personalized. 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. The app works whatever you choose. Analytics and crash reporting are not controlled by these advertising choices.
OTHER PERMISSIONS
Apart from the microphone, the app does not request camera, location, contacts, photos, Bluetooth, phone, health data or notification permissions. Its Android package also declares internet access, the advertising ID permission and Google Play billing for the services above, audio-settings access used by the audio player, and vibration for short haptic feedback. Storage permissions that a library would otherwise add are removed from the package.
STORAGE AND YOUR CONTROL
Measuring a new baseline replaces the old one, and when the results list is full the oldest results are removed. To remove all of the app's data, clear the app's storage in Android settings or delete the app. On Android the app allows system backup, so local data may be included in a Google or device backup depending on your settings; uninstalling normally removes the active copy but may not remove an older backup.
When you share a result card, the app creates an image (the result with its range, such as the delay, baseline and added delay, the output type and name, any mode label, the round dots and the suggested game offset) and passes it through the system share sheet to a destination you choose. If you export your history as a CSV file (where the app offers it), the file contains your saved results with their earbud names and labels. These files are written to the app's cache and can remain there until Android clears it; the app does not delete copies you shared elsewhere.
We do not receive your saved results, so we cannot delete those local records for you; the controls above remove them from your device. 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 earbud profiles and results 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, and it never uploads microphone sound. 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
Earbud Test is not a hearing test and is not a medical device; it checks your earbuds, not your ears. If you are worried about your hearing, see a hearing professional. Keep the volume moderate: start high-frequency tones, sweeps and noise at a low volume and turn it up slowly, and do not listen at high volume for long. Results depend on your phone's microphone, the room, how you hold the earbud to the microphone and the phone's own audio processing. Delay values are measurements with the range shown, the added Bluetooth delay is an estimate, and the response sweep shows relative levels heard by this phone's microphone, not the true sound output of the earbuds.
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