Manual capacity values
Design Capacity, Full Charge Capacity, and optional battery names entered into the manual calculator.
Data and privacy
Privacy Policy
This policy explains the main categories of information involved when a person visits CheckBatteryHealth, uses the manual calculator, submits a Windows battery report, or sends a contact message.
Privacy statements must match the deployed application. The site should not describe uploaded report processing as local-only when the report is submitted to an analysis endpoint.
Information categories
Information involved in using the site
Uploaded battery reports
The Windows battery-report.html file selected for analysis. A report can contain battery, device, capacity, and usage-related information supplied by Windows.
Technical request information
Information needed to deliver a page or API response, which can include an IP address, browser or user-agent information, requested URL, timestamps, response status, and security-related events.
Contact messages
The email address, message content, and attachments that a person chooses to send through the published contact channel.
Processing workflows
Manual values and uploaded reports are different
Manual calculation
The interactive calculator can calculate a percentage from manually entered values in the browser. The values can still be present in browser memory while the page is open.
Report analysis
The selected Windows report is sent to the site's analysis endpoint so that the server can validate and parse the file and return battery results.
Infrastructure
Hosting, network, security, and delivery providers can process standard technical request information when pages and API endpoints are requested.
Processing purposes
Why information may be processed
- Provide the requested page, manual calculation, or report analysis.
- Validate input, prevent malformed requests, and protect the service from abuse.
- Diagnose errors, investigate security events, and maintain site reliability.
- Respond to support requests, corrections, accessibility reports, and feedback.
- Meet legal obligations and enforce the site's terms where applicable.
Retention and deletion
Retention must match the deployed system
Report content should be processed only for the requested analysis and should not be retained longer than necessary for that purpose. Technical logs, security records, backups, and contact messages can follow separate retention periods.
The production API, hosting configuration, logging services, and backup systems must be reviewed so this policy can describe actual retention and deletion behavior accurately.
Data minimization
Do not submit unnecessary information
Do not place passwords, financial information, identity documents, access credentials, or unrelated personal information in capacity fields, battery names, file names, or contact messages.
Review report files and screenshots before submitting or emailing them.
Cookies and local storage
Optional services require accurate disclosure
Essential storage may be used where needed for security, consent choices, or core site behavior. Optional analytics and advertising storage should not be activated before the applicable configuration and consent requirements are met.
When analytics, advertising, or other third-party services are enabled, this policy should identify the provider, purpose, data involved, available controls, and relevant retention information.
A consent interface should allow users to make and revisit choices where required. A decorative banner that does not control the relevant technologies is not sufficient.
Advertising
Future ad services
If Google AdSense or another advertising provider is enabled, the provider can use cookies, local storage, IP addresses, page URLs, device information, and related signals to deliver, measure, secure, or personalize advertising according to the user's choices and applicable requirements.
Advertising should not be enabled with fake publisher identifiers or before the privacy notice and consent implementation match the deployed service.
Consent
Regional requirements
Where legally or contractually required, advertising and analytics technologies should respect a valid consent or opt-out signal before optional processing begins.
For Google publisher products, the deployed consent solution must satisfy Google's current requirements for the relevant regions and ad configuration.
Service providers
Infrastructure and third parties
Information can be processed by providers that host, secure, deliver, monitor, or support the site. Optional analytics and advertising providers can receive information only when those services are actually integrated.
Legal and security needs
Required disclosures
Information may be preserved or disclosed when reasonably necessary to comply with applicable law, respond to a valid legal process, protect users, investigate abuse, or defend the site and its rights.
Privacy requests
Access, correction, deletion, or objection
Depending on applicable law and the information involved, a person may have rights to request access, correction, deletion, restriction, portability, or objection. Identity and request details may need to be verified before a request can be completed.
Send a privacy request to recursivefield@gmail.com. Include enough information to identify the request, but do not send unnecessary sensitive data.
Related policies
Review the site terms and disclaimer
The Terms of Use explain permitted use, while the Disclaimer explains the limits of battery calculations and guidance.