Privacy policy

1. Information stored locally

Worklog stores time entries, settings, diagnostics, and provider credentials in your local Firefox profile. Entries include project, task, description, start and end times, duration, multiplier, status, device identifiers, and revision information. Analytics runs locally.

The extension does not send your data to the project developer, advertising services, or analytics services. If you contact support, the developer receives information you choose to include in your message. Please do not send passwords or authorization tokens.

2. MySQL storage

When you configure MySQL storage, your selected HTTPS API provider receives time entries and shared duration settings. Worklog sends the bearer token you enter only in the authorization header to the exact configured origin. It does not connect directly to MySQL or receive database credentials.

Connection testing and setup may contact a prepared provider when you request it. Normal synchronization and reconciliation use only the activated provider. The API provider’s retention and deletion policies apply to uploaded data.

3. Google Calendar access and use

Google Calendar sign-in is currently in testing for allowlisted test users. When you connect, Worklog sends sign-in, token refresh, and revocation requests directly to Google using its publisher-managed OAuth application. It requests these permissions:

• Account identity (openid): Google’s authenticated UserInfo endpoint supplies an account identifier to bind your account to its Worklog dataset. Worklog does not request profile or email scopes for account display.
• App-created calendars (calendar.app.created): create a dedicated Worklog Calendar and manage entries and settings in a selected app-created Calendar.
• Calendar list (calendar.calendarlist.readonly): discover calendars so you can select an existing Worklog Calendar.

The selected dedicated Calendar receives project, task, description, timestamps, multiplier, device ID, revision, shared duration settings, and dataset metadata. Canonical data is stored in private event properties, with additional records for large text; event titles and descriptions contain bounded readable summaries. Authorized clients of that Calendar can access these properties. Worklog does not encrypt them end to end.

Completed entries appear at their actual interval. Running and zero-length entries, deletion markers, and internal records use the archival day 1 January 1970 and are visible when that date is viewed in Google Calendar. Normal deletion writes a deletion marker rather than physically deleting the event. Worklog retains these markers and superseded payload parts without automatic cleanup. Editing or deleting events directly in Google Calendar may require explicit recovery in Worklog.

Google processes requests and stored data under its own privacy practices. Worklog does not sell Google data or use it for advertising. Its use of Google data is limited to the storage, synchronization, and user-requested actions described here.

4. Backups and transfers you request

Entries read from Google become local Worklog entries. A backup you request can export them to a JSON file. An explicit backend migration can send them to your selected MySQL provider, and an explicit Tempo upload can send completed work to Tempo.

Backups include entries and selected non-secret settings, excluding credentials, provider caches, account bindings, and recovery state. Diagnostic exports also exclude credentials and provider cache and binding state.

5. Optional Tempo upload

When you configure Tempo, its API token, author account ID, and task-to-issue mappings are stored only in local IndexedDB. Worklog sends the token only as Tempo’s bearer authorization header and sends worklog content only to Tempo. Running timers are not uploaded. Tempo’s retention and deletion policies apply to work already uploaded.

6. Optional ChatGPT usage limits

The experimental ChatGPT usage feature requests access to chatgpt.com only after you grant it. It reads the normal Firefox profile’s session and a fixed usage endpoint to show remaining usage and reset times. Its access token stays in memory for the request and is never persisted, synchronized, logged, exported, or sent elsewhere.

A sanitized usage snapshot and consent state stay in local IndexedDB. You can disable the feature by withdrawing consent. The Clear ChatGPT usage data control removes the snapshot and consent without signing you out of ChatGPT.

7. Credentials, retention, and your controls

MySQL, Google OAuth, and Tempo credentials remain local and are excluded from backups, diagnostics, URLs, and release artifacts. Each Firefox profile keeps its own Google refresh credentials, account and calendar bindings, synchronization cursor, cache, and recovery evidence. Google access tokens remain in background memory.

Disconnecting Google removes that profile’s Google credentials and stops Google synchronization, while preserving local entries and Calendar data. Revoking the Google grant is a separate action that invalidates the account’s tokens across clients in the publisher’s project; other devices may need to sign in again. Neither action deletes Calendar data. You can also manage access through your Google Account connections.

Worklog temporarily retains Firefox’s storage permission to remove two legacy OAuth credential keys left in synchronized storage by older versions. This removal-only cleanup does not read or write synchronized values or make network requests. It does not remove entries, unrelated settings, or supported MySQL state.

You can remove local records by removing the extension and its data or clearing its local data from your Firefox profile. Local removal does not delete backups or data already uploaded to Google, your API provider, or Tempo. Those services’ retention policies and account controls apply to remote data.

8. This website

These pages use no cookies, JavaScript, analytics, third-party fonts, or embedded tracking. Visiting the website does not connect your Google, Tempo, or ChatGPT account. The hosting provider may process standard request information, such as your IP address, browser information, and requested URL, to deliver and secure the website. External links are subject to the destination’s privacy practices.

9. Changes and contact

This policy will be updated when Worklog’s data practices change. The date above identifies the latest revision.

For questions, contact the developer through the Worklog issue tracker. Issues are public, so include only information you are comfortable sharing publicly.