Monitoring — what is recorded, and who sees it
A plain accounting of CronCrunch's opt-in activity and screenshot capture — what's collected, when, who can view it, and how to turn it off.
View as MarkdownMonitoring is off by default and strictly opt-in, per person. When you enable it, the CronCrunch desktop app can record which app and window title you have focused, and take periodic screenshots. Only you can view your captures — there is no manager or team view — and you can turn it off any time.
This page states exactly what monitoring does, based on how the product is built — not on what a sales page would like it to do.
What is captured
Two independent channels, each with its own toggle on the Monitoring page:
| Channel | Exactly what's stored |
|---|---|
| Record active app & window title | The focused app's name, its window title, and the start/end time of that focus — nothing else |
| Take periodic screenshots | A screenshot image (up to 5 MB) and the time it was captured |
Either capture can be linked to the time entry it happened during, so it shows up in context.
And what is not. CronCrunch has no way to receive keystrokes, mouse movement, webcam or microphone recordings, or browsing history — the service simply has no endpoints for them. The two channels above are the entire surface.
When capture happens
- Off by default, for everyone. A brand-new account has both channels disabled. Monitoring only starts if you switch it on.
- Enforced by the server, not just the app. When a channel is off for your account, the CronCrunch service rejects any capture sent for it. It's not a client-side setting that software could quietly ignore — the toggles are the enforcement boundary.
- Capture comes from the desktop app. The web app at app.easerix.com never records anything; it only shows your settings and what has been captured. To capture at all you need the CronCrunch desktop app running and signed in as you.
- Screenshots run at the interval you choose — every 2, 5, 10, or 15 minutes (5 by default).
- Your consent is timestamped. The first time you enable either channel, the moment is recorded and shown on the Monitoring page ("Consent recorded …").
Who can view it
Only you. Every screenshot and activity event is stored against your own account, and every way of viewing them returns only your own. There is no manager view, no admin view, no teammate view, and no organization-wide export — those capabilities do not exist in the product today.
Sharing a project with your organization changes nothing here: shared projects let teammates log their own hours; they never expose your entries, your activity, or your screenshots.
Screenshot images live in private storage and are displayed through links that expire after ten minutes — there is no permanent public URL to a screenshot.
How to turn it off — and what happens to the data
- Open Monitoring in the CronCrunch sidebar.
- Switch off either toggle (or both). From that moment the server rejects new captures on that channel.
For data that already exists:
| Data | Deleting it |
|---|---|
| Screenshots | Delete any screenshot individually from the Monitoring page — this removes both the record and the stored image, and cannot be undone |
| Activity events | There is currently no way to delete individual activity events in the app. Turning the toggle off stops new recording, but past events remain visible on your timeline |
Reviewing your own captures
The Monitoring page shows your last 7 days in two tabs:
- Screenshots — thumbnails grouped by day, each with its capture time and a delete button.
- Activity — a per-day list of app + window title with the time and duration of each focus stretch.
Frequently asked questions
Can my employer require this and see my screen?
CronCrunch has no mechanism for that today. The settings are per-user and self-service, and captures are only viewable by the person they belong to. There is no admin override and no manager dashboard.
Does monitoring only run while my timer is running?
The in-app description says the desktop app records only while your timer runs, with a visible indicator. What the server enforces is your toggles: with a channel enabled, it accepts that channel's captures regardless of timer state. Treat the toggles — not the timer — as the on/off switch that actually binds.
If I delete a screenshot, is the image really gone?
Yes — deleting removes the database record and the stored image file. The Monitoring page asks for confirmation because it cannot be undone.
Is anything captured from this web page or my browser?
No. Capture requires the desktop app. The web app only reads and manages what was captured.
Last updated on