Developer preview
Security & access
Handle enterprise identity, device permissions and application data at the layer that owns them.
Three different access relationships
| Relationship | Purpose |
|---|---|
| Worker → your app/backend | Your enterprise identity and session authorize use of business data and application services. |
| Phone → glasses | Bluetooth pairing, device identity and firmware capability establish the local connection. |
| Developer service → Lucyd platform | Future portal-issued credentials will authorize specific platform APIs when those services launch. |
Portal credentials authorize Lucyd platform services; local device access is governed separately by the supported pairing and device-security design. Any device-side authorization needs support in the firmware and SDK. Final Lucyd token types, scopes, expiry and revocation behavior will be published with the account services.
Handle credentials safely
- Keep long-lived service secrets on a controlled backend; do not embed them in a mobile app or browser JavaScript.
- Exclude device-network credentials, pairing material, tokens, private keys and user content from logs.
- Redact credential-bearing data before formatting object descriptions or serialized output.
- Bind recovery/sync records to the correct user, organization, device and asset.
Capture and data ownership
Request OS permissions in context and show what the app is doing. Preserve any device privacy indicator and follow the published capture behavior.
Define storage, retention and deletion across the device, phone and backend. Save and verify a transferred file, record durable sync, and then request deletion of the exact device file. Treat unknown capture or transfer outcomes as unresolved state.
Transfer and update trust
Transfer security, credential handling and supported network behavior will be documented with the SDK release.
For firmware, verify authenticity with the approved package/signing scheme in addition to integrity and compatibility. Keep private signing keys outside the app. Document how interrupted firmware updates recover before releasing OTA workflows.
Partner access in this preview
This workspace preview uses sample data and does not authenticate users, issue credentials or connect to a device. Public registration and access services are planned for 2027.