Privacy Policy

Last updated: October 16, 2026 (the AI features are removed; feature-use counts are described)

This Privacy Policy describes how Project Commander ("we", "our", or "the App") collects, uses, and protects information when you use our Jira Cloud app.

1. Information We Access

Project Commander is a planning and analysis app for Jira Cloud, available both as a full-page app and a dashboard gadget. It provides capacity planning, delivery forecasting (including probabilistic / Monte Carlo simulation), sprint and scope management, a risk register and action tracking, portfolio and program rollups across multiple projects, and saved plan baselines. To provide this functionality, the App accesses the following Jira data:

Jira Project Data

• Sprint information: Sprint names, dates, states, and goals
• Issue data: Issue keys, summaries, story points, time estimates (original, remaining, and time spent), status, assignees, issue types, priority, due dates, start dates, resolution dates, epic links, and dependency links (blocks / blocked-by)
• Board configuration: Board names and associated projects
• User information: Display names of Jira users (primarily issue assignees) for workload tracking

Configuration and App-Managed Data

Project Commander also stores content that you create or configure inside the App:

• Gadget and board settings (board selection, the project last chosen, sprint capacity, display preferences)
• Velocity tracking data from completed sprints
• Sprint snapshots used for scope-creep detection
• Team capacity configuration (per-member hours/week, utilization, time-off entries, holidays)
• Risks (strategies, owners, mitigation actions, rationales) and action items (assignees, due dates, notes)
• Retrospective notes and carry-over items
• Governance policies, portfolio project lists, and alert dismissals
• Saved plan baselines — named snapshots of scope, team capacity, delivery forecast, target date, and headline project stats, kept per project and per program
• Per-user UI preferences
• A note of when each person first opened the App, kept against their Atlassian account ID (see Section 3)
• An AI provider API key, only if one was saved in an earlier version of the App (see Section 4)

2. How We Use Information

All data accessed by Project Commander is used solely to provide the App's functionality:

• Display sprint, issue, and team information in the App and dashboard gadget
• Calculate capacity utilization, workload distribution, and feasibility scores
• Track velocity metrics and scope changes from completed sprints
• Surface risks, alerts, and dependency conflicts across sprints and projects
• Roll up multiple projects into portfolio and program views
• Run what-if scenarios, auto-leveling, critical-chain analysis, and probabilistic (Monte Carlo) forecasts
• Save plan baselines and compare the current plan against them over time
• Generate retrospectives and action items from closed sprints
• Enable drag-and-drop issue management between sprints and inline editing of issue fields

3. Data Storage

All App data is stored using Atlassian Forge's built-in storage, isolated to your Jira instance and scoped to your Atlassian account. No App content is held in browser local storage as a system of record.

• Jira Data: Project Commander reads your Jira data through Atlassian's secure APIs and never sends it to us or to any server of ours. To make repeat visits fast, the App keeps a copy of the issues it has read in your own browser, on your own device, keyed to your Atlassian account so nobody else using that browser sees it through the App; each visit then re-reads only what changed in Jira since the last read. Refresh, beside the project picker, and Start over remove that copy; a copy not used for 7 days is removed the next time the App opens; clearing your browser's site data removes it at any time.
• Configuration and analytics: Gadget settings, team capacity configuration, velocity history, sprint snapshots (used for scope-creep detection), and per-user UI preferences are stored in Forge storage.
• App-managed content: Risks (strategies, owners, mitigation actions, rationales), action items, retrospective notes and sprint carry-over items, governance policies, portfolio project lists, saved plan baselines, and alert dismissals are stored in Forge storage and follow your Atlassian account across devices.
• Feature-use counts: The App counts how often some of its features are used — for example, the App being opened, a tab being opened, an issue being moved or edited, a sprint being created or completed — through Atlassian's own usage metrics for Forge apps. Each count is a bare tally that goes up by one: no user, site, project or issue is attached to it, and it stays inside Atlassian. To count how many different people use the App, the App keeps a note in Forge storage on your site, against each person's Atlassian account ID, of when they first opened it; that note never leaves your site and is deleted with the rest of the App's data on uninstall.
• AI API key from an earlier version: The App no longer takes an AI provider key. A key saved in an earlier version stays in Forge's encrypted secret storage (separate from regular Forge storage), is sent nowhere and used by no feature, and is deleted on uninstall.

Data Retention

App data persists until you uninstall the App or clear it through the App interface. Velocity history retains the last 10 completed sprints. Uninstalling the App removes all data stored in Forge storage, including App-managed content, configuration, snapshots, and anything an earlier version stored for its AI features, including an AI provider key. The copy of issues kept in your browser is not in Forge storage; clearing your browser's site data removes it.

The Web App at projectcommander.app/app

The web app is separate from the installed App and does not use Forge storage. Its demo mode does not collect, store, or transmit personal data: it runs on generated sample data in your browser and cannot connect to a Jira site. Its optional connect mode analyzes your own Jira through Atlassian's official sign-in (OAuth): you approve read-only access on Atlassian's consent screen for one chosen site, and the resulting access grant is held in your browser for the current tab session only, is sent with each request through our relay directly to your Jira, and is never stored or logged by us; you can revoke it at any time from your Atlassian account's Connected apps page. When you sign in to connect mode we record an irreversible connection code derived from your Atlassian account, together with sign-in dates, sign-in counts, and usage counts — never your name, email address, or site. The code cannot be turned back into your identity; we use it only to count distinct connections and, where necessary, to disable access that abuses the service. App content you create in connect mode (such as risks and settings) is held in your browser, and logging out deletes it. In connect mode the web app also keeps a copy of the issues it has read in your own browser, keyed to your Atlassian account, so repeat visits re-read only what changed; Log out, Refresh and Start over remove it, and a copy not used for 7 days is removed on the next visit. The web app asks no AI service anything.

4. AI Features and Third-Party Providers

Project Commander asks no AI model anything and sends no data to any AI provider. Every figure, and every sentence the Ask panel writes, is worked out by the App's own code inside Atlassian Forge, and the risk suggestions on the Risks tab come from fixed rules over the project's own figures. There is no AI section in Settings and no API key to add.

Earlier versions offered optional AI features — the What-If question box, AI Review in Auto-Level, Chain Analysis on the Projects tab, and the Ask panel's use of an AI — which sent a project-context prompt to the AI provider a customer chose (Anthropic, OpenAI or Google Gemini), only after that customer saved their own API key. Those features have been removed.

Data egress

The App declares no address outside Atlassian that it is permitted to reach, so the data egress list Jira shows while the App is being installed, and in Atlassian Administration under Connected apps, names none. Earlier versions declared the three AI providers' addresses there — api.anthropic.com, api.openai.com and generativelanguage.googleapis.com — and those are gone.

Reporting a wrong answer

If you report a wrong answer from the Ask panel, the app copies the question and the answer, with its figures, to your clipboard and tells you where to send it. Nothing is sent unless you paste it into an email and send it, and what you send reaches our support inbox like any other support email.

A key saved in an earlier version

A key saved in an earlier version stays in Forge's encrypted secret storage, is sent nowhere and used by no feature, and is deleted when the App is uninstalled (see Section 3).

5. Data Sharing

Project Commander does not share, sell, or transfer your data to third parties.

6. Data Security

We implement security measures to protect your information:

• The Jira Cloud app runs entirely within Atlassian's secure Forge platform
• All API communications use HTTPS encryption
• An AI provider key saved in an earlier version is held in Forge's encrypted secret storage
• No Jira data is transmitted to our servers
• Access is controlled by your Jira permissions

7. Your Rights

You have the following rights regarding your data:

• Access: View all configuration, velocity, and App-managed content (risks, action items, retros, etc.) through the App interface
• Correction: Update your settings and App-managed content at any time through the App interface
• Deletion: Clear velocity data and App-managed content through the App where applicable. Uninstalling the Forge app removes all App data stored in Forge storage — configuration, velocity, snapshots, team capacity, risks, action items, retros, governance, portfolio data, plan baselines, alert dismissals, and anything an earlier version stored for its AI features, including an AI provider key.
• Portability: Your Jira data remains in Jira and is accessible through standard Jira exports. For App-managed content (risks, action items, retros), contact support@projectcommander.app if you need help exporting it.

8. Atlassian Marketplace

Project Commander is distributed through the Atlassian Marketplace. Atlassian may collect information about your use of the Marketplace and Apps. Please refer to Atlassian's Privacy Policy for details.

9. Children's Privacy

Project Commander is a business productivity tool and is not intended for use by children under 16. We do not knowingly collect information from children.

10. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify users of significant changes through the Atlassian Marketplace listing or the App interface. Continued use of the App after changes constitutes acceptance of the updated policy.

11. Contact Us