WorkBeat · Updated 16 October 2026
Employee data notice
A clear view of your work data. WorkBeat helps your employer manage work and attendance. The features enabled by your employer determine what is collected. Your employer should provide its organization name, privacy contact, purposes and applicable workplace policy before use.
What WorkBeat records
- Account details such as your name, email, department, role and assigned permissions.
- Attendance punch-in/out times and related work records.
- Device-reported GPS coordinates at attendance punches, during enabled attendance tracking and at enabled task check-ins.
- Browser/device labels and a device-binding hash used by attendance device registration. Resetting registration removes that binding.
- Tasks, comments, task history, billing and reimbursement records, receipts and attachments when those features are used.
- Administrative activity and access records for supported workflows.
Location is indicative. GPS and browser/device information can be inaccurate or spoofed. Reported location is not proof of physical presence.
Storage and who can view it
This PHP edition stores each company's records in its configured MySQL database. Uploaded receipts, profile photos and task/comment attachments are stored as private application files outside the public website folder.
Workspace access depends on your role and permissions. Administrators and people explicitly granted tracking access can view the attendance and tracking records available to them. Platform administrators can open time-limited, audited support sessions where that feature is used.
Some enabled services, such as external maps, email or identity providers, may process data required for those features. Your employer and service operator should identify the actual hosting region and providers used by their deployment.
What is kept and what expires
| Data | PHP edition behaviour |
|---|---|
| Attendance GPS samples and tracking events | Expire after 60 days by default. A company's explicit retention setting takes precedence. |
| Older attendance coordinates, location text and punch device details | Cleared after the configured period. Attendance rows and punch-in/out times remain. |
| Task records, task check-ins, billing and work history | Task and expense records, approvals, comment text and punch/check-in times remain. Task check-in/out coordinates expire after the configured location-retention period, 60 days by default. |
| Receipt files and task/comment attachments | Expire after 60 days by default, based on receipt upload or comment creation time. Expense amounts, approvals, comment text and file metadata/expiry markers remain. Profile photos follow account management rather than this attachment cleanup. |
| Registered-device binding | Remains while registration is active; reset or deletion removes the registration. |
Automatic cleanup requires the company's maintenance job to run on the hosting server. Active platform legal holds pause location and attachment cleanup. Provider backups have a separate retention period and may temporarily retain older copies.
Questions and requests
For access, corrections, questions about tracking or a request to remove information, contact your employer's administrator or designated privacy contact. Your employer decides the purposes, applicable retention requirements and available attendance alternatives.
This page describes the PHP edition's current behaviour. It does not replace an employer's own privacy notice or workplace policy.