Help center
How can we help?
Answers on capture, workflows, evidence, privacy, and your account.
Browse by topic
Getting started
Rolling out unpak: deploying the capture agent and choosing where to start.
Privacy & security
What unpak observes and who can see the data it collects.
Workflows and Reports
Reading reconstructed workflows, how times and counts are computed, and drilling from any number to the moment behind it.
Frequently asked
Does unpak store screenshots of our screens?
No. unpak reads the screen locally and keeps structured text and interaction events: which app was focused, what the work was about, how long each act took. Screen images are not stored in the cloud.
Who can see the data unpak collects?
The workspace members you grant access, typically the leadership and operations people running the transformation. The capture exists to reconstruct how work happens; reports are built around workflows and patterns, and every figure traces back to the evidence behind it.
How is this different from employee monitoring software?
Monitoring tools score individuals: hours active, keystrokes, screenshots for managers. unpak answers a different question: how does the work itself happen? The output is reconstructed workflows, recurrence counts, and AI opportunities, not per-person productivity scorecards.
Which apps does unpak work with?
All of them. Because unpak observes work at the screen level rather than through per-app integrations, it follows work wherever it happens: email, spreadsheets, ERPs, browsers, internal tools. There is nothing to connect or configure.
How long before we see results?
The first reconstructed workflows appear within days of rollout. Recurrence counts and the cross-team picture firm up over the following weeks as the capture accumulates. The longer it runs, the sharper the picture.