Privacy

Diagnostics

When. Development (debug) builds, the ones we test with, send diagnostics by default. Release builds send nothing until you turn on Send diagnostics in Settings, and stop when you turn it off.

What a record says.

• That the app launched, and the state of its camera tracking (AR on phones, the QR tracker on the Quest).
• That a code was looked up, how long it took, and whether it worked, with the reason when it didn't.
• That a glyph was placed in the room. On the Quest this includes where it was placed relative to the headset, in the room's own coordinates, so we can tell whether panels land on their codes.
• That you pressed Forget, and errors the app ran into.
• On a TV: that a glyph arrived from a phone, and whether its network listener is running.

About a code, only where its content comes from: whether it is a web address, a Bluetooth share or a document inside the code, the address's scheme (https, blue), and for web addresses the host name, such as glyphs.apphaus.us.

Never: the text of a code, the path of a web address, a Bluetooth device's name, glyph content, anything you type into a form, what you say, camera images, your AI key, or your name or account.

Also with each batch: the app's version, whether it is a debug or release build, the platform (iOS, Android, Quest, tvOS, Android TV), its role (phone, headset or TV), a random install id made on the device (not tied to you or your account), and a random id for each launch.

Where it goes. To telemetry.apphaus.us, a server we run on Cloudflare. It accepts only the fields above, drops anything else, and blanks out anything that looks like a key or token. Your IP address is used only to limit how often a device can send; it isn't stored. Records are deleted after 7 days.

Looking up glyphs

A code tells QRX where to fetch its content, so your device asks that server for the document, the pieces it shares and its media, like a browser opening a page. That server sees the request and your IP address under its own policy: for the demo codes it is this site (served by Cloudflare) and GitHub, which hosts their 3D models; for other codes, whoever hosts them. Codes that carry their document inside need no request at all.

Camera

QRX looks for codes in the camera picture on your device. No camera images or video leave it.

AI characters and speech

Characters in a 3D scene can think with an AI provider you choose (Anthropic, OpenAI, Gemini, or a server of your own). Until you add a key in Settings, they follow built-in rules and no AI request is made. With a key, your device sends the character's persona and what it notices (how far away you are, the time of day, what you said to it) straight to that provider, using your key and under that provider's terms. Your key is stored encrypted on the device (Keychain on Apple devices, Android Keystore on Android) and goes only to the provider it is for.

The mic button uses your device's own speech recognition (Apple's or Google's). Depending on your device and language, the system may send the audio to Apple or Google to turn it into text. QRX passes the text to the scene's characters, and so to your AI provider if you set one up; it doesn't store it or send it anywhere else.

Sharing with other devices

• Show on TV is off by default. When you turn it on, your phone or headset sends each glyph it finds (the code's text and its document) to every QRX TV on your home network. This travels unencrypted, and any device on the network can see it or send a glyph to the TV.
• Bluetooth sharing is off by default too. While it is on, nearby QRX devices can fetch the glyph documents your device holds and send it new ones, without a password.

This website

qrx.apphaus.us is a plain static site: no cookies, no analytics, no third-party scripts or fonts. The glyph generator runs entirely in your browser. Cloudflare serves the site and keeps the usual request logs under its privacy policy.

Questions

Open an issue on the site's repository.

Last updated 18 October 2026.