Privacy policy
Effective: 14 August 2026 · Last updated: 14 August 2026
Who we are
lunalink.ai (the trade name of 12824574 Canada Inc.) operates Time in Status Panel for Jira, an app for Atlassian Jira published on the Atlassian Marketplace under the LunaLink AI partner account. This policy explains what data the app accesses, why, and how it's handled. Questions: hello@lunalink.ai.
What the app accesses (Atlassian permissions)
- Read Jira work data (
read:jira-work) — to read a work item's status history, created/updated timestamps, and comment dates at the moment you open the panel, so it can compute how long the item has spent in each status. - App storage (
storage:app) — to save the three aging-threshold numbers your Jira admin sets on the app's settings page.
The app does not request write access to your issues and cannot modify Jira data.
What we store
Three numbers: the aging, stale, and no-activity thresholds configured by your admin, kept in Atlassian-hosted Forge storage inside your own Atlassian instance's scope. Everything else — durations, percentages, staleness flags — is computed in memory each time a panel loads and is never persisted. The app stores no issue content, no personal data, and no usage analytics.
Where it runs and who else is involved
The app runs entirely on Atlassian's Forge platform: Atlassian hosts the compute and the storage, and the app makes no network calls outside Atlassian. There are no third-party services, no subprocessors, and no data leaves your Atlassian instance. Data residency and encryption are inherited from Atlassian's Forge platform, and the app is designed to meet Atlassian's "Runs on Atlassian" criteria.
Data deletion
Uninstalling the app removes it and its stored settings from your instance under Atlassian's Forge data lifecycle. There is no other stored data to delete. For any deletion request or question, email hello@lunalink.ai.
Changes
If the app's data practices ever change — for example a future version adds a permission — this page will be updated before that version ships, and Atlassian additionally requires admins to re-approve any new permissions before they take effect.