When the agreed window closes, capture stops and the cohort's machines no longer send activity. Capture began earlier in the engagement, when you clicked Begin capture, so wind-down is removing the software and confirming where data stands.
For participants
You can remove flowscope from your own machine without an administrator. Uninstalling the desktop app, and removing the browser extension (or letting your organization remove it), ends all capture and transmission permanently. Until then you keep the same controls as throughout: the visible indicator and, where your company keeps the control enabled, the ability to pause. See Your privacy and controls.
Admin checklist
- Confirm capture has begun. It has, if you clicked Begin capture: no new people or devices, and flowscope no longer holds your recovery key.
- Revoke devices you want cut off immediately. Uninstalling ends capture on its own, but revoking stops a device's credential at once, useful when a machine will not be reachable to uninstall promptly.
- Keep your recovery key as long as you may need to map pseudonyms. While you hold it, the browser-only mapping tool connects pseudonyms back to people for a legitimate reason. Destroying your copy makes the mapping unrecoverable by anyone, including flowscope.
- Coordinate uninstall with IT to pull the software through the channel that deployed it, rather than relying on each participant.
Where the data stands
Captured activity and the derived workflow model follow your engagement's retention terms (Discovery trust addendum, governed by your agreement). You can request deletion of an individual participant's contribution at any time; flowscope then removes their raw records, the derived structures attributable to them, and the backup entries within the next rotation cycle. Aggregate models that no longer identify anyone are unaffected unless they are themselves the deletion target.
Wind-down or deletion requests: support@flowscope.com.