Privacy Policy - Battery Analyzer
Effective Date: December 1, 2025 | Last Updated: August 7, 2026
App and Developer Information
- App name: Battery Analyzer
- Package name:
com.tofabd.batteryanalyzer
- Google Play developer: AndroidCodeX
- Privacy contact: tofa.du@gmail.com
1. Introduction
Battery Analyzer (package name: com.tofabd.batteryanalyzer) is developed and published by AndroidCodeX ("we", "our", or "the developer"). This policy explains what information the app accesses, processes, collects, uses, and shares. Battery statistics and charging history are processed locally and are not transmitted to servers controlled by AndroidCodeX. Third-party Google services may process the information described below.
2. Summary at a Glance
- No account, login, or personal identity collected.
- Firebase Analytics & Crashlytics process app usage, purchase-event, device, diagnostic, and crash data to improve the app.
- Battery / performance metrics processed locally only.
- Ads provided via Google AdMob (may use Advertising ID).
- You can clear history in-app or uninstall to remove all local data.
3. Information the App Processes (Device-Local)
Collected/Read Locally for Display & Functionality Only:
- Battery level, status (charging / discharging / full), health, temperature, voltage, plug source (AC / USB / Wireless).
- Approximate instantaneous charging/discharging current (mA) derived from system battery properties.
- CPU temperature (when available via system thermal file) and available RAM snapshot.
- Charging session timing (start time, end time, duration, level change) stored as "history" entries.
- Charge-profile statistics, including battery-level ranges, sample counts, average current values, and session timing.
AndroidCodeX does not transmit battery statistics or charging history to servers controlled by AndroidCodeX. Depending on the user's Android backup and device-transfer settings, locally stored app data may be backed up or transferred by Android or Google as described in Section 6.
4. What We Do Not Collect
- No name, email, address, phone, contacts, calendar, photos, media, files, messages, or precise location.
- No background app usage patterns outside the metrics listed above.
- No biometric, health, or other sensitive personal data.
5. How Information Is Used Locally
- To display real-time battery and charging statistics.
- To generate on-device graphs and recent session summaries.
- To show a persistent foreground notification with current metrics (if enabled).
We do not sell user data. Google services integrated into the app may collect and process the information described in Sections 7, 8, and 9 for analytics, crash reporting, advertising, purchase processing, security, and fraud prevention.
6. Local Storage & Retention
- Charging and discharging history is stored in a local SQLite database and displayed for up to approximately the most recent 199 entries.
- Charge-profile sessions and battery-range statistics are stored in a separate local SQLite database.
- App settings, onboarding state, Pro entitlement cache, temporary monitoring state, and ad frequency counters are stored locally using Android preferences or DataStore.
- The History clear option deletes history records. The Charge Profile reset option deletes charge-profile records. Settings reset restores supported app preferences to their defaults.
- Because Android backup is enabled, eligible local app data may be included in the user's Google-managed Android cloud backup or device-to-device transfer, depending on the device and the user's settings.
- Uninstalling the app removes its active local app data. Data previously included in a Google-managed backup is controlled by the user's Google and Android backup settings and may be restored if the app is reinstalled.
7. Firebase Analytics & Crashlytics (Google)
The app integrates Firebase Analytics and Firebase Crashlytics to improve app stability and user experience. These services collect:
- App usage data (screen views, feature usage, session duration, settings changes, and ad interaction events).
- Pro purchase and restore events, including product identifier, displayed price, currency, purchase result, restore result, and whether Pro features are active.
- Crash reports and technical diagnostics (stack traces, device state at time of crash, app logs).
- Device and app information (model, OS version, app version, language, temperature-unit preference, and graph-mode preference).
- General geographic region (inferred from IP address, not precise GPS location).
This data is used solely to:
- Identify and fix bugs, crashes, and performance issues.
- Understand how users interact with the app to improve features.
- Monitor app stability and user experience metrics.
- Optimize ad placement and frequency.
AndroidCodeX does not use Firebase to request a user's name, email address, phone number, or contacts. Firebase may process app activity, device information, identifiers, diagnostic information, and crash data as described above. Refer to Google's policies for full details: Firebase Privacy & Security and Google Privacy Policy.
8. Advertising (Google AdMob)
The app integrates Google Mobile Ads (AdMob) to display native, interstitial, and app-open ads. AdMob may collect:
- Advertising ID (resettable), IP address, device information, coarse location (inferred), and performance metrics for ad delivery and fraud prevention.
Refer to Google's policies for full details: Google Privacy Policy. You may opt out or limit personalized ads via Android settings or https://adssettings.google.com.
EEA / UK / Switzerland Users: The app uses Google's User Messaging Platform (UMP) SDK to collect consent for personalized advertising in compliance with GDPR and IAB's Transparency and Consent Framework (TCF v2.2). Upon first launch or when consent expires, you will be presented with a consent dialog where you can:
- Accept personalized ads from Google and its ad partners
- Decline and receive non-personalized or limited ads instead
- Manage individual vendor purposes and preferences
Your consent choices are stored locally on your device and can be changed at any time through the app's privacy settings. For more information, see Google's Consent Management Platform.
9. In-App Purchases and Google Play Billing
Battery Analyzer offers an optional one-time Pro purchase through Google Play Billing. All payments are processed by Google Play. AndroidCodeX does not directly receive, process, or store users' credit card, debit card, bank account, or other payment method details.
The app may receive and process the following purchase information from Google Play:
- Purchased product identifier.
- Purchase status and acknowledgement status.
- Purchase token and transaction-related information provided by Google Play.
This information is used to confirm and acknowledge a purchase, unlock Pro features, and restore an existing purchase. The app does not send the Google Play purchase token or payment-method details to Firebase or to servers controlled by AndroidCodeX. However, the app sends purchase analytics events to Firebase Analytics, including the product identifier, displayed price, currency, purchase result, restore result, and whether Pro features are active. Purchase information is not sold or used for advertising by AndroidCodeX.
Google may process payment, account, device, and transaction information according to the Google Privacy Policy and Google Payments Privacy Notice.
10. Foreground Service & Notification
The app runs a foreground service to update battery statistics continuously and keep the notification active. This service does not transmit data externally; it only reads system battery APIs locally.
11. Permissions Used
INTERNET / ACCESS_NETWORK_STATE: Required for loading AdMob ads and sending anonymized Firebase data.
POST_NOTIFICATIONS: To show optional battery status notifications (Android 13+ runtime permission).
RECEIVE_BOOT_COMPLETED: To restart monitoring and restore notification after device reboot.
REQUEST_IGNORE_BATTERY_OPTIMIZATIONS: Opens an Android system screen where the user may exempt Battery Analyzer from battery optimization so optional continuous background monitoring is less likely to stop. The user makes this change knowingly and can reverse it from Android system settings.
FOREGROUND_SERVICE / FOREGROUND_SERVICE_SPECIAL_USE: To keep the monitoring service active with a persistent notification.
com.google.android.gms.permission.AD_ID: Enables access to Advertising ID for AdMob.
- No location permissions: We do NOT request or use
ACCESS_FINE_LOCATION or ACCESS_COARSE_LOCATION. Geographic region in Firebase is inferred from IP address only.
12. Security
- Locally stored app data is kept within Android's app sandbox, subject to Android cloud-backup and device-transfer behavior described in Section 6.
- AndroidCodeX operates no custom server for battery statistics, charging history, purchases, or user accounts. Network transmission is limited to the Google services disclosed in this policy.
- We do not implement additional encryption layers for local battery data because it is non-personal and confined on-device.
13. User Controls
- Disable or change notification permissions in Android system settings.
- Grant or revoke the battery-optimization exemption in Android system settings.
- Use the in-app reset/delete history option to clear session records.
- Reset the Advertising ID or limit ad personalization in system settings.
- Uninstall the app to remove all remaining local data.
14. Children's Privacy
The app is not directed to children under 13. We do not knowingly collect personal data from children. If you believe a child has provided personal information, contact us to request deletion (though the app does not require such data).
15. International & Legal Disclosures
- AndroidCodeX does not sell personal information.
- Google services may process information in countries other than the user's country under Google's applicable privacy and data-transfer safeguards.
16. Third Parties
- Google AdMob – Advertising delivery and measurement (see Google Privacy Policy).
- Google User Messaging Platform (UMP) – Consent collection for GDPR/TCF compliance (see UMP SDK Documentation).
- Firebase Analytics – Anonymous app usage analytics to improve user experience (see Firebase Privacy).
- Firebase Crashlytics – Crash reporting and diagnostics to improve app stability (see Firebase Privacy).
- Google Play Billing – Processing and managing the optional Pro purchase (see Google Privacy Policy).
- No other third-party SDKs (social, tracking, or advertising networks beyond Google) are integrated.
17. Changes to This Policy
We may update this policy to reflect feature changes or legal requirements. The "Last Updated" date will change upon revision. Material changes affecting user rights will be highlighted in release notes where practical.
18. Contact
Privacy questions or requests concerning Battery Analyzer may be sent to AndroidCodeX at tofa.du@gmail.com.
This Privacy Policy is hosted on GitHub Pages. For their data collection details, see the GitHub Privacy Statement and GitHub Pages Data Collection.