1. What data is processed
- Active tab URL and title metadata while the extension is enabled.
- Tab focus timestamps and active session durations.
- Minimal extension state required for local event batching and retries.
2. Where data is stored
Event data is buffered in browser extension local storage and delivered to your local WorqLog macOS app. Long-term records are maintained by the local app database.
3. Permissions used
- Tab/activity permissions are used to identify active work context.
- Storage permissions are used for local buffering and reliability.
- Network access is limited to local bridge communication used by WorqLog.
4. Data sharing
The extension is designed for local-first workflows. No background upload to a WorqLog cloud endpoint is required for core functionality.
5. User controls
- You can disable or remove the extension from browser settings at any time.
- You can clear extension local storage from browser extension settings.
- You can disable local bridge communication in WorqLog app preferences.