TaskBridge for TickTick

Privacy policy

This policy covers TaskBridge for TickTick ("the app"), a Forge app for Jira Cloud. The app lets each person add a Jira issue to their own TickTick and see that task's status on the issue, keep the issue's and the task's due dates the same, log their TickTick focus time on the issue as a Jira work log, move the issue to Done when the task is done, add their open assigned issues to TickTick, and make Jira issues from their TickTick tasks.

In Jira, the app shows as Add to TickTick in an issue's ••• menu, as the TaskBridge for TickTick panel on each issue ("the app's panel"), and as the TaskBridge for TickTick page in Jira's Apps menu ("the app's page").

This app is not created by, affiliated with, or supported by TickTick.

Where the app runs

The app runs on Atlassian's Forge platform. It has no servers or database of its own. It keeps a few small records in Forge storage, the app's own storage on Atlassian's platform. It sends data only to TickTick (api.ticktick.com, and ticktick.com for TickTick's sign-in), and once a week it reports the Jira account ids it stores to Atlassian (see "How long it stays"). It sends nothing to the developer or to anyone else.

TickTick is provided by Appest Inc., as TickTick's terms of service say. Its app-store listings name the developer as Appest Limited and TickTick Limited, of Hong Kong. TickTick says it hosts all its databases and servers on Amazon Web Services in the United States. What TickTick does with your data is covered by TickTick's privacy policy.

Because it sends data to TickTick, the app is not eligible for Atlassian's "Runs on Atlassian" badge.

What the app stores

The app keeps five kinds of small record in Forge storage, the app's own storage on Atlassian's platform. Only the app can read them, never other users. None of them holds task names, notes or any other task text.

1. Your links on an issue. For each issue where you added a task, made the issue from one of your tasks, or linked one of your tasks to it, the app keeps a list of your links, filed under your Jira account id and the issue's id. Each link has:

The list holds at most 50 links. The app deletes the list when your last link on that issue is removed.

The app keeps both due dates at the last sync so it can tell you which side changed later.

2. Your list preference. The id of the TickTick list you used last, filed under your Jira account id, so the form and the app's page can offer it next time.

3. Your focus marks. For each linked task whose focus time you logged with Log in Jira, the time up to which its focus time is logged, filed under your Jira account id and the task id. The app uses it so focus time already logged isn't offered again. Focus marks are kept for each Jira site. Remove my data deletes them too, so if you link the same task again within 29 days, focus time already logged on it is offered again: check the issue's work log before you log it.

4. A focus lock. While Log in Jira runs for a task, a record with the time it started, filed under your Jira account id and the task id, so two runs at once can't both log the same time. When Log in Jira finishes, the app deletes the lock. A run that couldn't finish, for example because Forge storage didn't answer in time, leaves it behind: after 60 seconds the app treats it as free, and the record stays until Remove my data or your account's closure.

5. Your account record. The date and time you last added a task or linked one to an issue, filed under your Jira account id. The app uses it for the weekly privacy report to Atlassian.

Who can see it

Only you, through the app. The app's panel shows each person only their own linked tasks and their own focus time, and no other Jira user can read your records. The tasks themselves stay in your own TickTick.

How long it stays

Apart from the focus lock, the app removes nothing by itself while it's installed. A link stays until you select Unlink on the task in the app's panel, even if the task is deleted in TickTick or can no longer be found there. Focus marks stay after Unlink, so focus time already logged isn't offered again.

Every week the app reports the Jira account ids it stores to Atlassian, each with the date its account record was last updated, as Atlassian requires. When Atlassian says an account is closed, the app deletes everything it stores for that account.

After the app is uninstalled, Atlassian deletes the app's storage. Forge keeps it for 28 days first, so it can be recovered if the app is reinstalled.

Otherwise your records stay until you remove them with Remove my data (see "How to remove everything").

What the app reads from and changes in Jira

It reads the issue's key, summary, due date and status, and the done statuses Jira lets you move it to. On the app's page, it reads the open issues assigned to you (key, summary and due date), to list them, and the issue whose key you type under Link to an existing issue, to link your task to it. It reads all of these as you, so it only sees issues you can see. It also reads your site's web address, to build the link to the issue, and your Jira time zone, for a task's due time. It gets your Jira account id from Atlassian's platform, to keep your records apart from other people's.

The app reads the issue as you before it stores anything for that issue, so it never stores anything for an issue you can't see.

The app changes an issue only when you click, with your own Jira permissions:

It changes nothing else on the issue.

When you select Create Jira issue on the app's page, the app fills in Jira's own Create issue window with the task's name, note and due date. Jira creates the issue only if you save it there.

What the app sends to TickTick

When you select Add task, it sends:

When you select Add tasks on the app's page (the button shows how many are ticked), it sends, for each issue you ticked, the task name (the issue key and summary), the issue link as the task's note, the list and priority you chose, the issue's due date and your Jira time zone.

When you select Update in TickTick, it sends the issue's Jira due date for that task. The task keeps its time of day and time zone, and its start date moves with the due date, so a task that runs over several days keeps its length. When you select Clear the due date in TickTick, it asks TickTick to remove the task's due date and start date; TickTick then removes the task's reminders too.

After Jira creates an issue from one of your tasks (Create Jira issue on the app's page), or when you link one of your tasks to an issue (Link to an existing issue), the app adds that issue's link to the end of the task's note in TickTick (on a checklist task, to its description).

When you select Unlink on a task in the app's panel, it takes that issue's link out of the task's note in TickTick, if the task is still open. The rest of the task doesn't change.

What the app reads from TickTick

The app shows these and doesn't store them, apart from the ids and times listed under "What the app stores".

When you connect, Forge reads your TickTick username (your email address) from your Inbox's list of members, and keeps it with the connection, to tell TickTick accounts apart.

Your TickTick connection

Each person connects their own TickTick account, using TickTick's own sign-in. Nothing is shared between Jira users.

The app asks TickTick for the tasks:read and tasks:write permissions, which allow reading and changing your TickTick tasks and lists. The app uses them only for what this page describes.

Your TickTick access token is held by Atlassian's Forge platform, not by the app. Forge adds it to each request the app makes to TickTick. The app doesn't store the token or log it.

What the app logs

The app writes to its log only when something fails. Each line is a fixed label for the failure, sometimes followed by the HTTP status code TickTick or Jira returned, for example ticktick:status:401. A line never contains task names, notes, issue keys, account ids, TickTick data or tokens.

How to remove everything

  1. Uninstall the app. A Jira admin uninstalls it from the site's app management page. The app then stops running on your site, and Atlassian deletes everything it stored (see "How long it stays").
  2. Unlink the app in TickTick. Each person removes it in TickTick under Settings → Integrations & Import → UnLink. After that, the app can no longer reach their TickTick.
  3. While the app stays installed, this is what removes your data:
    • Remove my data, on the last tab of the app's page (Apps → TaskBridge for TickTick), asks you to confirm first. Then the app deletes everything it stores for you on this Jira site: your links on every issue, your list preference, your focus marks and locks, and your account record. It works even after the site's subscription has ended. Your tasks stay in TickTick, and so does your TickTick connection: to end that too, unlink the app in TickTick (step 2). If it fails, it says so, and trying again finishes the erase.
    • To remove one task's link, select Unlink on the task in the app's panel. If the task is still open, it also takes the issue's link out of the task's note in TickTick.
    • When your Atlassian account is closed, the app deletes everything it stores for you. It checks every week, through the privacy report.
    • Uninstalling the app (step 1) removes everything it stores, for everyone.

Questions about your data: support@launchmotionlabs.com.

The tasks the app created stay in each person's TickTick, and so do the issue links it added to the end of tasks' notes. Delete or edit them in TickTick if you want them gone. Jira issues made from TickTick tasks are ordinary Jira issues and stay in Jira, and so do work logs made with Log in Jira.

Contact

Questions about this policy: support@launchmotionlabs.com.