Acceptable use

Updated: Sep 18, 2026

Before you build

Everything you build on this platform is bound by the Acceptable Use Policy⁠ and the developer terms⁠. Both apply in full and are the binding instruments — read them before you start. The guidance below tells you what we are looking for; it does not narrow, replace, or exhaustively restate either document.

What we encourage

Experiences that are uniquely possible or better on glasses, for example:
  1. Hands-free capture and logging — sport, fieldwork, inspection, inventory, repair.
  2. Assistive and accessibility — scene description, captioning, live translation, navigation aid.
  3. Context on demand — the wearer points at something and asks; you answer. Deliberate, not ambient.
  4. Motion and input — gesture control, activity and form tracking, coaching.
  5. Enterprise workflows — guided procedures, remote expert assistance, compliance checks, with clear on-site notice to everyone present.
Design principle: narrow purpose, short retention, obvious to bystanders.

We review and we enforce

We review Device Access Toolkit apps, monitor them afterwards, and investigate reports. Where an app breaches the Acceptable Use Policy⁠ or the developer terms⁠, we may act without prior notice — including revoking your app’s access to any or all device capabilities, removing it from distribution, and suspending or terminating your developer account and associated accounts.