Postgame 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 Postgame app for Jira Cloud (the "App") processes, where it is kept, and your rights. It covers only the App. It does not cover 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 retros. We do not receive, store or have access to your cards, votes, action items or Jira data.
- Retro content is stored in your own Atlassian site's app storage and stays there until someone on your site deletes the retro or an admin uninstalls the App.
2. What the App processes
| Data | Why | Where it lives |
|---|---|---|
| Retro settings: title, columns, phase, timer, linked sprint name and id, sprint numbers (issue counts by status category and type) | To run the retro and show history and trends | Forge app storage on your site |
| Cards: the text people write, the column and group | The retro itself | Forge app storage on your site |
| Card authorship: in anonymous retros (the default) only a one-way hash of the author's Atlassian account id combined with a random per-retro value; in named retros, the author's account id | Lets people edit their own cards; shows names only when the retro was set up as named | Forge app storage on your site |
| Votes and the 1 to 5 check-in rating, stored against the same one-way hash | Vote limits and the anonymous team average | Forge app storage on your site |
| Action items: text, owner (account id), due date, linked Jira issue key and last known status, who created it (account id) | Follow-up across retros | Forge app storage on your site |
| Account ids of the retro's creator and co-facilitators | Facilitation permissions | Forge app storage on your site |
| Display names of people (looked up from Jira when shown) | Showing owners and, in named retros, authors | Not stored by the App |
| Jira issues the App creates for action items | At the user's request, created as that user | Your Jira project (normal Jira data) |
| Review-prompt and onboarding preferences per account id | Not asking twice | Forge app storage on your site |
The App does not collect email addresses, IP addresses, passwords, API tokens, payment information or analytics. It sets no cookies and loads no third-party scripts. Live updates between people in the same retro use Atlassian's Forge Realtime service and carry only a "something changed" signal, never card text or names.
3. Anonymity
In anonymous retros the App never stores who wrote a card or how someone voted. It stores a one-way hash (SHA-256) of the person's account id combined with a random value created for that retro, and never sends that hash or the random value to anyone's browser. Facilitators, Jira administrators and Great Work LLC cannot see who wrote a card through the App. As with any anonymous tool used by a small team, people may still recognize a writing style; we say so in the App's help.
4. 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 for Forge apps. Atlassian is the hosting provider and acts as a subprocessor under Atlassian's terms. Great Work LLC uses no other subprocessors for the App.
5. Who can access it
- People on your site: anyone who can browse the Jira project can open its retros, because retros belong to the project. The App checks Jira permissions on every request.
- Great Work LLC: no access to App storage or your Jira data. If you open a support request, we only see what you choose to send us.
- Atlassian: as the platform operator, under Atlassian's privacy policy.
6. Retention and deletion
Retros and action items are kept until someone deletes them in the App (the person who started a retro or a project admin can delete it, which removes its cards, groups, votes and action items). Uninstalling the App removes its app storage according to Atlassian's Forge data deletion process. Jira issues created from action items are your Jira data and are not deleted.
7. Support requests
If you contact support through our help desk or by email, we process the information you send (name, email, message, attachments) only to answer you. Support data is kept for up to 24 months and then deleted. You may ask us to delete it sooner.
8. Your rights
Depending on where you live (for example the 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 administrators can delete retros or uninstall the App; for support data, email hello@greatwork.company. We respond within 30 days.
For App data in Forge storage, your organization (the Atlassian customer) is the controller and Atlassian processes it on your behalf; Great Work LLC has no access to it. For support data, Great Work LLC is the controller.
9. Security
The App uses only Atlassian-hosted compute and storage, requests the minimum Jira permissions it needs, acts as the signed-in user for every Jira call, and keeps no secrets of its own. See the Privacy & Security tab on the Marketplace listing for details. Report vulnerabilities to hello@greatwork.company.
10. Children
The App is a business tool and is not directed to children under 16.
11. Changes
We will post changes on this page and update the effective date. Material changes will also be announced in the App's release notes on the Marketplace.
12. Contact
Great Work LLC, 651 N Broad St Suite 206, Middletown, DE 19709, USA. hello@greatwork.company