Watchingthewatchers
We built a testbed that plays the same content on every TV without anyone at the remote, records all of its network traffic, and then works out which traffic belongs to ACR.
Collect the data Run thousands of controlled viewing experiments on 12 TVs and capture every packet they send and receive.
Run thousands of controlled viewing experiments on 12 TVs and capture every packet they send and receive.
Identify ACR endpoints Use the controlled content to pick out the servers that respond to what's on screen, then compare their traffic across conditions.
Identify ACR endpoints
Use the controlled content to pick out the servers that respond to what's on screen, then compare their traffic across conditions.
Data collection infrastructure.
Twelve smart TVs from ten manufacturers cover the eight operating systems that run 95% of U.S. smart TVs, and more than 80% of the TV brands with over 3% of U.S. households. The operating system is what we compare, so we chose TVs to cover every major OS first, adding a second TV where one OS is sold by several brands.
All traffic to and from each TV was captured with the Mon(IoT)r software and the SPHERE research infrastructure. In total we ran 5,943 controlled experiments.
Getting content onto the screen
A control machine sends the same content to every TV through three routes, so each viewing scenario is identical across devices.
HDMI-to-RF modulators broadcast our own custom channel to each TV's antenna input.
IP-to-HDMI converters turn video streamed from the control machine into an HDMI signal, like a cable box or console.
Google Pixel phones and a Windows laptop running Pigeoncast and Miracast cast to each TV using its own mirroring protocol.
Ten viewing scenarios
The scenarios cover the common ways people use a smart TV. Idle, with the TV on the screen and nobody using it, is the control for spotting baseline traffic.
Separating sound from picture
Some ACR systems recognize content by its audio, others by its video. By switching each one off in turn on our custom antenna channel, we can tell which a TV relies on. The antenna is a natural ACR target, because what you watch over the air can't be tracked by any app.
Running it without a remote
We wrote control scripts using each OS's Python remote-control library for six of the operating systems. Xumo OS and VIDAA OS had no reliable library, so we drove them through their Android remote apps using ADB.
The hard part was that TV menus change, so each OS needed its own tested sequence of commands. An IP camera on every TV recorded each run, and we reviewed the frames to confirm it worked. Runs that failed because of internet outages or unexpected TV behavior were repeated.
How we answer each question
Under what viewing conditions does ACR send traffic? We identify each TV's ACR endpoints, then compare the traffic they receive in each of the ten scenarios.
Are ACR opt-outs offered, and do they work? Every scenario runs 30 times with ACR on and 30 times after opting out in the TV's settings, in a random order so one test can't bleed into the . We then compare ACR traffic between the two states.
What viewing information is exposed? Where ACR traffic is unencrypted, we read it directly. Where it's encrypted, we infer what it carries from its timing, volume, destinations and protocol details. We also check whether content-delivery services leak viewing data outside ACR.
Twelve TVs from ten manufacturers, covering operating systems with 95% of the U.S. smart-TV market. Where one operating system is sold under several brands, we tested more than one TV.
Results reflect these devices and firmware versions at the time of testing and may not carry over to other models or regions.
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
