Privacy Policy - Remote ADB Shell
Privacy Policy
This Privacy Policy describes how Remote ADB Shell ("we", "our", or "the Application") collects, uses, protects, and handles your information when you download and use our Android mobile application. We are committed to transparency, user privacy, and strict compliance with the Google Play Developer Distribution Agreement, Google Play User Data Policies, GDPR, and CCPA/CPRA.
1. Information We Do NOT Collect
Unlike cloud-based management tools, Remote ADB Shell operates locally on your hardware. We do not collect:
- Personal Identifiable Information (PII) such as your real name, physical address, email address, phone number, or government IDs.
- ADB shell command history, command keystrokes, shell scripts, or terminal output transcripts.
- Files, photos, media, application packages (APKs), or personal data extracted from target connected devices.
- Biometric, financial, or payment information.
2. Information Processed Locally on Your Device
The Application processes certain configuration and operational data strictly within your local Android private sandboxed storage (DataStore / SharedPreferences):
- Saved Device Bookmarks: IP addresses, ports, device nicknames, and paired device fingerprints you choose to save for quick reconnection.
- ADB RSA Cryptographic Keys: The public and private RSA key pair required by the Android Debug Bridge protocol to authenticate debugging sessions. These keys are generated on-device via secure cryptographic providers and never leave your hardware.
- Terminal Customization Preferences: Your chosen terminal font size, cursor blink settings, color theme (e.g., Tech Blue, Monokai, Dark AMOLED), and quick-command favorites.
All local data can be cleared at any time by tapping "Clear Data" within the app settings or via Android OS System Settings > Apps > Remote ADB Shell > Clear Storage.
3. Device Permissions & Purpose of Use
In accordance with Google Play's Minimum Necessary Permissions policy, Remote ADB Shell only requests permissions essential for its core debugging and terminal functionality:
| Permission | API Level / Type | Purpose & Functional Need |
|---|---|---|
android.permission.INTERNET |
Normal Permission | Required to establish direct TCP/IP socket connections to target Android devices for ADB over Wi-Fi, Wireless Debugging, and remote IP debugging. Also used to fetch banner ads from Google AdMob. |
android.permission.ACCESS_NETWORK_STATE |
Normal Permission | Allows the app to check whether a local Wi-Fi or active network connection exists before attempting an ADB socket connection. |
android.permission.ACCESS_WIFI_STATE |
Normal Permission | Enables local subnet IP detection and automatic Wi-Fi interface discovery to facilitate pairing with target devices on the same Wi-Fi network. |
android.hardware.usb.host |
Hardware Feature (Optional) | Enables direct USB OTG (On-The-Go) communication between your Android phone and target devices via a physical USB cable. |
4. Third-Party Services and Advertising
To support ongoing development and maintenance, the Application integrates industry-standard Google Play SDKs:
-
Google AdMob (Google Mobile Ads SDK):
We display advertisements powered by Google AdMob. Depending on your region and consent preferences, AdMob may collect and process pseudonymous identifiers such as:- Mobile Advertising ID (Google Advertising ID / GAID)
- IP address (for coarse geographic ad delivery and fraud prevention)
- App performance diagnostics and ad interaction metrics
-
Google User Messaging Platform (UMP) / Consent Management:
For users located in the European Economic Area (EEA), the United Kingdom (UK), and Switzerland, we utilize Google's UMP SDK to present an IAB TCF v2.2 compliant consent dialog to collect, record, and manage your advertising consent preferences.
5. Google Play Data Safety Declarations
For complete clarity when reviewing our Google Play Store listing Data Safety disclosures:
- Data Shared: Pseudonymous advertising diagnostics and Advertising IDs are shared solely with Google AdMob for ad display and fraud detection.
- Data Collected by the Developer: None. The developer operates no external telemetry, tracking, or proprietary databases.
- Data Security: All network communication over ADB adheres to standard Android ADB cryptographic authentication. Local app data resides in encrypted, sandboxed app storage.
- Data Deletion: You can purge all bookmarks, saved sessions, and cryptographic keys instantly by clearing the app data or uninstalling the app.
6. Security and ADB Key Handling
Security is paramount when running Android Debug Bridge commands:
- RSA Authentication: When connecting to a target device for the first time, an ADB RSA key authentication prompt is generated. Your private key remains exclusively on your host Android device.
- Explicit Authorization: No target device can be commanded without an interactive user approving the "Allow USB/Wireless Debugging?" dialog on the target screen.
7. Children's Privacy (COPPA Compliance)
Remote ADB Shell is a technical developer tool intended for developers, engineers, and Android power users. It is not directed at or designed for children under the age of 13 (or under 16 in certain EU jurisdictions). We do not knowingly collect personal information from children. If you become aware that a child has provided us with personal information, please contact us immediately.
8. Changes to This Privacy Policy
We may update our Privacy Policy from time to time to reflect changes in legal requirements or application enhancements. Any revisions will be published on this page with an updated "Last Updated" date. We encourage you to review this page periodically.
9. Contact Us
If you have any questions, concerns, or requests regarding this Privacy Policy or your data, please reach out to us:
Developer / Support Team: Remote ADB Shell Support
Email: support@remoteadbshell.com
Application: Remote ADB Shell for Android