governance
Security & Data Handling
Security baseline and data governance guidance for deployments.
Security & Data Handling
Data Classification
Telemetry payloads are free-form JSON, so classification is a naming decision. Keep personal or sensitive values out of metric keys and payload bodies.
Encryption
- Platform APIs and client streams run over TLS; device transport hardening is in active development
- The Unreal plugin keeps credentials in its secure-storage path; the local twin cache is SQLite inside the project
Access Control
- Organization administrators manage the users, projects, and devices inside their own organization; a read-only user role also exists, and API keys carry per-key scopes
- Organization-scoped tenancy — every resource is bound to your organization
- Sign-in issues a 1-hour access token, refreshed against a 30-day refresh token
Retention Governance
Historical telemetry is retained server-side and queryable through the time-series endpoints. One stored reading is kept per device per minute, written in batches, so history trails the live stream by up to a minute. The live stream itself is not averaged.