Data and Privacy

Simple Checklist for Jira runs entirely on Atlassian Forge. It has no external servers, so your checklists never leave Atlassian. This page lists what the app stores and what it only reads.

What the app stores

Data	Where	Contents
Checklist items	The app's Forge storage for your site	Text, status, section or item, requirement, order, due date, linked sub-task key, the issue and project IDs, and who created and last changed it (Atlassian account ID). An assignee is stored with their account ID, display name and avatar URL
Checklist progress	An issue property on each issue with a checklist (yamunoChecklist)	Counts only: total, done, open, required open, percent done, and whether it has a checklist
Activity	The app's Forge storage	What changed, the item text, when, and the account ID of who changed it
Templates	The app's Forge storage	Name, items with their requirement, auto-add projects and issue types, and who created it
Settings	The app's Forge storage	Statuses, the assignee-only option, and the Automation token
"What's new" dismissals	The app's Forge storage	Per person: the account ID and which announcement they closed

What the app only reads

None of this is stored:

• The issue's key, project and issue type, to apply templates and run validators
• People's names and avatars for the assignee picker and the activity list
• Whether the signed-in user is a Jira admin, before saving settings or templates
• Your projects and issue types, for the template auto-add pickers

What the app doesn't do

• Send data to external servers or third-party services
• Include analytics or tracking inside the app
• Change issues, other than the progress property, and sub-tasks someone asks it to create

The Automation web request

The Automation URL is a Forge web trigger, hosted by Atlassian. It accepts a request only with your site's token, and only changes checklists.

Removing your data

Deleting an item or a template removes it. When the app is uninstalled, Atlassian deletes its Forge storage, as for every Forge app. Progress properties stay on issues until they are removed through Jira's REST API.

Scopes

storage:app (checklists, templates, settings, activity), read:jira-work (issues, projects, issue types, permission checks), write:jira-work (progress properties and sub-tasks) and read:jira-user (names and avatars).