Privacy policy
Last updated: November 19, 2026
Timebridge ("the app") is a Jira Cloud app published by Timebridge Labs, operated by Taeho Kim in Canada. It connects Jira to the time tracker each user chooses: Clockify or Harvest. This policy explains what the app handles and why. Contact: timebridge.support@gmail.com.
Where the app runs
Timebridge is built on Atlassian Forge, so it runs on Atlassian's infrastructure. Timebridge Labs runs no servers of its own and does not receive copies of your data.
What the app stores
The app keeps the following in Forge storage, inside the customer's Atlassian site:
| Data | Why | How long |
|---|---|---|
| Each user's tracker credential: Clockify API key, or Harvest token and account ID, plus the tracker user ID, name, email and workspace list the tracker returns | To make that user's requests to their tracker. Kept in Forge's encrypted secret storage. | Until the user clicks Disconnect, their Atlassian account is closed, or the app is uninstalled |
| Project settings: default tracker project and task, worklog on/off, rounding | To prefill timers for a Jira project | Until changed or the app is uninstalled |
| Each user's last tracker project and task per Jira project | To prefill the next timer | Until their Atlassian account is closed, or the app is uninstalled |
| The Atlassian account IDs of people who connected a tracker, with a timestamp | To find and erase data when an Atlassian account is closed | Until their Atlassian account is closed, or the app is uninstalled |
| Tracker entry ID → Jira worklog ID | To make sure the same time is never logged twice | Until the app is uninstalled |
What the app sends, and where
- To the tracker the user connects (Clockify, including its EU, USA, UK or Australia region servers, or Harvest): the Jira issue key, the issue summary, the user's optional note, the chosen project and task, and start and end times. Requests go directly from Atlassian Forge to the tracker's API.
- To the same Jira site: worklogs, created as the signed-in user with that user's own permissions.
The app reads only the issue being viewed (summary, time spent, project, issue type), the project's issue types on the settings page, and the user's own permissions. It does not read comments, attachments, descriptions or other issues.
What the app does not do
No analytics or tracking, no advertising, no selling or sharing of personal data, and no use of your data to train AI models.
Sub-processors
- Atlassian: hosting and storage (Forge).
- Clockify (CAKE.com Inc.) or Harvest (Forecast Inc.): only the tracker each user chooses to connect, under that tracker's own privacy policy.
Retention and deletion
- Disconnect in the panel deletes the user's credential immediately.
- Closed Atlassian accounts: once a week the app asks Atlassian which accounts were closed and erases everything it holds for them (credential, preferences and account ID).
- Uninstalling the app removes its Forge storage for that site, according to Atlassian's Forge data retention policy.
- Worklogs and tracker entries belong to the customer's Jira and tracker accounts; removing the app does not change them.
- For any other request (access, correction or deletion), email us.
Security
- Credentials are stored with Forge's encrypted secret storage and are never sent back to the browser.
- All traffic uses HTTPS.
- Project settings can be changed only by Jira project admins, and this is checked with Jira on every save.
- Report a security issue to timebridge.support@gmail.com. We aim to respond within two business days.
Changes
We'll update this page and its date when the policy changes. Material changes are announced in the Marketplace listing.