This Privacy Policy describes how Vireka Interactive ("we", "our" or "the company") collects, uses and protects information when you use the mobile application Local ADB Shell.
Local ADB Shell is a terminal that runs adb shell commands against the very phone it is installed on. It does not control other devices and it does not need a computer: the app connects to the Android Debug Bridge daemon of your own device over the loopback address 127.0.0.1, which never leaves the phone.
The short version: we run no servers of our own. Nothing you type, nothing a command prints, and nothing the app stores is ever sent to us or to anyone else. There are no ads, no analytics, no crash reporting and no user accounts.
Vireka Interactive is a brand owned by:
Owner: Miguel Lopez Soriano
Tax ID (NIF): 18470711D
Address: Calle Villacisneros 7, 44003, Teruel (Spain)
Contact email: [email protected]
We collect nothing. The app does store things, but all of it stays in the app's private storage on your device, where only Local ADB Shell can read it.
Almost all of it is created by you, as you use the app:
getprop ro.product.model, which prints your phone's model — and that leaves a chat and a history entry like any other command.A shell command prints whatever you asked it for, and that can include personal information: file names, installed package lists, network addresses, device identifiers. Local ADB Shell keeps that output in the chat so you can scroll back to it.
It stays on your device and we never see it — but it is stored until you delete the chat, and it will be included in any backup file you choose to export. If you are about to share a screenshot, a backup or a command's output, look at what is in it first.
Since version 1.0.2 the app can also read one of those lists for you. The app picker runs pm list packages through the shell session and shows the installed applications so you can choose one instead of typing its package name. From version 1.0.3 each row also carries the app's icon, and that part does not come through adb: icons are handed over by Android's own package manager inside this app, which is why the manifest declares a <queries> entry for apps that have a launcher icon (section 5). Either way, what is read is read again every time you open the picker, it is held in memory only while the picker is open, and it is never written to storage nor sent anywhere.
The data listed above exists for one reason: so the app can show you what you did last time. Chats let you scroll back, history and favourites let you run something again without typing it, and settings keep the app the way you left it.
Local ADB Shell declares two permissions, and no others.
There is no location permission, no storage permission, no contacts, no camera and no advertising ID. Reading and writing files on the device is done through the ADB session you authorised, not through Android storage permissions.
The manifest also declares a <queries> entry, which is not a permission and is nothing you are asked to grant. Since Android 11 an app only sees the other apps it declares an interest in, and Local ADB Shell declares apps that have a launcher icon, so that the app picker can draw those icons. It deliberately does not use QUERY_ALL_PACKAGES, the restricted permission for seeing every installed package. What is read that way stays on the device and is never stored, as described in section 3.2.
Chats, history and favourites live in a database in the app's private directory; settings live in the app's preferences. Both are sandboxed by Android: other apps cannot read them. Nothing is written to shared storage unless you export a backup yourself.
The app talks to the ADB daemon of the device it is running on, over the loopback interface. Traffic does not touch your Wi-Fi network, your router or the internet. The session is authorised with the ADB key pair described in section 3.1 and secured with TLS, exactly as a computer connecting over Wireless debugging would be.
That holds for what the app sends, always. What one optional setting does change is what your phone is willing to listen to, and it is described next.
This setting is off unless you turn it on, and turning it on takes a dialog that says what it does before anything happens. With it on, the app asks the ADB daemon of your own device to listen on a fixed port, 5555, and reconnects through there. From that point the app carries on working with Wi-Fi off, in aeroplane mode and without pairing again — useful when you are away from any network and still want a shell on your own phone.
What it costs is worth saying plainly: while it is on, that port is open on every network your phone joins — your home Wi-Fi, an office network, a café — and not only on the loopback interface. Only a device holding an ADB key you have already authorised can open a session through it, and that session is still secured with TLS, but the port itself is reachable from the local network.
It lasts until the next restart and no longer, because Android does not restore that port on boot. The app checks for the restart when it starts, turns the setting off on its own and says so the next time you open it, so it is never left on across a restart without you deciding again. You can also turn it off yourself in Settings → Connection: that stops the app reopening the port, and restarting the phone closes the one that is already open.
You can export your chats, history, favourites, your own commands and your macros to a file. That file is plain, readable JSON and it goes wherever you tell Android to put it — your Downloads folder, a cloud drive, a message. From that moment the file is yours to look after; the app has no copy of it and no way to reach it.
The catalogue can also save what your phone answers about itself — the list of services and the built-in help of tools like pm or am — as a plain text file, in the same way and to wherever you choose. It contains no personal data beyond what those commands print about your device.
Since version 1.0.6 you can also share a command together with its output, from the share button on that command in the console. The app hands it to Android's share sheet and only the app you pick receives it: as text, or as a plain text file when the output is long. That file is written to the app's private cache just before sharing, is readable only by the app you chose, and is deleted the next time you share something. Nothing is sent until you pick where it goes, the app keeps no record of what you shared, and once it arrives it is covered by the other app's own policy.
Settings → About → Recommend the app works the same way, and what it shares is a sentence and the Google Play link. It carries nothing about you or your device.
The app integrates three Google Play services and nothing else. No advertising network, no analytics provider, no crash reporter.
Used to sell and restore the Pro purchase. The transaction happens entirely inside Google Play; we never see your payment details, and we receive no personal data from it. See Google's Privacy Policy.
Used to tell you when a newer version is available and to install it without leaving the app.
Used to show the Play review dialog. Whether you write a review, and what you write, is between you and Google Play.
Pro — a single, one-off payment. It is not a subscription and it does not expire. It unlocks unlimited favourites, as many console tabs as you want, your own commands in the catalogue, macros, repeating a command every few seconds, and putting the widgets you build on your home screen. Backups, the file browser and the app picker are free for everyone.
The purchase is tied to your Google account, so reinstalling the app or changing phone restores it at no extra cost.
Refunds are handled by Google Play under its own terms. You can request one from your Play Store order history. If something is not working as described, write to us first — we would rather fix it.
Under the GDPR you have the right to access, rectify, erase, restrict and port your personal data, and to object to its processing. In this app those rights are unusually simple to exercise, because the data never leaves your device: you already hold all of it, and deleting it is immediate and complete (section 6.5).
We hold no copy of anything, so there is nothing for us to hand over or erase on your behalf. If you believe otherwise, or you are not satisfied with our answer, you may lodge a complaint with the Spanish Data Protection Agency (aepd.es).
Notification permission can be granted or revoked at any time in Android Settings → Apps → Local ADB Shell → Permissions. Wireless debugging itself is an Android developer setting, and you can turn it off there whenever you want; the app stops connecting immediately. The one exception is the setting in section 6.3: if you turned it on, the session already open survives Wireless debugging being switched off, and it takes disconnecting from the app or restarting the phone to end it.
Local ADB Shell is a developer tool and is not directed at children. We do not knowingly collect data from anyone, minors included, because we collect no data at all. The app carries no ads and no social features.
We may update this Policy when the app changes. The date at the top always says when it was last revised, and material changes will be announced in the app's release notes on Google Play. Continuing to use the app after a change means you accept the revised Policy.
This Policy is governed by Spanish law and by Regulation (EU) 2016/679 (GDPR), together with Organic Law 3/2018 on the Protection of Personal Data and the Guarantee of Digital Rights (LOPDGDD).
If you have any questions about this Privacy Policy, please contact us:
Response time: within 72 business hours.
This Privacy Policy is effective from September 15, 2026 and applies to all versions of Local ADB Shell distributed through the Google Play Store.