Privacy Policy

This policy describes how the Android application Sensor Tester (pl.halun.android.sensortester), developed by Jakub Hałun, handles data. Last updated: 11 November 2026.

In short: sensor and battery readings stay on your device. The application is free and shows ads from Google AdMob, and it measures its use with Google Analytics for Firebase. These Google services collect some data from your device, as described below. Where the law requires it, you are asked for consent first, and you can change your choice at any time.

1. Data that stays on your device

Sensor and battery readings are read only while the application is open. They are shown on the screen and are not saved. The application does not send them anywhere, and it stops reading the sensors when you leave it. When you choose Copy to Clipboard, the readings shown are placed on the system clipboard.

The application stores on your device your Preferences (which sensors are shown, and the availability filter), and a usage count for Google Play's rating prompt. Google's consent service stores your consent choices on the device as well. If backup is turned on, Android may copy this data to the backup of your device in your Google account and restore it when the application is installed again. Clearing the application's data or uninstalling the application removes the data from the device, but not necessarily a copy already in a backup; backups are managed in the backup settings of your device and your Google account.

The application has no user accounts. It does not ask for your name, email address, date of birth or location.

2. Advertising: Google AdMob

A banner ad from Google AdMob is shown at the bottom of the screen. To show ads, to measure them and to prevent fraud, the Google Mobile Ads library collects the following data from your device and sends it to Google, which may share it with advertising partners as far as your consent allows (section 4):

• the IP address, which may be used to estimate the general location of the device,
• device identifiers: the advertising ID, the app set ID and, where applicable, identifiers related to signed-in accounts on the device,
• interactions with the application and the ads, such as application launches, taps and ad views,
• diagnostic information, such as the performance of the application and the library, launch times, hangs and energy use,
• reports of crashes and errors that involve the Google Mobile Ads library itself, when Google turns this reporting on: the error, its stack trace and technical details of the device and the application.

Whether ads are personalized depends on your consent where it is required (section 4) and on the ad settings of your device, where you can also reset or delete the advertising ID.

3. Usage statistics: Google Analytics for Firebase

Google Analytics for Firebase measures how the application is used with the events its library records automatically. In this application these are: the first launch after installing (first_open), sessions (session_start) and the time the application is in the foreground (user_engagement), the screens viewed (screen_view), updates of the application and of Android (app_update, os_update), removal of the application and clearing of its data (app_remove, app_clear_data), campaign parameters when the application is opened with them (firebase_campaign), and events about the AdMob ads: requests, impressions, clicks and the time ads are on screen (ad_query, ad_impression, ad_click, ad_exposure, adunit_exposure). Each event carries the application version and the screen it happened on. Analytics uses an app instance ID and the advertising ID, and it derives a coarse location from the IP address. The application logs no events of its own and sends no sensor readings to Analytics.

Google signals is turned off for this application. When it is on, Analytics associates the data it collects with information from the Google accounts of signed-in users who have turned on Ads Personalization, for example for reports across devices and for demographics. Because it is off, Analytics does not collect signed-in account information for this application.

Analytics deletes event-level data 2 months after it is collected, and user-level data, which is tied to the app instance ID and the advertising ID, 2 months after your last use of the application. Standard aggregated reports, such as the number of users per day, are not affected by these settings.

Analytics starts only after the application has checked whether consent is required. Where it is required, nothing is sent before you make your choice. If you consent, Analytics collects the data described above. If you do not consent, it sends only cookieless measurement without identifiers, as Google's consent mode provides.

4. Consent and your choices

In the European Economic Area, the United Kingdom and Switzerland, the application shows Google's consent form on the first launch, before any ad is requested or any statistics are sent. It offers Consent, Do not consent and Manage options, where you can choose individual purposes and partners. Some advertising partners may process data on the basis of legitimate interest; you can object to that under Manage options. If you do not consent, the application still shows ads, and Google uses your data only as far as your choice allows, for example for non-personalized or limited ads.

You can change your choice at any time with Privacy options in the menu of the main screen or of a sensor's details screen. The item is shown whenever the consent form applies to you.

Outside these regions no consent form is shown: ads are requested and usage statistics are collected from the first launch.

5. Permissions

The application never asks for a permission while you use it: reading the sensors and the battery needs none. It declares only permissions that Android grants at installation:

Internet access and network state: for the ads, the consent form and the usage statistics; the Google libraries check the connection before their requests.

Advertising ID: access to the advertising ID, subject to your consent and your device settings.

Permissions added by the Google libraries: Android's Privacy Sandbox advertising interfaces (advertising ID, attribution and topics) where the device offers them, keeping the device awake and running background work to deliver their data, and Google Play's install referrer, which tells how the application was installed.

6. How the data reaches Google

The application itself opens no network connections. The data described in sections 2 and 3 is collected and sent by Google's libraries, over encrypted connections, and processed by Google under its own policies:

Google Privacy Policy

How Google uses information from sites or apps that use its services

Privacy and security in Firebase

7. Your rights

Depending on where you live, you may have the right to access, correct or delete your personal data, to object to its processing and to withdraw your consent. You can change or withdraw your consent with Privacy options, reset or delete the advertising ID in the settings of your device, and remove the data stored on the device by clearing the application's data or uninstalling it. Because the application has no accounts, the developer cannot look up data by your name or email address; for the data collected by Google, see the Google policies above. You may also lodge a complaint with your data protection authority.

8. Changes and contact

In version 2.0.0 and later, the About screen of the application links to this policy. When the application changes how it handles data, this policy is updated and the date at the top changes. If you have any questions or concerns, please contact me at jakubhal@gmail.com.

Account Deletion

Sensor Tester does not offer user accounts, so there is no account to create or delete. To delete the data the application stores on your device, clear its data in the Android settings or uninstall it.