The headset has a private browser two inches from your eyes
Adult-site traffic from Meta Quest headsets grew 47.5 percent in a single year. Most parents who bought one for Beat Saber have never opened its browser and do not know it exists. Here is how we close that door, and - just as important - exactly where our protection stops.
Why the headset is different
A phone is a shared object. It gets left on counters, glanced at, handed around. A headset is the most private screen ever put in a house: opaque, worn on the face, with audio in the ears. Nobody can walk past and see what is on it. It ships with a full Chromium-based browser, and it sits in a category most filtering products ignore entirely because they are built as phone apps.
How Breaking Chains blocks it
Every website visit begins with a question: "what is the address for this site?" That question is a DNS lookup, and it happens before any content loads, in the browser or in an app. Breaking Chains answers that question - or refuses to. When a Quest on your home network asks for a blocked address, it gets no usable answer, so the page never loads. Nothing to install on the headset, nothing a teenager can uninstall from inside it.
That is the whole mechanism, and it is why the headset is covered the moment your home network is covered.
Where that protection stops. Honestly.
This is the part other companies leave out, and it is the part a parent actually needs, because it tells you when the headset is safe and when it is not.
1. The headset leaving your network. Our home protection follows your network, not the device. Take the Quest to a friend's house, a hotel, or a phone hotspot, and it is on their DNS, not ours. On a phone we solve this with a profile that travels; the headset has no equivalent we can install today. So the honest rule is: at home, covered. Away from home, not covered.
2. Sideloaded apps that carry their own content. Blocking a domain stops a site from loading. An app that ships its content inside itself never asks us anything. Locking down app installs with a parent-held account is the answer here, not DNS.
3. Casting from another device. A phone on cellular can cast to a headset. The traffic is the phone's, not the headset's, so the phone is what needs protecting.
What we recommend to parents, plainly
Cover the home network so the headset is protected by default. Set up Meta parental supervision from your own phone so app installs need you. Then make the rule that matches the technology: the headset stays on the home network. That is not us dodging a limitation, it is us telling you where the wall ends so you can put a human decision there instead.
We would rather you trust a smaller promise we actually keep. A parent who knows exactly where the guardrails stop can hand over a headset with confidence. A parent who was told "you are fully protected" cannot, because it was never true.
Set up your VR headset step by step · What we block · The facts