Privacy Policy
Battery — Privacy Policy
Privacy Policy
Effective date: October 2, 2026
1. Introduction
This Privacy Policy explains how information is accessed, processed, stored, transmitted, and otherwise handled when you use Battery (the “Application”).
Battery is developed and provided by Marek Hovorka, operating under the developer brand MH Softworks.
Battery is primarily designed to process battery information locally on your device. Certain third-party services integrated into the Google Play version of the Application, particularly Google advertising, consent-management, and billing services, may independently process information as described below.
2. Data Controller and Contact Information
For processing for which the developer determines the purposes and means, the responsible developer/data controller is:
Marek Hovorka
Stavařská 735
686 05 Uherské Hradiště
Czech Republic
Privacy contact: hello@mhsoftworks.com
“MH Softworks” is used as a developer and trading brand and does not, for purposes of this Privacy Policy, refer to a separate legal entity.
3. Information Processed by Battery
3.1 Battery and device-state information
To provide its core functionality, Battery accesses technical information made available by the Android operating system concerning the device’s battery. Depending on the device and Android implementation, this may include information such as:
- battery temperature;
- battery charge level;
- charging and power-source status;
- battery health status reported by Android;
- voltage;
- battery technology; and
- battery-current, charge-counter, energy-counter, or similar battery-related measurements where made available by the device.
This information concerns the technical state of the device and is used to provide battery monitoring, graphs, historical information, alerts, and related Application functionality.
The Application does not intentionally treat battery-status information as medical or health information about the user.
3.2 Local measurement history
Battery stores selected battery measurements locally in the Application’s private storage so that measurement history and graphs can be displayed.
The stored history may include timestamps, battery temperature, charge level, charging or power status, battery health status reported by Android, voltage, and battery-technology information.
This measurement history is not transmitted to a server operated by Marek Hovorka or MH Softworks in the Application configuration covered by this Privacy Policy.
3.3 Application settings and operational state
Battery stores Application preferences and operating information locally. This may include settings such as temperature units, appearance, monitoring and alert preferences, measurement state, onboarding state, session information, advertising-removal entitlement caching, temporary ad-free status, and language-related preferences.
3.4 Local diagnostic information
If certain Application errors occur, Battery may write technical error information, including an exception description or software stack trace, to a file in the Application’s private local storage for diagnostic purposes.
This diagnostic file is not automatically uploaded to the developer in the Application configuration covered by this Privacy Policy.
3.5 Advertising and related information
The Google Play version of Battery uses the Google Mobile Ads SDK (AdMob) to display advertising.
Depending on the user’s device, region, consent choices, Google service configuration, and applicable law, Google and advertising-related services may process information such as:
- IP address and information from which a general location may be estimated;
- interactions with the Application or advertisements, such as application launches, taps, and video views;
- diagnostic and performance information;
- Android advertising identifiers;
- App Set ID; and
- other device or account-related identifiers where applicable.
Such information may be processed for advertising, advertising measurement, analytics, fraud prevention, security, and related purposes.
The transmission and subsequent processing of information by Google or other authorized advertising providers are subject to the terms, privacy notices, consent choices, and legal responsibilities applicable to those services.
The developer does not receive full direct access to all information processed by Google’s advertising infrastructure merely because the Google Mobile Ads SDK is integrated into Battery.
3.6 Consent information
Battery integrates Google’s User Messaging Platform (“UMP”) to obtain and apply privacy and advertising choices where required.
The consent interface presented to a particular user may depend on the user’s region, applicable legal requirements, Google’s configuration, and the advertising choices available at that time.
Where a privacy-options entry point is required by the applicable Google consent configuration, Battery makes that option available within the Application.
3.7 Purchases
Battery uses Google Play Billing for purchases such as removal of advertising.
Google Play processes the payment transaction. The developer does not receive users’ complete payment-card or bank-account credentials through Battery.
The Application may receive and process transaction-related information made available by Google Play, such as product identifiers, purchase state, purchase tokens, and entitlement status, to determine whether a purchase is valid, acknowledge the transaction where appropriate, and provide the purchased feature.
In the Application configuration covered by this Privacy Policy, such purchase verification does not transmit the purchase token to a developer-operated purchase-verification server.
Google Play’s own processing of payment and transaction information is governed by Google’s applicable terms and privacy documentation.
3.8 Communications with the developer
If you contact the developer voluntarily, for example by email, the developer may process the information contained in your communication, your contact details, and related correspondence to respond to your request, maintain appropriate records, protect legal rights, or comply with applicable law.
4. Local Processing and Storage
A substantial part of Battery’s functionality is performed locally on the user’s device.
Battery measurement history, preferences, session information, and local diagnostic information described above are stored in Application-private storage and are not, in the configuration covered by this Privacy Policy, synchronized to a developer-operated cloud service.
The audited Application configuration disables Android backup and device-to-device transfer for Application data.
Because this information normally remains on the user’s device, the developer generally cannot access, inspect, recover, correct, or delete that local information remotely.
5. Purposes of Processing
Information is processed only where relevant to purposes including:
- providing Battery’s core monitoring, graphing, history, notification, and preference functionality;
- maintaining the user’s Application configuration;
- providing and restoring purchased functionality;
- displaying and managing advertising;
- managing legally required privacy and advertising choices;
- maintaining security and preventing fraud or abuse;
- diagnosing Application errors;
- complying with legal obligations;
- establishing, exercising, or defending legal claims; and
- responding to communications or requests submitted to the developer.
The Application does not use locally stored battery-measurement history for independent advertising profiling by the developer.
6. Legal Bases for Processing
Where the General Data Protection Regulation (“GDPR”) or another law requiring a legal basis applies, the applicable legal basis depends on the processing activity.
Processing may be based on:
Performance of a contract or steps requested by the user where processing is necessary to provide requested Application functionality or a purchased feature.
Consent where legally valid consent is required, including for certain advertising, personalization, device-storage, or similar activities. Where processing is based on consent, consent may be withdrawn in accordance with the mechanisms made available for the relevant processing, without affecting the lawfulness of processing carried out before withdrawal.
Legitimate interests where applicable, including proportionate interests in securing the Application, preventing fraud or abuse, maintaining reliable operation, responding to communications, and establishing or defending legal claims, provided such interests are not overridden by the user’s rights and freedoms.
Compliance with legal obligations where processing is necessary to comply with applicable law or legally binding requirements.
A legal basis is not relied upon more broadly than permitted by applicable law.
7. Advertising
Battery may display advertisements through Google Mobile Ads / AdMob, including formats such as banner, interstitial, rewarded, rewarded-interstitial, and app-open advertisements.
Advertising requests are subject to the privacy and consent state provided through the integrated Google consent mechanisms.
Depending on applicable law and the user’s available choices, advertisements may be personalized, non-personalized, limited, or otherwise restricted.
Users may also obtain advertising-free use through functionality offered by Battery, including eligible purchase or rewarded-ad mechanisms where available. Suppressing future advertisements does not itself require or guarantee deletion of information that was previously processed by Google or another provider under its own applicable retention rules.
Google and participating advertising providers may process information under their own privacy policies, contractual terms, and applicable legal responsibilities. To the extent permitted by applicable law, the developer is not responsible for independent processing carried out by a third-party provider outside the developer’s control, but this does not limit any responsibility that applicable law imposes on the developer.
8. Analytics and Diagnostics
The audited version of Battery does not integrate Firebase Analytics or Firebase Crashlytics as separate services.
However, the Google Mobile Ads SDK may process Application-interaction and diagnostic information for analytics, advertising, and fraud-prevention purposes.
Battery also maintains the local diagnostic information described in Section 3.4. Local diagnostic information is not automatically transmitted to the developer in the configuration covered by this Privacy Policy.
9. Third-Party Services
The Google Play version of Battery integrates services provided by Google, including:
- Google Mobile Ads / AdMob;
- Google User Messaging Platform; and
- Google Play Billing.
These services may process information directly between the user’s device and Google infrastructure.
The nature of Google’s legal role may depend on the relevant service, processing activity, contractual terms, and applicable law. Nothing in this Privacy Policy is intended to assign Google or the developer a legal role different from the role that actually applies.
Users should review Google’s applicable privacy information and service terms for further information regarding Google’s processing practices.
10. Data Sharing and Disclosure
The developer does not transmit Battery’s locally stored measurement history to a developer-operated server in the Application configuration covered by this Privacy Policy.
Information may nevertheless leave the device through integrated third-party services. In particular, advertising-related information may be transmitted directly to Google and relevant advertising providers through the Google Mobile Ads SDK and related infrastructure.
Transaction-related information is processed through Google Play in connection with purchases.
Information that is actually held by the developer, such as correspondence voluntarily submitted to the privacy contact address, may also be disclosed where reasonably necessary and permitted or required by applicable law, including to:
- comply with a legal obligation, court order, or legally binding request;
- protect rights, property, or security;
- investigate fraud or abuse;
- establish, exercise, or defend legal claims; or
- obtain professional legal, accounting, or technical assistance subject to appropriate obligations.
The developer does not create an unrestricted right to disclose information and will process such information subject to applicable law.
11. International Data Transfers
Google and other third-party service providers may operate infrastructure in multiple countries and may process information outside the country in which the user is located.
Where international transfers are subject to legal restrictions, the relevant provider and, where applicable, the developer must use the safeguards required by applicable law and the applicable service arrangements.
This Privacy Policy does not represent that a particular international-transfer mechanism applies where that mechanism has not been established for the specific processing operation.
12. Data Retention
Local measurement data
The current Battery configuration uses a nominal 30-day retention period for historical measurement samples. Samples forming part of the currently active measurement may be retained beyond the nominal history window where necessary to preserve that active measurement.
Local information may also remain until Application storage is cleared or the Application is uninstalled, subject to the behavior of the user’s device and operating system.
Preferences and Application state
Local preferences, configuration values, and Application-state information are generally retained until they are changed, Application storage is cleared, or Battery is uninstalled.
Local diagnostic information
A local diagnostic report may remain in Application-private storage until it is overwritten by later diagnostic information or the Application’s local data is removed.
Google and other third parties
Information processed by Google or another independent third-party service is retained according to the rules and policies applicable to that provider and service. The developer does not promise a retention period for third-party systems over which the developer has no technical control.
Communications
Correspondence sent directly to the developer may be retained for as long as reasonably necessary to respond to the communication, maintain appropriate records, protect legal rights, resolve disputes, prevent abuse, or meet applicable legal obligations.
13. Data Deletion
Battery does not create a developer-operated user account.
Users can remove locally stored Battery data through Android’s application-storage controls. Clearing Battery’s application storage removes its local database and locally stored Application preferences. Uninstalling the Application will normally remove its app-private local data from the device.
Removing local Battery data does not necessarily delete records maintained independently by Google in connection with Google Play purchases, advertising services, or other Google services.
Users may use the privacy, advertising-identifier, Google-account, or other privacy controls made available by Android and Google for information controlled through those services.
For personal data actually held by the developer, users may send an applicable privacy request to hello@mhsoftworks.com. Requests are handled subject to identity verification where reasonably necessary and to the conditions, limitations, exemptions, and lawful retention requirements provided by applicable law.
Because locally processed Battery information is ordinarily not received by the developer, the developer cannot remotely retrieve or delete information that exists only in the Application’s private storage on the user’s device.
14. Security
Battery uses measures appropriate to the nature of the processing reflected in the audited Application configuration.
These include use of Application-private local storage, disabling Application-data backup and device transfer in the audited configuration, restrictions on cleartext network traffic, and use of HTTPS/TLS for applicable network communications controlled by the Application.
Third-party services implement their own technical and organizational safeguards.
No method of electronic storage, transmission, software operation, device security, or network communication can be guaranteed to be absolutely secure. Nothing in this section excludes or limits any security obligation that cannot lawfully be excluded.
15. Data Protection Rights
Where the GDPR or similar applicable law applies, users may have rights including, subject to the relevant statutory conditions and exceptions:
- the right to obtain information about processing and access applicable personal data;
- the right to request rectification of inaccurate personal data;
- the right to request erasure;
- the right to request restriction of processing;
- the right to object to certain processing;
- the right to data portability where legally applicable;
- the right to withdraw consent where processing is based on consent; and
- the right to lodge a complaint with a competent supervisory authority.
The exercise of a right does not mean that every request must be fulfilled unconditionally. Applicable law may permit or require verification, restrictions, exceptions, or continued retention.
For users in the Czech Republic, the competent supervisory authority is the Office for Personal Data Protection (Úřad pro ochranu osobních údajů). Users may also have the right to contact another competent supervisory authority under applicable law.
Because most Battery measurement information remains exclusively on the user’s device, the developer may not possess information that could be produced, corrected, or erased remotely in response to a data-subject request.
Requests concerning personal data controlled by Google or another third-party provider may also need to be directed through the privacy mechanisms provided by that provider.
16. Children’s Privacy
Battery does not require users to create a developer account or provide their age as part of its core functionality.
The Application is not designed to solicit profile information from children. Where applicable law requires parental consent or other special protections in relation to a minor, those requirements must be observed.
A parent or legal guardian who believes that personal data relating to a child has been provided directly to or is otherwise controlled by the developer may contact hello@mhsoftworks.com.
Third-party advertising and consent services may be subject to additional age-related requirements under applicable law and platform rules.
17. Third-Party Links and External Content
Battery may open external websites, including developer information, Privacy Policy, or Terms pages, through the user’s browser or another application capable of handling web links.
Websites and services operated by third parties are governed by their own terms and privacy practices. The developer does not control the content, security, availability, or privacy practices of independent third-party websites, except to the extent responsibility cannot lawfully be excluded.
18. Changes to This Privacy Policy
This Privacy Policy may be updated from time to time to reflect changes in Battery, applicable law, regulatory requirements, third-party services, or data-processing practices.
The effective date displayed at the beginning of the Privacy Policy will be updated when the policy is revised.
Where applicable law requires additional notice, consent, or another procedure for a material change, the required procedure will be followed.
19. Contact
Questions, requests, or concerns regarding this Privacy Policy or processing carried out by the developer may be directed to:
Marek Hovorka
Stavařská 735
686 05 Uherské Hradiště
Czech Republic
Email: hello@mhsoftworks.com