RewindOS is local-only — your screen history never leaves your machine. It reaches the network for one thing: a daily check-in (the app's update check and the capture daemon's heartbeat). Here is exactly what that records, in full.
One row per day per version per desktop — counts only. Version and desktop are install attributes (which release is live, KDE vs GNOME), kept as aggregates, never tied to you. No IP, no identifier, no account, no payload, no per-event log — there is no other table. The live contents are at /stats.json.
On each check-in the worker hashes your IP together with the date and a random, server-only salt, uses that hash to dedupe within the day, then discards it — a day's hashes are dropped once the next day's first request arrives, leaving only the counts above. The salt never leaves the server, and because the date is part of the hash, a device can't be linked from one day to the next.
Counting is by IP, so devices is approximate: a shared network merges several into one, a dual-stack connection can split one into two. It's a rough floor, not a precise headcount.
usage_heartbeat = false under [privacy] to send nothing.This page is served by the same worker the app checks in to — read its source, or take the raw counts from /stats.json. The desktop app is open source too: every request it makes is in updater.rs.