Privacy

The app

vrOS does not phone home, does not check in, and does not send usage data. There is no telemetry setting to turn off because there is nothing collecting.

Window capture, keyboard input and pointer forwarding all happen on your machine. Captured pixels go to your headset and nowhere else.

• No telemetry, no analytics, no usage metrics, no crash uploads
• Overlay layouts, settings and every other durable state are stored locally
• Nothing vrOS observes — captured windows, keystrokes, window facts — leaves the machine it runs on

Features that use the network

The core of vrOS never touches the network. The features that do are ones you turn on: each is off by default, and each tells you what it connects to before it starts. What they send is only what the feature is for — never captured windows, keystrokes or window facts.

Anything that listens for connections is bound to your own machine unless you choose otherwise, and shows its address and port on the page that owns it.

• Twitch connects to Twitch for sign-in, chat, ads and streams, and to 7TV, BetterTTV and FrankerFaceZ for emotes. Chat history is off by default; if you turn it on, the names of the channels you open are sent to recent-messages.robotty.de to load their recent messages. The full list of hosts is on its consent screen.
• OBS Control connects only to the OBS instances you add, over obs-websocket.
• VRChat OSC talks to VRChat on your own machine. So that VRChat can find it, it announces itself on your local network; the announcement carries no personal data.
• A third-party extension declares network access on its consent screen. vrOS cannot sandbox a native program, so judge one by who wrote it.

What vrOS can see

Capturing a window means vrOS watches that window — where it is, whether it moved, whether it closed. The watch begins when you bind the capture and ends when you unbind it. vrOS never installs a global keyboard hook and never watches focus across your whole desktop.

Text awareness is position-only. When there is a text cursor in a captured window, vrOS learns that it exists and where it sits, which is what lets the VR keyboard place itself. It does not read the text in the field, and it does not read your keystrokes back after sending them.

None of that goes anywhere. Keystrokes, composition state and window facts live and die inside the process that draws your overlays.

This website

vros.cat and docs.vros.cat are static files. No account, no login, no form.

There is no analytics on these sites: no beacon, no measurement script, no identifier of any kind. Nothing here sets a cookie, which is why there is no cookie banner — there is nothing to consent to. The host that serves the files sees the requests it serves, the way any web server does, and nothing on the page adds to that.

Fonts are served from this site rather than a font CDN, and no third-party embed loads when you open a page.

Filing a bug

support.vros.cat is the one place on these sites where you send something. A submitted report becomes an issue on the bug tracker, and support.vros.cat mirrors that tracker, so a filed report is public: anyone can read it, including everything you typed into the form.

That includes anything you paste in: logs, hardware details, whatever is visible in a screenshot. Send what the bug needs, and nothing you would not want sitting in a public thread. The form asks for no contact address and none is stored.

If you would rather talk than file, Discord works too.

Steam

vrOS is sold on Steam. Valve handles the purchase and your account identity; vrOS never sees your payment details. What Valve collects is covered by their policy, not this one.

Steam Privacy Policy

Questions

For anything on this page, ask in Discord or send it through support.

Discordsupport.vros.cat