Security and data handling
These controls are implemented in the repository. Production rollout and policy commitments require separate verification.
Implemented controls
Account sessions
The gateway issues random session tokens and stores their hashes. Session cookies use Secure, HttpOnly, and SameSite=Lax attributes. Signing out revokes the session family on the server.
Telemetry access
Telemetry reads check the account session and current tenant membership. Device queries are scoped to that tenant. Responses use private, no-store cache controls.
Device credentials
Uploads use a separate device bearer credential; the database stores its hash. A revoked credential cannot authorize a new upload. Device credentials do not grant access to account telemetry queries.
Validated, durable uploads
Ingestion validates packet structure, provisioned channels, value ranges, and timestamps before committing readings. An acknowledgment follows a successful transaction. Identical retries do not duplicate stored samples.
Before launch
The security patch policy, supported device lifetime, vulnerability reporting process, privacy notice, and terms are still being defined. Automatic signed firmware updates and a fleet patch rollout are not currently provided by this portal. This page does not establish a patch-duration, compliance, or service guarantee.
Keep session cookies, email codes, device tokens, and Wi-Fi passwords private. Use a local development device for simulator experiments.
Read the setup and telemetry guides