Monitoring and Workplace Transparency Notice

Exactly what the Projments desktop agent captures while you track time, what it never captures, who can see it, and what you can control.

Effective: 16 August 2026
Last updated: 16 August 2026
Version: 1.0

In short

While your timer is running, the agent captures screenshots of your screen, counts key presses and mouse clicks, and records which application is in front.
It never records what you type. Keys are counted, not identified — there is no keylogger in Projments.
Nothing is captured when the timer is stopped. Stopping the timer stops the capture, immediately and completely.

This summary is for orientation only. The sections below are the document that applies.

1. Why this notice exists#

Projments includes a desktop agent that captures screenshots and activity measurements while a person tracks time. Software of that kind should never be a surprise to the person it is pointed at, and in many countries a surprise is also unlawful. This notice is written so an employer can hand it to their team unedited.

It describes what the software does. Whether it is switched on, and for whom, is decided by the organisation that runs your workspace — not by us. See §6 for the duties that come with that decision.

2. What the agent captures#

Capture happens only while a timer is running against a project or task, and only on the machine running the agent. When you start a timer, a first snapshot is taken straight away and then repeats at a regular interval — currently about once a minute — until you stop.

Each snapshot contains

A screenshot of your screen as it looked at that moment, uploaded and stored against the time session, with its dimensions and file size.
The number of key presses since the previous snapshot — a count only.
The number of mouse clicks since the previous snapshot — a count only.
An activity percentage derived from that input, or from system idle time where input cannot be counted.
The application in the foreground when the snapshot was taken, taken from the window title.
When it was taken, and which project, task and time session it belongs to.
Any memo you attached to the timer yourself.

Where the input-counting component cannot load on a machine, the agent says so rather than guessing: the counts are recorded as “not measured” instead of zero, and only an idle-derived activity percentage is sent. A blank count means the machine could not measure it — not that you did nothing.

3. When it is not capturing#

When the timer is stopped. No timer, no capture — including outside working hours, at weekends, and on leave.
When the agent is not running, or the machine is off.
On machines without the agent installed. The web app and the mobile apps take no screenshots at all.

4. What your workspace controls#

Workspace owners set the monitoring policy for their workspace under Settings → Snapshots:

Setting	What it governs	Default
Screenshots	Whether screenshots are captured at all	On
Interval	How often a snapshot is taken while a timer runs	Every 10 minutes — see the note below
Cap per hour	An upper bound on snapshots in any one hour	Not set
Blur sensitive areas	Blurs the captured image before it is stored, at low, medium or high strength	Off
Capture active apps	Whether the foreground application is recorded alongside the snapshot	On
Capture app titles	Whether the window title is recorded, not just the application	Off
Activity tracking	Whether key and click counts are measured at all	On
Allow members to pause	Whether a member may pause screenshots during a session	Allowed
Retention	How long snapshots are kept before they should be removed	30 days

These settings are how your organisation records its monitoring policy, and your owner can tighten them at any time. The desktop agent currently captures on a fixed short cycle of roughly one minute rather than the interval configured here; where the agent’s behaviour and a setting differ, §2 describes what is actually happening on your machine, and we would rather tell you that than let this page imply a protection you do not have. If anything else you observe differs from your workspace’s policy, raise it with your workspace owner and tell us in our Support Center.

5. Who can see it, and for how long#

You can see your own snapshots and activity in the app.
Workspace owners, administrators and members whose role grants access to worklog data can see them for the members they manage.
Our staff access them only when strictly necessary to operate or debug the service, or when your workspace owner asks us to, and such access is logged.
They are stored in encrypted object storage and served through short-lived signed links, never public URLs.
Your workspace sets how long snapshots are kept — 30 days by default. Deleting the time session, the project or the account removes its snapshots with it, and a workspace owner can ask us to purge older snapshots at any time. The full schedule is in the Data Retention Policy.
They are not sold, not shared for advertising, and not used to train any model.

6. If you are the employer#

Enabling monitoring makes you the controller of the resulting data. That is a legal position with obligations attached, and they are yours — we cannot discharge them for you.

Tell people first, in writing. Before you switch anything on. Handing out this notice, with your own retention period and reasons added, is a reasonable way to do it.
Have a lawful basis. In most of Europe consent from an employee is not a valid basis, because the relationship is unequal — you will normally need to demonstrate a legitimate interest, and to document why less intrusive means would not do.
Keep it proportionate. Monitor working time, not people. Blur sensitive areas, lengthen the interval, shorten retention: choose the least intrusive settings that still meet your purpose.
Do not monitor covertly. Secret monitoring of staff is unlawful in many jurisdictions and is a breach of the Terms of Service.
Do not point it at private life. Not at personal devices, not outside working hours, not at anyone who has not been told.
Answer your people. Access, correction and deletion requests about monitoring data come to you, because the records are yours.
Check your local law. Works-council consultation, prior notification of an authority, or an impact assessment may be required before you begin.

7. If you are being monitored#

You are entitled to know that monitoring is happening, what is captured and why. This notice is part of that; your employer owes you the rest.
You can ask your employer for a copy of the monitoring data held about you, and for correction of anything wrong.
You can ask that a snapshot which caught something private be deleted. Your employer decides, and can always delete it.
You can stop the timer at any time. Nothing is captured while it is stopped, and where your workspace allows it you can also pause snapshots during a session.
You can complain to your local data-protection authority if you believe the monitoring is unlawful or disproportionate.
You can raise a request with us in our Support Center. We will tell you what we hold and pass your request to your workspace owner. We will not delete your employer’s business records on your instruction — see Privacy Policy §2 for why.

8. Contact#

Questions about monitoring: our Support Center. See also the Privacy Policy and the Data Retention Policy. This version is 1.0, effective 16 August 2026.