Security

Effective 02/11/2026.

Runs on Atlassian

Checkwright is built on Atlassian Forge and runs entirely on Atlassian's platform. It is built to be eligible for the Runs on Atlassian program: it makes no connections outside Atlassian and we operate no servers of our own.

Where data is stored

• Checklists: in your Jira site, with each work item.
• Templates and settings: in Atlassian-hosted app storage for your site.
• Nothing is stored outside Atlassian. Data residency follows your Jira site and Atlassian's Forge platform.

Permissions

• Read Jira work: to show checklists, search with JQL and list projects for templates.
• Write Jira work: to save checklists on work items and create subtasks you ask for.
• Read Jira users: to show names and avatars of assignees, and to notify an assignee.
• Manage Jira configuration: to provide the Checklist progress field and the Checklist complete validator.
• App storage: to keep templates and settings.

Every read and change to a work item is made with the permissions of the person using Checkwright, so nobody can see or change a work item they couldn't already. The app acts on its own only to update its read-only progress field after a permitted change, and to add auto-apply templates that a Jira admin has set up when a work item is created.

Who can change settings

Only Jira admins, and members of template manager groups chosen by a Jira admin, can manage templates and settings. Only Jira admins can turn on auto-apply.

Reporting a problem

If you think you have found a security issue, email support@wattlebrooks.com. We aim to reply within 2 business days.