Privacy Policy
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:
| Data | Why |
|---|---|
| Work items: key, summary, status, assignee, estimate, sprint, and change history | To calculate committed work, remaining work, and what was completed in each sprint |
| Boards, sprints, sprint dates and goals | To know which sprint is being planned and how long it runs |
| Users assignable to the project: display name, Atlassian account ID, avatar | To build the team roster in setup and show who holds what |
| Custom field definitions | To find which field holds story points on your site |
| Project workflow statuses | To 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:
| Stored | Contents |
|---|---|
| Setup choices | Selected board ID, story-point field ID, date setup was completed |
| Team roster | For each team member: Atlassian account ID, display name, hours per day, focus factor, allocation percentage, and any time off entered |
| Holidays and settings | Working days, holiday dates, planning mode, thresholds |
| Sprint metadata | Goal, theme, release and notes entered for a sprint |
| Sprint baselines | A snapshot at sprint start of each work item's key, assignee ID and estimate. No summaries or descriptions are stored. |
| Sprint history | For 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 log | The last 100 configuration actions with timestamps. The acting user is not recorded. |
4. What the App does not do
- It does not send any data to servers outside Atlassian. The App has no backend of its own.
- It does not use analytics, tracking, cookies, or advertising.
- It does not use any artificial-intelligence or machine-learning service. Every number it shows is arithmetic on the data above.
- It does not store Jira credentials, tokens, or passwords.
- It does not sell, share, or disclose your data to anyone.
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
- While installed: configuration is kept for as long as the App is installed on your site. The audit log keeps only the most recent 100 entries.
- After uninstall: Atlassian soft-deletes the App's storage immediately and permanently deletes it 28 days after uninstallation. During the first 21 days a site administrator can ask, via the developer, for the data to be restored to a fresh installation.
- Trial or subscription lapse: data is retained while the App remains installed, even if it is unlicensed. Nothing is deleted on licence expiry.
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