The main checklist view, as presented on the screenshot below, disappears (the view is rendered by Issue Checklist app, so once the app is removed, the view is no longer there):

When the Issue Checklist is uninstalled, the data is still available in custom fields (if "Save checklist data to Jira custom fields" option was enabled when the app was in use). It means that if you add the Text or YAML custom field to the View Issue screen in Jira, you can still see the checklist like this:

The data also stays in Issue Checklist external database for 90 days (as explained in Privacy Policy). After 90 days the data is permanently deleted. If you re-install the app before 90 days since uninstallation, you can still access the data and use Issue Checklist as usual. 

The checklist data is stored both in Jira (custom fields and entity properties) and on our servers.

Safety

We care about the safety of your data:

• We encrypt the data in transit but also at rest when stored on our servers 
• We do backup data every day
• The main database has 1 primary node and 2 backup nodes to minimize the risk of an outage
• We use trusted DB provider, i.e. MongoDB.com 
• Only authorized personnel can access the data
• All our systems are protected with two-factor authentication.

Read more in our Security Statement

Why we store data on our servers

The reason why we store checklist data on our servers is both security and flexibility:

• storing checklist items in Jira custom field means that:
  • data is limited to 32kb per issue
  • removing the custom field removes all checklist items from all projects (that is extremely risky)
• storing checklist items in Jira issue entity properties means that:
  • data is limited to 32kb per issue
  • no custom permission can be implemented (every user who can see Jira issue could also see checklist items; every user who can edit Jira issue could also edit/delete checklist items)

We avoid the above limitations by storing data on our servers. This way you can store as many checklist items as you need and use custom permissions to control who can view, add, edit, toggle or delete the checklist items.

Jira storage (custom fields)

Checklist data is also stored in Jira custom fields as long "Save checklist data to Jira custom fields" option is enabled in Global Settings. It means that:

• Every checklist action you take updates also Jira issue by saving new value to custom fields. It adds an entry to the Jira issue history and notification area.
• Checklist data is stored in Jira so your Jira backup contains checklist data too. This way you can keep your backup safe according to your company policy.
• You can read and modify the checklist through API by reading and modifying the text stored in custom fields. 
• Checklist fits into custom fields only up to 32kb 

If you don't accept any of the above, please disable "Save checklist data to Jira custom fields" option in Global Settings. In that case, checklist items will be stored only on our servers. 

Jira storage (entity properties)

Checklist meta-data is stored also in Jira entity properties. These include information if all items are completed, how many items are in the checklist, etc. 

We also store raw checklist items text in entity properties to enable JQL search of the checklist items text (as long as custom View Checklist permission is not enabled).