WorqLog
Menu

Navigation

Access options
← Privacy center

Apple platform policy

WorqLog for macOS Privacy Policy

This policy covers desktop activity capture, local persistence, operating system permissions, and the user controls available in the macOS application.

Last updated: 3 April 2026

Storage model

Local-first database on your Mac with optional private CloudKit sync

Primary permissions

Calendar · Optional microphone/system audio · Optional speech recognition fallback

Default transfer mode

No WorqLog cloud upload for core tracking; optional user-enabled transfers only

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.
  • Browser tab metadata received from local WorqLog browser extensions when that integration is installed.
  • Meeting metadata when calendar integration is enabled.
  • Crash and performance diagnostics used for local reliability workflows.
  • 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.

If you enable iCloud Sync, cloud-eligible records are synced through your private CloudKit database associated with your Apple Account. If iCloud Sync is off, those records remain local only.

3. Permissions used

  • Calendar permission for meeting-aware analytics.
  • Microphone and system audio capture permissions only if meeting recording/transcription is enabled.
  • Speech Recognition permission only when Apple speech fallback is needed for meeting transcription.
  • Accessibility is not required for the sandboxed Mac App Store flow. Some non-App-Store builds may use Accessibility for richer app/window context.

4. Sharing and transfers

By default, data remains local. Local editor and browser integrations communicate with the app over machine-local bridges only.

External transfers occur only when you explicitly enable integrations or export features that require sending data to third-party services.

Examples of optional transfers include private CloudKit sync that you enable yourself and AI requests sent to OpenAI, Anthropic, or Gemini when you select one of those providers and supply your own credentials.

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 iCloud Sync and return to local-only storage at any time.
  • You can disable optional integrations and AI-related features at any time.