{
  "id": 19770047,
  "title": "Packet Notes #3: Your phone has outbound AI traffic now. Nobody shows you it.",
  "url": "https://urgent.news/2026/11/13/packet-notes-3-your-phone-has-outbound-ai-traffic-now-nobody-shows",
  "topic": "ai",
  "section": "AI",
  "published": "2026-11-13T06:55:41.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/tacuns_firewall/packet-notes-3-your-phone-has-outbound-ai-traffic-now-nobody-shows-you-it-b60"
  },
  "original_language": "en",
  "account": "In the realm of firewall logs, I have observed an unusual trend: outbound AI traffic originating from personal devices. This discovery does not stem from ad or analytics traffic, but rather the actual data packets leaving phones and reaching AI service providers. Android's permission system, which governs access to camera, microphone, contacts, and location, does not extend to this new form of data sharing. The INTERNET permission, granted automatically during installation, allows apps to connect to external endpoints without any user notification. Consequently, it is impossible for users to determine which of their applications communicate with AI providers. Unlike tracking mechanisms, AI traffic is characterized by the transmission of actual content, such as user drafts, photos, and queries, which are typically concealed within the app's interface. This data is sent to a limited set of large AI companies, making it relatively easy to identify once noticed. To address this issue, I developed a firewall application for Android devices, called TacUNS, which runs directly on the phone without requiring root access. TacUNS provides two screens: AI Radar, which identifies apps transmitting data to AI companies along with the volume of data sent, and ExfilMeter, which monitors overall outbound traffic. Upon first use, I discovered two apps on my device that were transmitting data to AI providers, which I had not anticipated. While the significance of this data transmission may vary, the primary concern is that users should have visibility into this activity, which the current platform does not provide. Steps to investigate outbound AI traffic include checking data usage per app in the device settings, examining the assistant, summarise, or smart reply features within commonly used apps, and reviewing the app's data safety section on Google Play for indications of third-party sharing. Ultimately, the solution lies in providing users with a log of outbound AI traffic on their devices, enabling them to make informed decisions about their privacy.",
  "summary": "I spend my working hours in firewall logs. Policies, sessions, denies, the usual. Then one evening I pointed the same habit at the device I actually carry, and the thing that stood out was not ads or analytics. It was AI. Not \"an app has an AI feature\". Actual bytes, leaving the phone, going to the endpoints of AI companies. The permission model never covered this Android's permission screen…",
  "key_points": [
    "Outbound AI traffic detected from personal phones",
    "Android permission system doesn't cover AI data sharing",
    "TacUNS app developed to monitor AI traffic on Android"
  ],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}