History & data
What Guardian records, where the data actually lives, and how long each tier keeps it.
Guardian keeps two kinds of history: the record that always lives on your own device, and an optional hosted copy in the cloud so you can look back from anywhere. This page explains both, plus exactly where your data sits and what the cloud does and doesn’t store.
On-device history: always on, always free
Every device running the app keeps its own history locally, on every tier:
- Usage history — water flow, battery voltage, and power readings, bucketed into hourly aggregates and shown as charts in the app.
- Event log — flood alarms, valve opens and closes, threshold crossings, and other notable events, in the order they happened.
There is nothing to enable and nothing to pay for.
Cloud history: opt-in, per vehicle
Cloud history is an opt-in setting on each vehicle. When enabled, sensor data flowing through the cloud path is also retained in your vehicle’s cloud record, so any of your devices — or anyone the vehicle is shared with — can browse the same history from anywhere.
| Plan | Hosted retention | Export |
|---|---|---|
| Free | On-device only — no hosted history | — |
| Basic | About 1 month | — |
| Premium | About 3 years | CSV export |
Where your data lives
Two places, and only two:
- Your device — the app’s local usage history and event log, plus all of your settings.
- Your vehicle’s cloud record — if you use the hosted cloud, each vehicle has its own document holding synced settings, the last-known sensor state, and (when opted in) its tier’s history window.
The cloud worker’s role is deliberately small. It caches each vehicle’s last-known sensor state so the app can show status from anywhere, forwards push notifications, and can close the valve on a flood event. It retains history only for vehicles that opted in, at their tier’s retention — it does not build profiles, and it has nothing from vehicles that never enable the cloud path.