The Ruwad Connect desktop tracker takes screenshots only while a person is punched in, from every monitor, at a cadence the workspace's plan sets and the server enforces. Nothing is captured before the person has given consent, and blur can be turned on so a reviewer sees the shape of the work rather than its content.
The short answer. The rest of the page explains it.What is captured, and when
The desktop tracker is a small app on the person's computer. It records only while someone is punched in on a project and a task. Punching out, or taking a break, stops the timer, and a stopped timer captures nothing. There is no background mode that watches a machine outside working sessions.
While the timer runs, the tracker takes a screenshot of every monitor at the workspace's cadence. Each capture is uploaded with:
- the time it was taken,
- the monitor it came from,
- an activity level for the minutes around it, derived from keyboard and mouse input counts (never the keys themselves),
- the name of the application that was in the foreground.
Those captures appear on the Captures page in the web workspace, laid on an hourly activity chart, and each one gets a short AI description and a category such as coding, design or meeting on plans that include analysis.
Who sets the cadence
The cadence is a plan limit, not a desktop setting.
| Plan | Screenshots an hour |
|---|---|
| Free | 1 |
| Starter | 12 |
| Professional | 30 |
| Enterprise | Up to 30 |
Enterprise sets no plan limit, but 30 an hour (five every ten minutes) is the densest cadence the tracker offers, so that is the most any plan captures.
The desktop reads the cadence from the server every time it starts a session. An admin can lower it in Capture settings; nobody can raise it above the plan from the desktop, because the server refuses a setting above the cap. Moving up a plan is how the limit is lifted.
Blur
Blur is a workspace setting. When it is on, the tracker blurs each screenshot on the computer before uploading it, so a reviewer sees which application was open and roughly what the screen looked like, but not the text on it. The setting lives on the server and every tracker reads it from there, so a person cannot switch it off for their own captures. The server applies the same blur to every screenshot it receives while the setting is on, so a capture taken before a tracker picked up the change is stored blurred all the same.
Consent comes first
The first time the tracker runs for a person, it shows what the workspace records: screenshots and their cadence, webcam checks if the workspace has turned them on, and activity levels. Nothing is captured until they have accepted. The consent text is versioned, and the version a person accepted is checked by the server before tracking starts. When Ruwad Connect publishes a new version of the consent text, everyone is asked again. Changing a workspace setting, such as turning on webcam checks, does not ask again by itself, so tell the team before you change what is recorded.
Where the captures live
Captures are stored in private object storage. The web workspace never links to a capture directly; every read goes through a short-lived signed link, so a capture URL cannot be shared and opened later by someone outside the workspace. Retention follows the plan: Free keeps 30 days, Starter a year, Professional and Enterprise as long as the workspace exists.
What is never recorded
- Nothing while the timer is stopped or paused.
- No keystrokes. The activity level is a count, not a log.
- No webcam images unless the workspace turns webcam checks on, and then only inside the working hours it sets.
- Nothing for clients to see. Clients do not sign in; they receive invoices and receipts built from approved hours, never a capture.