Employee monitoring transparency
How WorkPulse Can Monitor Work Activity
A clear description of the monitoring capabilities in WorkPulse for employees, contractors and other tracked users.
Last updated: 26 August 2026
1. When monitoring can happen
WorkPulse is a workforce-management platform. Its desktop and mobile clients can collect activity information when a Customer has enabled tracking and you are using a tracked work session. The scope depends on the Customer's plan, settings, the application installed on your device and the permissions granted to that application.
Desktop activity capture is paused by the current desktop client during its in-app break mode. Mobile location collection can be governed by a different workflow, so your employer's own notice should state exactly when location tracking starts, pauses and stops for your organisation.
2. What may be collected
| Category | What this can include |
|---|---|
| Work time and work context | Start and end times, projects, teams, breaks, idle periods, manual time requests, approvals, reports and activity levels. |
| Keyboard and mouse activity | Counts and individual keyboard and mouse events with timestamps. Keyboard events can include the actual characters typed or key names such as “Enter”, not only a keystroke count. |
| Application and browser context | Foreground application or process, program-use records and browser-window-title context. A window title can reveal a website, document title, search term or other on-screen content. |
| Screen captures | Periodic whole-screen screenshots, including all connected monitors. Standard desktop capture uses approximately ten-minute windows; an enabled feature can add screenshots approximately every two minutes. |
| Screen recording and camera | An authorised manager can request a short screen recording during an active desktop session. Camera images are a supported optional capability where a compatible client and feature are enabled. |
| Mobile location | Precise latitude, longitude, accuracy, reverse-geocoded address and timestamps while mobile tracking is used. |
| Messages, files and work records | Messages, attachments, tasks, project records, payroll-support information, reports and other information added to the Customer workspace. |
| Device and security information | Device identifiers and platform details, IP address, login history, browser or device information, push-notification tokens and security signals. |
3. A critical point about typed and on-screen content
The current Windows desktop client records individual key values during active tracking. It does not have a source-code-enforced exclusion for password fields, particular applications or other sensitive inputs. Its whole-screen captures and manager-requested recordings can also contain personal or sensitive content that appears on screen.
This means that WorkPulse should not be described as collecting only “keystroke counts” or only “work-related” content. Your employer must carefully assess whether this collection is necessary and lawful before it enables or uses the feature.
4. Who can see the information
Within a Customer workspace, access is controlled by roles and permissions. Depending on the Customer's configuration, authorised administrators, managers, team leaders, payroll staff and other permitted users may be able to see parts of your activity, reports, time records or files.
Your employer may also configure scheduled reports, email notifications, data exports or HTTPS webhooks. Those can send selected session information to recipients or systems chosen by your employer. WorkPulse's Privacy Notice explains these categories in more detail.
5. AI Time Reports
If an authorised Customer user chooses to use the optional AI Time Report feature, WorkPulse can send a derived report prompt to OpenAI. The prompt can contain aggregate time and activity figures, leading application or browser-title context and derived typed-keyword signals. It does not send screenshots, screen recordings, GPS location, raw messages or full raw key-event arrays as part of that feature's reviewed code path.
AI output should be reviewed by a person. It should not be the sole basis for an employment, performance, pay, disciplinary or other materially significant decision.
6. Your employer's responsibilities
Before using monitoring, your employer should explain:
- its identity and privacy contact;
- the lawful basis and business purpose for each type of monitoring;
- the devices, work periods and users covered;
- which WorkPulse features it has enabled, including screenshots, individual key capture, recordings, location, reports, webhooks and AI reports;
- who can access the records and any external recipients;
- how long it retains each category of information; and
- how you can ask questions or exercise your privacy rights.
Your employer remains responsible for complying with applicable employment, monitoring, privacy, labour and consultation requirements. It should carry out any required impact assessment and use human review for significant decisions.
7. Retention and your rights
The current source code does not establish a verified universal automatic deletion period for current desktop screenshots, two-minute screenshots, recordings, keyboard-event records, session data or location records. A pruning task targets some legacy file paths only. Your employer should tell you the actual retention period it applies and should not assume that account or tenant deletion automatically removes every historic work record, capture file or backup copy.
For access, correction, objection or deletion requests about work records, contact your employer first. You can also read the Privacy Notice and use the data deletion request form for an account-related request.