Steerwell for Jira: Privacy Policy
Effective date: October 1, 2026 Publisher: Great Work LLC, 651 N Broad St Suite 206, Middletown, DE 19709, USA Contact: hello@greatwork.company
This policy explains what information the Steerwell app for Jira Cloud (the "App") processes, where it is kept, and your rights. It covers only the App, not Atlassian's products, which are governed by Atlassian's own privacy policy.
1. Summary
- The App runs entirely on Atlassian's Forge platform ("Runs on Atlassian"). It has no servers of its own and sends no data to Great Work or to any third party.
- Great Work LLC cannot see your Jira work items, increments, objectives, risks or votes.
- The App's own storage, hosted by Atlassian for your site, holds increment settings and the planning content people type into the App (objectives, risks, votes). It never stores copies of work items.
2. What the App processes
| Data | Why | Where it lives |
|---|---|---|
| Increments: name, dates, iterations (names, dates, optional release name), feature JQL, link types and their order, teams (name, color, board id and name, project keys, sprint id per iteration, capacity or availability), who can edit, the owner's Atlassian account id, created and updated times | To build the program board | Forge app storage for your site, until the increment is deleted |
| Feature plans: the iteration a feature was dragged to | To remember a plan that has no release in Jira | Forge app storage, deleted with the increment |
| PI objectives: team, text, committed or not, business values, work item keys, the author's account id | To show objectives and predictability | Forge app storage, deleted with the increment |
| Risks: title, details, team, owner (free text you type), ROAM status, work item keys, the author's account id | To show the ROAM board | Forge app storage, deleted with the increment |
| Confidence votes: scope (program or team), value 1-5, the voter's account id, time | One vote per person per scope, and the summary | Forge app storage, deleted with the increment or when a new vote starts |
| Velocity cache: per board, the done totals of the last three closed sprints | So boards open quickly; recomputed every 6 hours | Forge app storage |
| Admin settings: who can create increments | Site policy | Forge app storage |
| A development-install marker (one true/false value) | So development installs are treated as licensed | Forge app storage, only on development or staging installs |
| Work items returned by Jira: key, summary, status, work type, project, parent, sprints, fix versions, story points and links | To draw the board and compute flags | Read in memory during one request, as the person looking at the board; never stored |
| Moves and new sprints you confirm | To change the sprint or fix version you asked for, or create the sprints you asked for | Written to Jira as you; the App keeps no copy |
PNG and CSV files are created in your browser and saved to your device; they are never uploaded. The App does not collect email addresses, passwords, API tokens, payment information, IP addresses or analytics. It sets no cookies and loads no third-party scripts.
3. Where data is stored
All App data is stored by Atlassian in Forge storage associated with your Jira site, subject to Atlassian's data residency settings. Atlassian is the hosting provider and acts as a subprocessor under Atlassian's terms. Great Work LLC uses no other subprocessors for the App.
4. Who can access it
- People on your site who can open the App: see every increment's settings, objectives, risks and vote totals (not who voted what). The board itself reads Jira as the person viewing it, so it only shows work items that person can browse.
- Editors (the increment's owner and Jira admins, or everyone if the owner allows it): change settings, move work and set business value. Jira still checks each move against the editor's own permissions.
- Jira admins: can see and delete every increment and set who may create increments.
- Great Work LLC: no access. If you open a support request, we see only what you send us.
- Atlassian: as the platform operator, under Atlassian's privacy policy.
5. Retention and deletion
Increments and everything under them remain until their owner or a Jira admin deletes them. Uninstalling removes Forge app storage according to Atlassian's Forge data deletion process.
6. Support requests
If you contact support through our help desk or by email, we process what you send (name, email, message, attachments) only to answer you, keep it up to 24 months, and delete it sooner on request.
7. Your rights
Depending on where you live (for example EU/UK GDPR or US state privacy laws), you may have the right to access, correct, delete or port personal data and to object to processing. For data in your Jira site, your organization (the Atlassian customer) is the controller and Atlassian processes it on your behalf; your admins can delete increments or uninstall the App. For support data, Great Work LLC is the controller: email hello@greatwork.company. We respond within 30 days.
8. Security
The App uses only Atlassian-hosted compute and storage, acts as the person for every Jira request (so Jira permissions always apply), checks every JQL query with Jira's strict parser before running it, re-reads a work item before and after every move, writes to Jira only when a person confirms a previewed move or asks for sprints to be created, and keeps no secrets of its own. Report vulnerabilities to hello@greatwork.company.
9. Children
The App is a business tool and is not directed to children under 16.
10. Changes
We will post changes here and update the effective date. Material changes will also be announced in the App's Marketplace release notes.
11. Contact
Great Work LLC, 651 N Broad St Suite 206, Middletown, DE 19709, USA. hello@greatwork.company