Privacy Policy

Last updated: May 31, 2026

1. Introduction

This Privacy Policy explains how Velocity Chart for Jira ("the App"), developed by Janek Behrens ("we", "us", "our"), handles data when installed on your Atlassian Jira Cloud instance. The App is a read-only reporting tool: it reads agile data to draw a sprint velocity chart and never modifies your issues.

2. Data We Access

The App reads the following Jira data, on demand, solely to compute the velocity chart:

• Boards & board configuration: Scrum board names, project, the board's estimation field and column-to-status mapping — used to list boards and provide sensible defaults.
• Sprints: Closed sprint names, start and complete dates — used to define the chart's time axis.
• Issue data of sprint members: Issue key, status, issue type, creation date, and the chosen estimation field value (Story Points or a numeric custom field) — used to compute committed and completed work per sprint.
• Sprint-field change history: The Jira changelog of the Sprint field for those issues — used to reconstruct which issues were in the sprint at its start ("committed").

The App does not read or use assignee, reporter, or any other user/personal fields. Velocity is reported only at the team/board level — never per individual.

3. Data We Store

The App stores only the following, using Atlassian Forge Storage (KVS), which is hosted and managed by Atlassian within your cloud instance:

• Computed result cache: The aggregated velocity numbers (committed, completed, averages) per board and configuration. Cached for 5 minutes to reduce API calls, then recomputed on demand.
• Discovery cache: A short-lived cache of available estimation fields and the board's statuses, to render the configuration form. Refreshed automatically.

We do not store issue titles, descriptions, comments, attachments, user names, emails, account IDs, or any free-text content. Stored data consists of numeric aggregates, issue keys, sprint and board identifiers, and status names only.

Gadget configuration (selected board(s), number of sprints, estimation mode, Definition of Done, label style) is stored by Jira as standard dashboard-gadget configuration.

4. Data We Do NOT Collect

• We do not run any servers. There is no developer-operated backend or database.
• We do not collect personally identifiable information (PII). The App does not read assignee or user fields.
• We do not use cookies, tracking pixels, analytics platforms, or advertising networks.
• We do not send any data to external services. The App makes no network calls outside the Atlassian platform.

5. Data Processing Location

All processing occurs within the Atlassian Forge runtime environment under the Runs on Atlassian program. No data is transmitted to servers operated by us or any third party outside the Atlassian platform.

6. Data Retention

• The result and discovery caches live in Forge Storage and expire automatically (minutes/hours). Uninstalling the App removes all App-stored data.
• Gadget configuration is removed when the gadget is removed or the App is uninstalled.

7. GDPR Compliance

The App does not collect or store personal data. It does not read assignee or user information. Stored data is limited to numeric aggregates, issue keys, and identifiers. GDPR data-subject requests relating to data held by Jira itself should be directed to Atlassian. For App-specific concerns, contact us below. Uninstalling the App removes all App-related data from Forge Storage.

8. Security

• Runs in a sandboxed Forge environment with no egress to external networks outside the Atlassian platform.
• Uses minimal, read-only Jira API scopes (boards, sprints, issues, fields, changelog) plus app storage.
• Stores no credentials, tokens, or secrets — there are none.

See our Security Policy for full details.

9. Children's Privacy

The App is a business productivity tool and is not directed at children under 16. We do not knowingly collect data from children.

10. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be reflected in the "Last updated" date above. Continued use of the App after changes constitutes acceptance of the updated policy.