Last updated: 26 October 2026
This Privacy Policy explains how ADB Shell handles information when you authorize an Android debugging connection, use its terminal and records, export data, or contact its developer.
This policy covers the Android application's connection, terminal, notification pairing, command library, history and data-management features, and correspondence sent to the developer. Your target device and any document provider or recipient you choose have their own permissions and practices. ADB Shell does not operate a command relay, user account service or developer backend.
The app processes the IP address or hostname, pairing and connection ports, transport, device nickname, groups, favorites and connection timestamps you enter or select. After authorization, two identification queries may read the target's model and Android release. Local discovery receives the names, addresses, ports and types of advertised ADB services. It does not scan the internet. Notification pairing accepts only service addresses belonging to this phone; it does not automatically choose another person's device.
The app stores editor submissions, records of interactive input sent, session dates, target information, transport, state, available exit information and retained output in private application data. It also stores personal command templates, descriptions, groups, favorites, font and display preferences, retention and storage limits, and non-secret connection-form fields. Direct terminal input records describe input sent; they are not a guarantee of the shell's final parsed command or individual exit result.
Commands, terminal output and logcat can contain personal information, identifiers, account details, addresses, tokens or other sensitive content depending on your actions and the target. Treat saved records and exported files accordingly.
The app generates an RSA authorization identity. Its private material is encrypted using an Android Keystore wrapping key and stored in the private no-backup directory. The public key and certificate are used to authorize the host on your target. Pairing codes are used to perform the requested pairing, are not intentionally written to history, logs or backups, and are cleared from the manual form after success.
Notification pairing receives the code through Android's explicit direct-reply action. It does not read notifications from other applications, monitor the clipboard, or request Notification Listener access. Code text is not echoed into the notification or added to remote-input history. Android controls the system entry field and its own input behavior. The helper retains only non-secret progress, result, address, connection port and timestamps for recovery when you return. Result visibility expires after ten minutes, with cleanup on the next status read; it is replaced when a new attempt starts and can also be removed by resetting the identity or clearing app data.