Information the product handles
Timerflow stores account and organization details needed to authenticate users and provide workspace access. It also processes project assignments, tracked time intervals, activity samples, idle decisions, and device information submitted by the desktop application.
When enabled by organization policy, activity context can include application names, website domains or URLs, and screenshots. These signals support time and activity reporting; they are not presented as a substitute for organizational judgment.
How information is used
- Authenticate members and connect them to the correct organization.
- Synchronize tracked sessions from registered desktop devices.
- Generate dashboards and project, activity, and idle-time reports.
- Process uploaded screenshots and create display thumbnails.
- Operate, diagnose, and improve the reliability of the service.
Organization controls
Organization administrators can manage membership, roles, and tracking settings. Current policy controls include screenshot cadence and idle-prompt behavior, with settings exposed centrally so tracking expectations can be communicated consistently.
Role-based permissions restrict access to protected product functions. The specific people authorized to view time, activity, or screenshot information depend on the organization's membership and role configuration.
Idle decisions and transparency
When an idle prompt appears, a person can keep the time, discard it, stop tracking, or move it to another project. Timerflow records the selected outcome so reports can distinguish tracked work from an unresolved gap.
Storage and retention
Product data is stored in the database and object-storage services configured for the deployment. Retention periods, deletion procedures, regional hosting, and backup policies are deployment-specific and should be agreed during an organizational rollout.
Questions and requests
For a demo environment or organizational deployment, privacy questions and requests should be directed to the Timerflow contact responsible for that deployment at hello@timerflow.space.