Check what a private-time control actually changes
Test boundaries around pausing collection and retained metadata.
Check whether pausing collection meets the actual boundary you need, including what is retained before, during and after the pause. A private-time button is not a complete privacy policy.
Separate availability from authority
DeskTime documents a Private time feature, while its help material says an administrator can restrict its availability. Verify both the feature and the setting with the role people actually use. Separately establish the organization’s authority and communication for collection; the presence of a control does not settle employment or privacy obligations.
Test a fictional boundary case
Under the approved evaluation setup, note the time before the pause, enter private mode, and inspect what the user and permitted reviewer can see afterward. Ask which timestamps, state changes or duration summaries remain. Do not assume that a pause deletes information already collected. Avoid using real personal activity as test material; a labeled fictional interval can establish the interface behavior.
Explain what contributors can expect
A clear instruction distinguishes pausing future capture from deleting historical records, and states who may change the control. If a setting can be disabled, explain the resulting workflow before rollout. If the required boundary is “no collection from this personal device,” a pause control may be the wrong mechanism; consider an approved manual process or a separate work environment.
Stop if the boundary cannot be demonstrated
Do not recommend collection merely because a feature has a reassuring name. Mark an undocumented behavior unresolved and request a demonstration or written clarification. Keep any retention or deletion promise limited to what has been verified. This page offers a configuration-check method, not a determination that a monitoring practice is lawful.
Continue this work-record check
Use the linked guide for the next decision in this workflow. Keep your original records separate from experiments and record any unresolved requirement before changing a live process.
Sources and boundaries
Primary documentation supports the dated product facts. Proposed checks and fictional examples are our editorial method, not observed product results.
- DeskTime — private · checked September 23, 2026
- DeskTime — private admin · checked September 23, 2026