What Team Checklist stores, what it reads from Google Tasks and Jira, who can see the team checklist, and what never leaves Atlassian and your own Google account.

Data Storage and Processing

Team Checklist is built on the Atlassian Forge platform. Everything the app stores is kept in Atlassian’s Forge-hosted storage for your site, which follows your site’s data residency — never on a server or database we operate. Simplify has no access to it. The app talks to two systems only: your Jira site and Google’s Tasks API for your own Google account.

In the app’s Forge storage the app keeps:

for each issue: the id of the Google task list attached to it;
for each person and issue: which of their connected Google accounts the issue uses (only when they choose one);
for each issue: the Links tab’s links (title and URL);
for each issue: the team checklist — each item’s title, details, due date, whether it is done, and the Atlassian account ids of who added, completed and last changed it, with the time;
for each person and issue: which team items they copied to their Google Tasks (the Google task’s id);
an internal index of task lists attached before version 4 (issue and project keys, ids and types), no longer written.

Google Tasks

What the app accesses. When you connect your Google account, the app asks for three permissions and nothing else:

https://www.googleapis.com/auth/tasks — to create, read, edit, complete, reorder and delete the task lists and tasks you work with in the panel;
https://www.googleapis.com/auth/userinfo.email and profile — to show which Google account is connected (its email address and picture).

The app never reads your mail, calendar, contacts or Drive. Your Google sign-in (the OAuth token) is held by Atlassian’s Forge platform, not by the app, and is used only when you act in the panel, for you.

How it is used. Your tasks are read from Google when you open the panel or refresh it, shown to you, and changed in Google when you change them. The app does not keep a copy of your tasks: Forge storage holds only the id of the attached task list. What the app sends to Google is what you enter in the panel — list titles (the Use the issue key and summary and Create checklist buttons put the issue key and summary into the list title), task titles, details, due dates, completion and order. A Google Drive link you paste into a task is stored as text in that task’s details; the app does not access Drive.

Moving between Google and the team checklist happens only when you choose it. Share with the team… and Copy to the team checklist… copy a list’s open tasks into the issue’s team checklist, after a question that says who will see them; from then on they are team items, visible to everyone who can see the issue. Copy to my Google Tasks copies team items into your own Google Tasks. Nothing personal becomes shared by itself.

Google API Services User Data Policy. The app’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The app uses Google Tasks data only to provide the checklist features you use in Jira, never uses it for advertising, never sells it, never transfers it to anyone except as described above at your direction, and never allows humans to read it except as needed for security, legal compliance, or with your explicit consent.

The Team Checklist

The team checklist is visible to everyone who can see the issue in Jira, and can be changed by everyone who may edit the issue; Jira’s permissions are checked as the person using the app on every read and change.

Names. From version 4, the panel shows the display names of the people who added or completed team items. The app asks Jira for them, as the person viewing the issue, when the panel opens; it does not store names — only the Atlassian account ids listed above.

A copy in the issue (from version 4). So that Jira search, Automation and workflow rules can use the team checklist, the app also writes a copy into each issue that has one, as a Jira issue property: the progress, the dates of the open items, and each item’s title, whether it is done, its date and its parent item — no details, names or account ids. The copy is written by the person who changed the checklist, with their Jira permissions. It is part of the issue’s data in Jira: everyone who can see the issue can read it, and Jira’s search indexes it.

We do not share your data with third parties. The app sends data only to Google’s Tasks API for your own Google account, as described above, and to your own Jira site. No analytics, tracking or other external service is used.

Accessing, Correcting, or Deleting Your Data

Team checklist items can be edited or deleted in the panel by anyone who may edit the issue. They are deleted automatically when their issue is deleted.
Your Google tasks and lists are yours in Google Tasks: edit or delete them in the panel or in Google Tasks. Removing a list from an issue leaves it in Google; the panel can also delete it in Google.
Your Google connection: remove it in your Atlassian account’s connected apps (the panel’s Disconnect… opens the page) or in your Google Account (Security → Third-party access).
Links can be removed in the Links tab.

If you have a question about your data, contact us via our Support Desk.

Data Security Measures

Runs on Atlassian Forge, in Atlassian’s hosted storage, scoped to your site
Every change is made as the person using the app, with their own Jira permissions and their own Google account
Google access is requested only for Tasks and the connected account’s email and profile
No server of our own, no analytics, no third-party services

Persistent App Data

Forge-hosted storage keeps the data listed above while the app is installed. When the app is uninstalled, Atlassian deletes the app’s stored data after its documented retention period. Data in your own Google Tasks stays in your Google account. Jira keeps issue properties as part of the issue when an app is uninstalled: the copy of the team checklist in each issue (from version 4) stays until someone who may edit the issue deletes it, for example through Jira’s REST API (DELETE /rest/api/3/issue/{issue}/properties/simplify-team-checklist).

Updates to this Policy

This policy may be updated from time to time. Any changes will be published on this page.

By using our apps, you agree to be bound by our End User License Agreement (EULA), which governs the use of our apps.

For more information about Atlassian’s privacy practices, see the Atlassian Privacy Policy. For Google’s, see the Google Privacy Policy.

Privacy Policy for Team Checklist