Forgentia · WorkTracker

Privacy Policy

Last updated: 1 July 2026 · Forgentia

WorkTracker is local-first. It infers Jira worklog entries from your local editing activity and current git branch. The only data that leaves your machine is data you explicitly opt into by configuring a backend and triggering an action. There is no telemetry or analytics of any kind.

What stays on your machine

The following are stored locally and are never transmitted by WorkTracker:

• Activity events, draft worklogs, ticket extractions, and non-secret settings — in a single SQLite database shared across your JetBrains IDEs at ~/.worktracker/worktracker.db.
• Secrets — your Jira API token, Jira OAuth tokens, optional OAuth client secret, Anthropic API key, and WorkTracker license key — in the IDE's PasswordSafe (the OS keychain/credential store), never in the database or the settings file.

What is sent, and only when you opt in

1. AI generation (optional)

Triggered by Generate Suggestions, Generate standup, or AI title, and only when you have configured an AI backend. WorkTracker sends the backend:

• a git diff of your recent changes (capped in size),
• the related commit messages,
• the branch name,
• the changed-file paths (relative to the repository root),
• the ticket key and summary, and
• for standup/title generation, your draft worklog notes for the day.

The backend is one of:

• Anthropic Claude (cloud) — HTTPS to https://api.anthropic.com/v1/messages when an Anthropic API key is configured. Governed by Anthropic's Privacy Policy.
• Ollama (local by default) — HTTP to the Ollama server URL you configure (default http://localhost:11434). With the default loopback URL, nothing leaves your machine. If you configure a remote host, the same content is sent there over the connection you specify.

If no backend is configured, nothing is sent — a deterministic offline note is generated locally instead.

2. Jira Cloud

When you press Submit, the worklog (time spent and note text) is sent to your Jira Cloud site via the Atlassian REST API (api.atlassian.com). Other actions you explicitly invoke — creating a ticket, commenting, changing assignee/reporter, and adding a development-panel branch link (which includes the branch name and repository remote URL) — likewise send their content to your Jira site. No Jira data is sent anywhere else.

Authentication uses either a Jira API token or OAuth 2.0 (3LO) with PKCE; tokens are stored in PasswordSafe.

Data retention

Local activity data is pruned according to the retention window you set in Settings. You can delete all local data by removing ~/.worktracker/worktracker.db. Secrets can be cleared from Settings.

Contact

Questions about this policy: andrew@forgentia.com