ADB Companion is provided under the Austin Projects name. For support or privacy questions, contact austin-projects@mail.com. This policy describes the Android app com.adbcompanion. A website or app store may process information under its own privacy policy.
What the app does with your data
ADB Companion connects to Android devices you choose and sends the shell commands you run to those devices. Device addresses, pairing/authentication messages, commands, and returned output are exchanged with the selected target. Output can contain personal or sensitive information depending on the command. Commands can also make the target contact other services; those services and the target's behavior are outside ADB Companion's control.
The app has no account system, advertising SDK, analytics service, automatic crash reporting, or developer-operated backend. It does not automatically send your saved devices, commands, results, or usage history to the publisher. Local command explanations are built into the app; they do not use a remote AI service.
Information stored on your phone
The app stores saved device names and addresses, connection metadata, preferences, saved actions and favorites, command text, execution status/timing, and captured command output in its private Android app storage. Command history and preferences rely on Android's app-storage protections; the history database is not separately encrypted by the app.
The ADB host private key is encrypted using Android Keystore protection. Pairing codes are used in memory and are not intentionally logged or saved by the app. Same-device pairing can receive the code through an Android notification reply. Android itself handles that notification and input.
Automatic Android app backup and device-to-device data transfer are disabled for the app's data. There is no cloud sync or publisher recovery service for lost authorizations or history.
Discovery and connections
Local discovery uses network service advertisements to find ADB endpoints. When you choose Scan network, the app checks private IPv4 addresses on the current Wi-Fi or Ethernet network, within a bounded subnet, for the standard ADB port and possible streaming-device ports. This sends network probes to local devices. Scan results stay in memory until discarded; scanning does not send an ADB host key or run shell commands. A detected device is saved only when you choose to connect or pair successfully.
Wireless Debugging code pairing and its subsequent connection use TLS. Classic ADB-over-TCP can be unencrypted. ADB's connection protocol does not provide permanent, pinned server identity authentication; connect only to devices and networks you trust.
Permissions
Internet/network-state/Wi-Fi and multicast access support local discovery and ADB connections. Android versions that require a local-network permission ask before access. Optional notifications and a connected-device foreground service support same-device pairing while Android Settings remains visible. The app does not request camera, microphone, contacts, or precise-location access. Import/export uses Android's document picker for files you select.
Copy, share, import, export, and support
Copy places the selected content on Android's clipboard. Share sends the selected content to the app you choose. Action export writes action names, descriptions, commands, categories and relevant action preferences to your chosen document provider; that provider may sync files to the cloud. These are user-initiated transfers. They do not automatically include pairing private keys or the whole command history. Imported actions are saved locally and do not run automatically.
If you email support, your email provider and the publisher receive the address, message, and any attachments you send. A feedback template includes app/Android version and space for reproduction steps, without automatically attaching logs, device addresses, commands, or results. Review anything you send and omit codes, keys, credentials, and unnecessary personal information.
Austin Projects uses support correspondence to answer requests and investigate reported problems. Messages are handled through the support email provider and retained for as long as needed for those purposes or applicable legal obligations. To request deletion of correspondence, email austin-projects@mail.com. The email provider may retain its own records under its policies. Deleting app data does not delete email correspondence.
Retention and deletion
Command history defaults to 30 days, with a maximum of 1,000 results. Each result retains at most 64 KiB of standard output and 64 KiB of error output. Retention is applied when the app performs its pruning operations; it is not a background erasure guarantee while the app is unused. Change the retention period in Settings, clear the selected device's history from Terminal, or clear all command history in Settings.
Saved actions, favorites, preferences, and devices remain until you delete or reset them. Deleting a saved device does not delete its past history. Forget all devices and authorization removes the local ADB identity; revoke the app's authorization on the target as well if needed. Reset app removes local user data and restores starter actions. Android's Clear storage or uninstall removes the app's local storage. Files you exported, copied/shared content, support messages, and changes made on a target are not undone by deleting app data.
Changes
Updates to this policy will appear in the app and in the privacy policy linked from its Google Play listing, with an updated effective date. For questions about changes or data handling, contact austin-projects@mail.com.