Earlywick

Privacy Policy — Queue Aging Heatmap

Last updated: 24 July 2026

Queue Aging Heatmap runs entirely on Atlassian Forge, Atlassian's own hosting platform for Marketplace apps. It never sends data to any server outside Atlassian's infrastructure. There are no analytics services, no third-party SDKs, and no external network calls of any kind at runtime.

What the app accesses

To do its job, the app reads (never writes):

The app does not read ticket descriptions, comments, attachments, or any custom fields beyond what's listed above, and it never modifies, creates, or deletes any Jira data.

What the app stores

Two things, both inside Forge's own storage (not a third-party database):

  1. Your gadget configuration — which service project, queues (or custom JQL), age buckets, and grouping you chose. This persists per gadget instance so you don't have to reconfigure it every visit.
  2. A cached aggregate — the computed heatmap counts (not full ticket content) for up to 15 minutes, to avoid re-querying Jira on every dashboard load. This cache expires automatically and is rebuilt from live Jira data afterward.

Storage is scoped to this app's installation and is not accessible to other apps or sites.

Who can see this data

Data is read using the permissions of the Jira user viewing the dashboard (via Forge's asUser() API) — the app never uses elevated or app-level access to see more than the viewing user already can. It is not shared with the developer, with Atlassian beyond normal Marketplace operation, or with any other party.

Data retention and deletion

Changes to this policy

If this policy changes, the updated version will be published at the same location and the "Last updated" date above will change accordingly.

Contact

Questions about this policy or how the app handles data can be sent to support@earlywick.com, or via the support contact listed on the app's Marketplace listing page.