Secure V2 · SDK 0.3.0
Telemetry, history and retention
Updated October 11, 2026 · verified against repository implementation
Understand what is stored and what a successful send proves.
Readings and history
Overview loads at most fifty retained samples for the selected device, not the entire telemetry history. Live updates supplement that bounded query; if realtime is unavailable use Refresh. Stored JSON is gateway-decoded data, while the chart joins numeric samples without inventing intervening readings.
A newly added device has its own setup guidance even when workspace onboarding is already complete. An inactive existing device needs troubleshooting rather than first-time account onboarding. Empty history can mean retention, not that a device never worked.
Retention
Existing retention is one day for Free, seven days for Flexible, and thirty days for Pro/Scale. Account Billing and current entitlements remain authoritative. Retention removes old sample rows but preserves workspace completion and durable device activity evidence.
Keep long-term history in your own downstream system where necessary. A webhook that succeeded before retention is separate from the sample still being visible in Overview.