Passthrough panels: what we log, and what we refuse

Mixed reality features tempt teams to hoard data. We start every passthrough workshop with a refusal list: what we will not retain, where we will not send frames, and which APIs stay off by default. Learners draft a one-page tester brief that mirrors the product README. If marketing screenshots need a living room, we use stock cubemaps instead of teammate apartments — boring, but kind. When depth is available, we practice degradations: flat planes, conservative bounds, and explicit UI when data is missing. The goal is predictable behavior, not maximal fidelity. We are educators, not counsel. The template points to Japanese privacy references, but every shipping team should validate with their own legal advisors before launch.