Skip to content

Privacy policy

Last updated: August 2026

The short version

The ChargeLog app records charging sessions on your phone and keeps them there. It has no way to send them anywhere: it declares no INTERNET permission, which you can verify in the APK manifest. This website uses no cookies, no analytics scripts, and no trackers.

Who we are

ChargeLog is developed and published by BluffWorks LLC, based in Virginia. For the purposes of data protection law (including GDPR), BluffWorks LLC is the data controller for any personal data processed through this website. The app itself sends nothing to us — see below. You can reach us at hello@chargelog.org.

The app

  • What it records: charging sessions — battery readings, charging phases, temperature, and physical context such as fold state, screen state, and whether the charge is wired or wireless — in a local database on your device.
  • What leaves your phone: nothing. The app declares no INTERNET permission, so it cannot make network requests. There is no analytics, telemetry, or crash reporting.
  • Your control: sessions can be deleted from within the app, and uninstalling the app removes all of its data.

This website

  • No cookies, no analytics scripts, no third-party trackers, no forms.
  • Your browser stores a single localStorage entry to remember your light/dark theme choice; it never leaves your device.
  • The site is served by Cloudflare, which keeps aggregate operational logs as its hosting provider — see their privacy policy.

Donations

Donations are processed by Liberapay (and the payment processors beneath it, Stripe and PayPal) under Liberapay's privacy policy. We never see your card or bank details.

Your rights

Because the app sends us nothing, there is no app data for us to access, correct, or delete — it is all on your device, under your control. For anything related to this website or a donation, email hello@chargelog.org and we'll respond within 30 days.

Changes

If this policy changes, the date at the top changes with it. A policy change can never retroactively grant the app network access — that would be a new APK with a new manifest, visible to everyone.