Your data

Where sessions live

Every session is two things on your phone: a raw log file — the samples exactly as captured, stored unconverted — and database rows derived from it for display. The raw log is the record; the database is a projection of it, and can be rebuilt from the logs at any time.

Keeping, and not keeping

• Retention — keep history forever (the default), or one year, or six months; older sessions are removed at launch.
• Delete one session — removes its raw log and its database entries, after a confirmation. It cannot be undone.
• Delete everything — lives in a labeled danger zone and makes you confirm you understand. Uninstalling the app also removes all of its data.

Getting data out

Any session exports as CSV, or as its raw log, to a location you pick. There is no lock-in to a format you can't read — the CSV is the same time/watts/level/temperature table the app shows you.

Getting data in

A session log recorded by ChargeLog on another device — a second phone, or the Wear OS build being proven on a watch — can be imported. Imports are identity-checked: a log with no device identity, a malformed one, or a duplicate of a session already present is refused with a reason, because a session history you can't trust is worse than a shorter one.

What leaves the phone

Nothing. The app declares no INTERNET permission — verifiable in the APK manifest — so it cannot make a network request at all. There is groundwork in Settings for contributing anonymized charging curves to an open dataset: off by default, with a preview showing exactly what would be sent — quantized curves only, never your tags or notes — published only as per-model aggregates of at least 20 devices, and deletable for as long as the app is installed. As of this writing that is consent machinery, not a transmitter: with no network permission, nothing can be sent even if you opt in. If upload ever ships, the privacy policy and this page change first, and the manifest change is visible to everyone.