Privacy Policy
Honest Checklist for Jira, published by Backyard Tools.
Overview
Backyard Tools (“we”, “us”) operates Honest Checklist for Jira, an app for Jira Cloud built on Atlassian’s Forge platform. This policy explains what data the app collects once it is installed on your Atlassian site, how that data is used, where it is stored, who else can see it, and how to remove it.
Data we collect
The app stores only what it needs to run your checklists:
- Checklist item text, its checked/unchecked state, its position in the list, and when it was created.
- Saved template names and the items inside them, kept per Jira project.
- The Jira issue key and project ID that a checklist or template belongs to — used only to store and look up the right data, not for any other purpose.
That is the complete list. The app does not collect your name, email address, IP address, or device information, and it has no analytics or usage-tracking of its own. It has no sign-up and no user account — anyone who already has Jira access to an issue sees the same checklist stored on that issue, exactly like any other issue field.
How we use it
Solely to show, edit, and store your checklists and templates in the Jira issue panel, and — only if a project or site admin has opted a specific workflow transition into it — to check whether every item is complete before allowing that transition. We do not use this data for advertising, profiling, or anything beyond operating the feature you are looking at.
Where it is stored
All app data lives in Atlassian’s own Forge hosted storage — the Forge platform’s built-in storage, scoped to this app. We do not run a separate server or database of our own. Forge hosted storage automatically follows the data residency region your Atlassian site is configured to use (for example EU, US, or another region Atlassian supports); we do not choose or move that region ourselves.
Who else sees it
No one outside Atlassian’s own platform. The app makes exactly one network call beyond Forge’s storage APIs: a request to Jira’s own REST API, on the same Atlassian site, to confirm you are allowed to see an issue before reading or writing its checklist. That call stays inside the Atlassian platform your data already lives in — it is not a third party. The app does not send data to any external service, analytics provider, or AI/LLM API, and it has no subprocessors.
How long we keep it, and how to delete it
- Delete an item, a whole checklist, or a saved template at any time from the issue panel — this takes effect immediately.
- If your site admin uninstalls the app, Atlassian’s Forge platform retains the app’s stored data for 28 days (in case the app is reinstalled and the data should be reattached to it), then deletes it automatically. We keep no separate copy anywhere, so once that window passes, the data is gone.
Your rights and choices
Because a checklist lives on the Jira issue itself, controlling who can see or change it is a matter of your own Jira project permissions — the same permissions that already control the rest of the issue. To access, export, or erase data the app has stored, an admin can use the in-app delete controls described above, or uninstall the app to start the deletion described above. For anything those controls do not cover, contact us using the details below.
Children’s data
This app is a business productivity tool for Jira Cloud. It is not directed at children, and we do not knowingly collect data from them.
Changes to this policy
If this policy changes, we will update the “last updated” date below. We will reflect material changes here before they take effect.
Contact
Questions about this policy or the data the app stores: use the support form.