Privacy
What DisplayXR's own software does with your data.
The DisplayXR runtime
The DisplayXR runtime, its background service and its tracking process run on your device. They have no accounts, no analytics and no crash reporting. Diagnostic logs stay on your device (on Windows, in %LOCALAPPDATA%\DisplayXR). The DisplayXR runtime goes online only to download model files for optional 2D-to-3D features. An optional feature can send a photo to a conversion server you choose; it is off by default and asks for your consent first.
Eye tracking
Eye tracking runs on your device, in the display's plug-in or in DisplayXR's open camera tracker. The open tracker processes camera images in memory and never saves or sends them; only eye positions come out of it, and the DisplayXR runtime keeps them on your device. Apps receive the views they need to draw in 3D, which are based on where your eyes are, and an app can also ask for the eye positions themselves.
Some displays have a built-in 3D camera. An app can use it only after you allow it, and browsers ask per website.
Plug-ins and devices
The display's plug-in and your device's tracking software come from the display maker, and the display maker's privacy policy applies to them.
DisplayXR Browser
The DisplayXR Browser is built on Chromium. It has no account, no sync and no usage or crash reporting. Its start page, hosted on GitHub Pages, checks updates.displayxr.org for a newer version with a plain request that carries no identifier, and nothing installs by itself. Like any Chromium-based browser, it still contacts Google for Safe Browsing, certificate-revocation and component updates, and for search suggestions if Google is your search engine.
DisplayXR Chat
Calls go directly between browsers, encrypted. The signaling server sees your IP address, your browser type and the page you connected from. It receives the room code only to admit you to the room, keeps it in memory and never logs it, and it relays the connection handshake between participants without storing it. It never sees your audio, video or shared 3D content. When a direct connection is impossible, a relay forwards the encrypted media; it sees IP addresses and the amount of data, but cannot read the media. Rooms exist only in memory and disappear when the call ends or after two hours. There are no accounts, no recordings and no tracking; the only record kept is a monthly usage total per API key, and the Chat app uses no key. Your display name goes only to the other people in the call, and Share 3D sends an app's 3D view the same way as your camera, after you approve it. Our hosting and relay providers keep standard connection logs for a limited time.
DisplayXR Gallery is a separate website with its own sign-in and policy.
DisplayXR plugin for Claude Code
The displayxr-inline3d plugin helps a coding agent in Claude Code build and check 3D web pages. It sends nothing to DisplayXR: no telemetry, no accounts, and nothing runs in the background.
Its page checker runs on your computer, in a headless Chrome and a local server on 127.0.0.1. The page under test loads what it normally loads, such as its scripts from a CDN, and nothing else leaves your machine. When the agent optimizes a 3D model, it downloads a pinned open-source tool from the npm registry.
Generating 3D assets is optional and paid. It sends your prompt or image link, with your own API key, directly to the provider you pick (Meshy, Tripo or OpenAI), and only after you approve that call and its estimated cost. That provider's privacy policy and terms apply. The plugin reads your keys from your environment and never prints, stores or sends them anywhere else.
Questions
Open an issue on the DisplayXR runtime repository on GitHub.