Berth 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 Berth 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.
- Your CI pipelines send deployment reports to an endpoint that belongs to your Jira site and the App. The App never calls out to your CI or anywhere else.
- If your Jira admins leave the setting on, the App passes each deployment on to Jira's own Deployments feature in the same site.
- Great Work LLC cannot see your environments, bookings, deployments or who used the App.
2. What the App processes
| Data | Why | Where it lives |
|---|---|---|
| Environments: name, key, tier, group, URL, notes, owner account id, booking limits, status and status note with who set it | The environment board | Forge app storage until removed or uninstall |
| Bookings: environment, start and end, account id of the booker, purpose text, optional work item key, who ended it early | Booking and clash checks | Forge app storage; deleted 120 days after the booking ends |
| Deployments sent by your CI: environment key, version, state, pipeline name, links to the CI run and pipeline, commit id, description, work item keys | Deployment history and what is on each environment | Forge app storage; per-environment history 180 days, site-wide feed 90 days |
| Work items on each environment: work item key, version, time | "What is on it" and the work item panel | Forge app storage until replaced, rolled back or uninstall |
| CI tokens: name, environments it may report to, a SHA-256 hash of the token, a masked form, who created it, last use | Authenticating your pipelines | Forge app storage until revoked or uninstall. The token itself is shown once and never stored |
| Settings: time zone, first day of the week, booking group id and name, booking horizon, the Jira Deployments setting | To apply your admins' choices | Forge app storage until uninstall |
| Space keys known to exist | To tell real work item keys from look-alikes in commit messages | Forge app storage; deleted after 1 day |
| Activity log: time, account id, what happened | So people can see what happened | Forge app storage; deleted after 180 days |
| Work item summaries and status, group membership, display names | Shown on screens and in booking messages | In memory while a screen loads or a check runs; not stored |
The App does not read work item descriptions, comments or attachments, and it does not collect email addresses, IP addresses, passwords, payment information or analytics. It sets no cookies and loads no third-party scripts. Commit messages your CI sends are scanned for work item keys and then discarded; only the keys are kept.
3. Where data is stored
All App data is stored by Atlassian, in your Jira site or in Forge app storage for your 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.
4. Who can see what
- Anyone who can use Jira on the site can see the environment board, bookings and deployment history. Work item summaries are read as the person viewing, so people only see work items they are allowed to see.
- Only Jira admins add environments, create tokens and change settings; environment owners and Jira admins change an environment's status. Your admins can limit booking to a Jira group.
- 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
Bookings, deployment history, the space cache and the activity log expire automatically (see section 2). Revoking a token deletes its hash. Uninstalling the App removes its Forge storage according to Atlassian's Forge data deletion process; deployments passed on to Jira's own Deployments feature stay in Jira under Atlassian's terms.
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 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. CI tokens are random 256-bit values stored only as hashes and compared in constant time; each can be limited to chosen environments and revoked at any time. Admin actions re-check permissions on every call. 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