Privacy
Ilya Shumilin publishes Drone Battery Log and is responsible for this app and support website. This notice explains how they handle data. Battery records are kept on your device. Some technical data is handled separately, as explained below.
Your battery records
Battery names, specifications, connectors, notes, purchase dates, counts, voltage readings, custom reference markers and activity history are stored on your device. Existing imported session records are retained even though the Sessions interface is no longer available. Statistics are calculated locally. We do not receive your logbook or keep a cloud copy.
The app has no account system, cloud synchronisation or advertising. You can use the logbook without a network connection. Operating-system backups may include app data according to your device settings.
Photos, QR codes and NFC
Camera and NFC permissions are requested when you use those features. Printed labels are recognised on the device with Apple Vision on iPhone and iPad or Google ML Kit on Android. Photos and recognised text are not uploaded or attached to battery records. Only the details you review and save enter your logbook.
QR labels and NFC tags contain a battery identifier, not its history. Scanning does not transfer records to another device. Original photos remain in their chosen location. Android camera capture may also leave a local image in the app’s Pictures directory, separate from the logbook.
Google ML Kit on Android
The QR and text-recognition models are bundled with the app, so first use does not require a model download. Google states that input images and recognition results are processed on the device and are not sent to Google servers.
ML Kit sends performance and usage metrics to Google and may contact its servers for SDK maintenance. This is separate from the app’s local diagnostics switch. Google describes this processing in its ML Kit privacy terms.
Backups and exports
JSON backups contain the complete logbook, including notes and recorded times. CSV exports contain battery details and counts. PDF labels include battery identifiers and descriptions. You choose where to save or share these files.
Restoring a backup replaces the local logbook after validation. If records already exist, the app asks the system to save a recovery copy first. Export a backup before changing devices or uninstalling the app.
Error reporting
Configured production builds send sanitised reports of unexpected errors to GlitchTip, hosted in Switzerland at glitchtip.wildma.ch. Reports use fixed error codes, random support references, timestamps, app version, release and platform. They may contain application filenames and line positions needed to locate a fault.
Reports exclude battery details, photos, scanned values, raw error messages, database contents, filesystem paths and local support logs. No account or installation identity is attached. Retention is configured for 90 days for error events and source files, and 365 days for release metadata. These settings do not guarantee that every backup has already been purged.
Usage analytics
PostHog usage analytics is not configured in the current release and sends no usage events. The app contains support for a separate EU analytics project, but it will not be enabled without updating the privacy notice and selecting its retention policy.
There is no advertising identifier collection, session replay or automatic recording of screen text or form input. Development and staging builds send neither app error reports nor app usage analytics.
Optional diagnostics and local logs
Optional diagnostics are off by default. When enabled, they keep up to 300 entries from the last seven days on your device: timestamps, fixed action names, durations, outcomes and error codes. Shared reports also include app/build and platform information. Battery names, identifiers, notes, images, scanned values and file paths are excluded.
You can inspect, copy, share, export or clear diagnostics. There is no automatic upload. Turning them off stops new entries but keeps existing ones until expiry or clearing. Copies you send through another app or the clipboard follow that service’s rules.
The native app also keeps separate local operational logs for failures. These are not uploaded or included in diagnostic reports, and the diagnostics switch does not control or clear them. A sanitised unexpected-error report may still be sent to GlitchTip as described above.
Deleting data
Settings → Delete all data clears the local logbook, including batteries, notes, activity, undone entries and archived sessions. It also clears and disables optional diagnostics and resets the usage-statistics installation ID. Deletion requires confirmation, has no Undo and creates no recovery backup.
This does not remove exported files, shared reports, original photos, Android capture files, local operational logs, operating-system backups, physical tags or previously transmitted error reports. Clearing the database is not a promise of forensic erasure. Only an existing backup can restore a deleted logbook.
Network connections and this website
Error reporting is best effort and is not required to use the logbook. Network services receive your IP address as part of a connection even where the app excludes IP-based identity and location enrichment from its reports.
This website uses no analytics scripts, cookies or contact form. Its hosting and delivery providers receive technical request information, including your IP address, to serve the pages. Email links open your mail app. If you contact support, your email address and message are processed to respond to your request. Send only the information needed.
Questions and requests
Contact drone-battery-log@shumil.in with privacy questions or requests concerning information you have sent us. Device-only records can be managed or deleted in the app; we do not hold a copy. Material changes to this notice will be published here.