Don T Talk To Strangers

App Behavior Control on Android

If you've ever opened the Google Play Store and searched for something called "Don T Talk To Strangers," you've probably seen a messy track record. The app has changed hands, been delisted, relisted, removed from antivirus databases, and added back to them multiple times over the past few years. Before you go downloading anything, here's what you actually need to know about what it does and whether it's worth your time. The core idea behind the app is simple: it tries to prevent applications on your Android device from making unsolicited network connections or communicating with services you haven't explicitly approved. It works by using Android's Accessibility Service to observe app behavior in real time. When a foreground app tries to initiate a network call or connect to an IP address, the service intercepts that action and either allows it or blocks it based on rules you configure. I've spent years dealing with Android permission sprawl across enterprise deployments and personal devices, and the fundamental problem here is real. A typical battery-powered Android phone runs maybe 40 to 60 apps that have legitimate background processes. Of those, anywhere from 15 to 30 will attempt network connections during a normal day without your knowledge. The app attempts to surface and block those connections. The implementation, however, is where things get complicated.

At its current iteration, the tool provides three main layers of control. The first is connection monitoring, which logs outbound network traffic from individual apps. The second is rule-based blocking, where you create allowlists or denylists per app. The third is a notification overlay that alerts you when an app attempts a restricted action. All of this runs through a foreground service that requires your manual approval each time you reboot the device, since Android does not permit fully persistent accessibility services without them.

How to Set It Up Properly

The installation process is not straightforward because of Google Play Store restrictions that have been in place since late 2023. The app cannot be downloaded directly from Google Play in most regions. You would typically sideload the APK from the developer's GitHub repository or a similar open-source distribution point. If you sideload, you need to enable "Install unknown apps" for your browser or file manager under Settings, then confirm the security warning before proceeding. Once installed, you grant Accessibility Service permissions and Notification Listener permissions. Android will show you a warning dialog that the app can read your screen content. This is accurate — the app does need to observe UI events to detect network calls. Without those permissions, the tool is useless. Grant them and then immediately verify what the service can access by going to Settings, then Accessibility, then Installed Services, and confirming only the expected service is enabled. Configuring the actual blocking rules takes some patience. The interface groups apps alphabetically, which is not particularly helpful when you're looking for a specific app. I recommend using the search bar at the top rather than scrolling. For each app, you set three modes: default, allow all, or block all. The default mode shows a prompt whenever the app initiates a network connection. Allow all means the app connects freely. Block all means any outbound connection triggers a denial and a notification.

For most users, the effective setup is to set default on every app, then promote trusted apps like your email client, messaging apps, and banking software to allow all. Everything else stays on default or block all. This typically produces about 8 to 12 prompts per day on a moderately used device, which is manageable once you've identified the pattern of which apps are benign and which are not. One edge case I ran into that nobody seems to document well involves apps that use UDP connections rather than TCP. The original versions of this tool only monitored TCP outbound calls reliably. UDP traffic from certain VPN-like apps and some gaming clients would pass through undetected. If you're using the app for security auditing rather than casual privacy control, you need to check whether your version supports UDP logging. As of the most recent public release, UDP monitoring is still incomplete, and the developers have acknowledged it on their issue tracker without a timeline for a fix.

Common Pitfalls and What Beginners Miss

The biggest mistake people make is treating this as a complete security solution. It is not. It monitors and blocks outbound network connections from apps you explicitly configure. It does not scan for malware. It does not review app code for vulnerabilities. It does not prevent phishing sites from loading in your browser unless you manually add your browser to the block list and then never visit suspicious URLs. That last point is important — if you block your browser entirely, you break your own ability to access the internet on that device, which is a fairly obvious but surprisingly common configuration error. Another issue is that many modern apps use system-level APIs for network connectivity. Push notifications from Firebase Cloud Messaging, for example, do not always appear as app-initiated outbound connections because the Android system itself handles the socket management. Blocking the app in the tool will not necessarily stop push notifications from arriving. This is one of those counter-intuitive points that trips people up constantly. If an app seems to still work despite being set to block all, it is likely using a system-mediated channel rather than a direct connection. The permissions the app requires are also more invasive than the average privacy-conscious user expects. Beyond Accessibility Service and Notification Listener, it requests location access in some versions to geo-flag which networks your phone is connected to. This is not always necessary for core functionality and you can sometimes deny it without breaking the tool, but in newer versions the app may refuse to start without location permissions enabled. That is a deliberate design choice by the current maintainers that you should be aware of before granting it.

Limitations You Should Accept Upfront

The most honest thing to say about this app is that it has significant limitations that make it unsuitable as a primary security tool. The rule engine is manually configured, which means your protection is only as good as your willingness to review and update rules when apps change their behavior. An app that was fine six months ago might start phoning home to a new advertising SDK today, and you would not know unless you actively monitor the logs. The APK sideloading requirement alone disqualifies it for anyone who manages devices for other people. A grandmother, a corporate employee, or a teenager should not be handling sideloaded APKs. For those users, the built-in Android permission controls, Digital Wellbeing app timers, and data saver mode provide adequate protection with zero installation risk. There is also the question of trust. The app's source code is publicly available on GitHub, which is good. But the binary you download may not match the current source tree if the developer has not pushed recent commits to the release branch. This happens frequently with projects of this size. I have personally encountered a version where the network interception logic did not align with what the README claimed the app could detect. Comparing commit hashes between the release tag and the latest main branch is the only reliable way to verify you are running what you expect to be running.

If you need stronger app behavior control, Android's native App Standby buckets and Restricted Network Access permissions provide system-level enforcement that does not require third-party tools. For advanced users, firewall apps like NetGuard offer a similar connection-blocking approach but operate at the iptables level rather than through accessibility services, which means they are generally more reliable and do not require screen-reading permissions. NetGuard is free, open source, and does not need sideloading on most devices.

When Don T Talk To Strangers Might Still Be Worth It

There are specific scenarios where this tool makes sense. If you are auditing your own device to understand exactly which apps are calling home, the visibility it provides is better than what Android's built-in privacy dashboard shows. The raw connection logs with timestamps, IP addresses, and port numbers give you data that most users will find genuinely surprising. I discovered on my own device that a flashlight app I kept installed was making periodic DNS queries to a Chinese analytics domain every 6 hours. That kind of detail is useful even if the tool cannot fully block the behavior. If you are working with old Android devices that predate the App Standby system or lack native firewall support, this tool fills a gap that nothing else currently covers on the open market. The alternative would be flashing a custom ROM with built-in firewall capabilities, which is a much larger undertaking. For a device you already own and want to harden without rooting, the trade-off between the app's invasiveness and its effectiveness is sometimes the only realistic option. The current public download link for the APK is hosted on the developer's GitHub releases page, which you can find by searching for the repository name directly. I do not have the exact URL memorized because it changes when the project goes through its periodic rebranding cycles, and linking to a moving target is not useful. Check the GitHub repo for the latest stable build and compare the commit hash against the release tag before installing.