Amply Privacy Policy

Amply works locally on the device. It contains no analytics, advertising, account system, or automatic data transmission.

The optional adapter-discovery tool reads Android settings through user-authorized Shizuku access. A before/after comparison is kept in memory. Reports are created only after explicit user action, redact common identifiers, and are shared only through Android’s user-selected share target.

Debug-log recording is optional and starts only after the user confirms it. A recording can include Amply events, device and Android versions, battery and cable state, and charging-control results. Logs remain in Amply’s private app storage until the user explicitly shares or deletes them.

Amply uses a foreground service while a user-initiated temporary full-charge session, the optional reconnect gesture, or the optional charge alarm is active. The service observes battery level and charger connection state solely to manage one-time full charging, restore the selected protective charging policy, and — when the charge alarm is enabled — notify you to unplug once your chosen level is reached. The battery details shown in the app (level, temperature, voltage, current, health, and similar values) are read on-device from the system battery status and are never collected or transmitted.

On unsupported devices you can request charge-control support. This is opt-in. The report contains device and build details (manufacturer, brand, model, device and product codes, build fingerprint), Android version, battery and charger state, Amply’s version and distribution channel, and the results of Amply’s compatibility check — no personal identifiers such as serial numbers, account data, or contact details. Requesting support on GitHub shows the full report first and then opens a prefilled public issue page; the report is transmitted to GitHub as part of that page’s URL as soon as it opens, but becomes public only if you submit the issue. Alternatively, the same report can be handed to an email app of your choice as a text attachment addressed to the developer.

Last updated: 2026-07-20.