Sprint Capacity Planning & Forecast

Privacy Policy

Effective 15 September 2026 · Applies to Sprint Capacity Planning & Forecast for Jira Cloud (the "App")

The short version. The App runs entirely inside Atlassian's infrastructure. It reads your Jira work items with your own permissions, stores only its own planning configuration in Atlassian-hosted storage, and sends nothing to anyone else. There are no third-party servers, no analytics, no advertising, and no AI services.

1. Who is responsible

The App is developed and published by Akash Ram, an individual developer, who is the controller of the data described in this policy. Contact: support@falconsaas.online.

Atlassian Pty Ltd hosts the App on its Forge platform and processes data on the developer's behalf as a sub-processor. Atlassian's own handling of your Jira data is governed by the Atlassian Privacy Policy.

2. What the App reads from Jira

Every call the App makes to Jira is made as the signed-in user, with that user's own permissions. The App cannot see anything the person using it could not already see in Jira.

To plan and monitor a sprint, the App reads, for the project and board you select:

DataWhy
Work items: key, summary, status, assignee, estimate, sprint, and change historyTo calculate committed work, remaining work, and what was completed in each sprint
Boards, sprints, sprint dates and goalsTo know which sprint is being planned and how long it runs
Users assignable to the project: display name, Atlassian account ID, avatarTo build the team roster in setup and show who holds what
Custom field definitionsTo find which field holds story points on your site
Project workflow statusesTo map board columns to real transitions

This data is read when a page is opened, used to draw that page, and not retained by the App except as described in section 3.

3. What the App stores

The App stores its configuration in Atlassian Forge hosted storage, scoped to your Jira site and project. Nothing is stored anywhere else. Per project, this is:

StoredContents
Setup choicesSelected board ID, story-point field ID, date setup was completed
Team rosterFor each team member: Atlassian account ID, display name, hours per day, focus factor, allocation percentage, and any time off entered
Holidays and settingsWorking days, holiday dates, planning mode, thresholds
Sprint metadataGoal, theme, release and notes entered for a sprint
Sprint baselinesA snapshot at sprint start of each work item's key, assignee ID and estimate. No summaries or descriptions are stored.
Sprint historyFor each completed sprint: totals committed and completed, scope added and removed, and per team member, the work committed, completed, and their capacity for that sprint
Audit logThe last 100 configuration actions with timestamps. The acting user is not recorded.
About per-person history. The App's forecast works by learning how much each person has completed in past sprints, so completed sprints are stored per team member. This is planning data about work assignment, not an evaluation of anyone — but it is information about identifiable people, and administrators should treat it accordingly. It is visible only to users who can open the App in that project, and it is deleted with everything else when the App is uninstalled.

4. What the App does not do

The only external requests the App's page makes are to load team members' profile pictures — Atlassian's own avatar images, served from Atlassian domains and, for some accounts, Gravatar. No data is sent with these requests beyond the image address itself.

5. Where data lives

All storage is Atlassian-hosted and follows the data residency of your Jira site. If your site is pinned to a region, the App's data stays in that region. All compute and storage is Atlassian-hosted; the App has no servers of its own and sends no data to third parties.

6. How long data is kept

7. Your rights and how to delete data

A Jira site administrator can delete all of the App's data for a site by uninstalling it from Apps › Manage apps. Individual team members can be removed from the roster in the App's setup, which removes their availability settings; their entries in stored sprint history can be cleared by an administrator on request.

If you are in a jurisdiction that grants you rights to access, correct, or erase personal data, contact support@falconsaas.online. Because the developer has no independent copy of your data, most requests will be fulfilled by guiding your site administrator through the steps above.

8. Security

The App runs in Atlassian's Forge sandbox, which enforces the permission scopes declared in the App's manifest and isolates the App from other apps and from the open internet. It acts only with the permissions of the signed-in user. The developer does not have access to your Jira site or to the App's stored data.

9. Children

The App is a business tool for Jira Cloud and is not directed at children.

10. Changes to this policy

If the App's data handling changes — for example, if a future version adds an external service — this policy will be updated before that version is released, and the change will appear in the App's release notes on the Atlassian Marketplace.

11. Contact

Akash Ram · support@falconsaas.online