Twinwell 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 Twinwell 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.
- The App keeps pairs of work items in two projects of your own Jira site in step. Field values, comments and attachments go from Jira to Jira; the App does not keep copies of them.
- The App stores sync settings, which work items are linked, fingerprints (one-way hashes) of field values, retry state and a log in its storage on Atlassian's platform for your site.
- Great Work LLC cannot see your work items, your sync pairs or who used the App.
2. What the App processes
| Data | Why | Where it lives |
|---|---|---|
| The fields of synced work items you mapped (for example summary, description, priority, labels, custom fields), their status, comments and attachments | To copy changes between the two work items | Read from Jira and written to Jira while a sync runs; held in memory only, never stored by the App |
| Sync pairs: names, project ids and keys, field, status and work type mappings, JQL and status rules, comment and attachment settings, the account id of the admin who last saved them | To know what to sync and how | Forge app storage for your site until deleted or uninstall |
| Links between twins: work item ids and keys, per-field one-way hashes and sync times, comment and attachment id maps, state, the last error message and warnings, retry counters | To sync only what changed, never echo a change back, retry failures and show health | Forge app storage until the twins are unlinked or the App is uninstalled |
An issue property issue-sync on each synced work item: link id, pair id and name, which side, the twin's key, the sync state | So JQL can find synced work (issueSyncTwin, issueSyncState, issueSyncPair) and so a twin is never given its own twin | In your Jira site, on the work item, until unlinked or deleted |
A comment property issue-sync on each comment the App writes: the id of the source comment | So a synced comment is never synced back | In your Jira site, on the comment |
| Sync log: time, kind, work item keys, a short description (for example "Status Resolved -> SUP-3", or Jira's error text) | So admins can see what synced and why something failed | Forge app storage, the latest 400 entries |
| Your account id and Jira permissions | To check that you may see a work item, create work in the target project, or change sync pairs | In memory only |
The log and error messages can contain field names, status names and Jira's error text (for example "Option value 'Platinum' is not valid"); they do not contain field values or comment text. 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.
3. Where data is stored
All App data is stored by Atlassian in Forge app storage for your Jira site, encrypted at rest by the platform and 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
- Synced work items and comments: like any work item, whoever Jira lets see each project. Comments the App writes into a service project are internal notes by default, and an internal note is never made public by the App.
- The issue panel shows a work item's twin only to people who can see the twin.
- Sync pairs, the Health page and the log: Jira admins.
- 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
Unlinking twins deletes their link record and removes the issue property; both work items and everything already synced stay. Deleting a sync pair is possible once it has no linked work items. The log keeps the latest 400 entries. Uninstalling the App removes its Forge storage according to Atlassian's Forge data deletion process. Work items, comments and attachments the App created are ordinary Jira data and stay in your site until you delete them.
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 unlink work items, delete sync pairs 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. Before anything is queued for a person (create a twin, sync now, unlink), the App checks with Jira, as that person, that they can see the work item and hold the needed permission in the target project. Background syncs run as the App and only touch work items that a Jira admin's sync pair covers. The App 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