1. What data is processed
- Application usage events such as active app/window titles and session durations.
- Project/workspace context inferred from file paths and app metadata.
- Meeting metadata when calendar integration is enabled.
- Optional AI-generated summaries derived from local activity records.
- Optional Git metadata used for correlating commits with work sessions.
2. Where data is stored
WorqLog stores data locally on your Mac in a local database under your user profile. Data is not uploaded to a WorqLog cloud backend as part of core tracking.
3. Permissions used
- Accessibility permission for active window and app context.
- Calendar permission for meeting-aware analytics.
- Microphone permission only if meeting recording/transcription is enabled.
4. Sharing and transfers
By default, data remains local. External transfers occur only when you explicitly enable integrations or export features that require sending data to third-party services.
5. User controls
- You can revoke macOS permissions at any time in System Settings.
- You can clear local data from the app or by removing app storage files.
- You can disable optional integrations and AI-related features at any time.