Privacy

WHAT'S STORED ON YOUR DEVICE

WHAT GETS SENT BACK

Anonymous analytics through PostHog: page views (the route you land on, the site that referred you, and any campaign / utm / ?src tag on the link), and the runtime events that show how the build performed for you (first-pixel time, how long until you could drive, frame-rate samples, whether the scene loaded cold or from the warm cache, arena selections, photo captures, settings touches). No account, no email, no cross-site tracking. The point is to know whether the build runs fast enough on the hardware people actually have, and, during launch, which channel sent you.

Once per browser, a single snapshot of the kind of machine you are on: number of processor cores, rough memory size, the graphics chip, screen size, network type, storage headroom, and your browser and operating system. It is read during an idle moment so it never slows the page, and it is sent once, not on every visit. It is what lets me say whether a photoreal scene really runs on an ordinary laptop. It carries no name, and no exact serial or precise device ID: browsers do not expose those, and I do not try to rebuild them.

When something breaks, the page sends a short fault report: the error message, where in the code it happened, and the page you were on, alongside the device snapshot above. The live site has no console, so a fault report is the only way I find breakage on hardware I cannot test on myself. It contains no personal content.

The analytics service works out an approximate location (country, region, city) from your IP address, the way most websites do. It is coarse, and I use it only to see where the demo is reaching. There is no precise or GPS location, and nothing follows you onto other sites.

PostHog is hosted at eu.i.posthog.com (European Union). Their policy is at posthog.com/privacy.

If you tap the settings drawer's analytics opt-out chip, all of the above stops and nothing leaves your device. The opt-out sticks and travels with the settings record above.

The exact set of events, and the data each one carries, is defined in the source. Reach out via /contact if you want a sample dump.

Want to see what your browser has stored about your sessions (lifetime stats, photo hunt progress, achievements)? /data renders the lot. Pure read, nothing leaves the device.

IF YOU JOIN THE WAITLIST

Two screens offer a waitlist field: the compatibility wall (when your browser can't run WebGPU yet) and the mobile coming-soon screen. They're the only places WASCAPE asks for an email, and only if you choose to type one in.

What gets stored: the address you enter, which of the two screens captured it, and a timestamp. It's written to a Cloudflare store, kept apart from the anonymous analytics above. It buys you exactly one thing: a single message when the build reaches your browser or your phone. Never sold, never shared, no marketing drip.

Want off the list, or want it deleted? Mail /contact and it's gone.

WHAT IT DOESN'T DO

• ·No third-party ad networks, ever.
• ·No selling, renting or sharing telemetry data.
• ·No cross-site tracking and no advertising profile. The device snapshot is read once to size performance, not to follow you between sites.
• ·No precise or GPS location. The only location signal is the rough city and country your IP implies.
• ·No email unless you hand it over on the waitlist. Analytics never carries it.
• ·No autoplaying audio. The AudioContext primes silently and only un-mutes on a real user gesture.

WORLD CAPTURES

The drivable scenes are real-world Gaussian-splat captures. They were sourced from public datasets or self-captured; identifying information visible in the scene (faces, license plates, etc.) is incidental to the photograph and we don't process or recognise it.

CONTACT

Questions, opt-out requests, takedown requests: [email protected]

response within 48 hours · founder reply