Binwell 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 Binwell 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.
- To make deleted work items recoverable, it keeps a compressed copy of each work item in the projects your Jira admins choose, in Forge storage on your own site.
- Great Work LLC cannot see your work items, the copies or the activity log.
2. What the App processes
| Data | Why | Where it lives |
|---|---|---|
| A copy of each protected work item: key, project, work type, summary, description, environment, status, resolution, priority, labels, components, versions, due date, estimates, security level name, custom field values, parent and sub-task ids, link targets (id, key, summary), attachment details (file name, size, type, uploader, date; never the file contents), watcher account ids, vote count | To show and restore the work item after it is deleted | Forge SQL on your site, compressed. Replaced each time the work item changes; kept until the retention period after deletion (default 90 days, 7 to 3,650) or until a Jira admin narrows the protected projects |
| Comments (body, author account id and display name, dates, visibility) and work logs (author, start, time spent, description) on protected work items, up to 1,000 each | To restore them with their original authors and dates | Inside the copy above |
| People on the work item: account ids and display names of assignee, reporter, creator, comment and work log authors, user custom fields | To restore those fields and credit authors | Inside the copy above |
| Deletion and restore records: time, account id of the person who deleted, restored or removed a copy, work item id and key, project key, a short detail | Activity log | Forge SQL; kept two years |
| Restore marker on restored work items: old key and id, deletion and restore times, account ids of the deleter, restorer and original creator, original created date | So restored work items can be found by their old key | A Jira issue property (binwell.restored) on the restored work item, visible to people who can see it |
| Admin settings: protected project ids, retention, restorer group id and name, restore options; progress of Copy existing work items; short-lived restore batches (2 days) | To apply your admins' choices and run restores | Forge app storage |
| The signed-in person's permissions and group membership | To decide who may open a bin and restore | Not stored |
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. It never copies attachment files.
3. Where data is stored
All App data is stored by Atlassian in Forge storage (Forge SQL and Forge app storage) and in Jira issue properties on 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
- A project's Recycle bin: Jira admins, that project's admins (unless a Jira admin turns this off) and members of the one restorer group a Jira admin may choose, in projects they can browse. Deleted work items that had a security level, and deletions Binwell saw without a copy, are shown only to Jira admins and project admins.
- The bin across all projects, settings and the full activity log: Jira admins.
- Restores run as the restoring person for the work item itself, so Jira's Create work items permission applies; comments, work logs, watchers and the marker are added by the App.
- 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
Copies of deleted work items are removed once older than the retention your Jira admin sets. Copies of work items in projects that are no longer protected are removed when the admin saves that change. A Jira admin or project admin can remove any copy from the bin at any time. Activity entries are removed after two years. Uninstalling the App removes its Forge storage according to Atlassian's Forge data deletion process; restore markers stay on restored work items until removed. If someone asks you to erase their personal data, a Jira admin can remove the affected copies from the bin; contact us if you need help.
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, including the App's copies, your organization (the Atlassian customer) is the controller and Atlassian processes it on your behalf. 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, checks who is asking on every request, restores work items as the restoring person, hides restricted copies from non-admins and records every deletion and restore. It keeps no credentials and has no outbound network access.
9. Changes
We will post changes to this policy at its listing URL and update the effective date. Material changes will also be noted in the App's release notes.