Cascade for Jira

Your data never leaves your browser.

Cascade for Jira displays and exports your Jira issue hierarchy. It has no server, collects nothing, and shares nothing.

Everything the extension does happens locally, inside your own browser. The only network requests it makes are to your own Jira site — never to us or any third party.

What the extension accesses

When you open Cascade on a Jira Cloud page, it reads your Jira issue data — keys, summaries, types, statuses, assignees, dates, and hierarchy — by calling Jira’s own REST API from within your already-authenticated browser session. It only ever accesses data you are already permitted to see.

Where that data goes

Nowhere off your device. All processing is local:

There is no backend server, and the extension makes no requests to us or to any third party — only to your Jira site (*.atlassian.net).
Issue data is held in memory while the panel is open and cached in your browser’s local storage so reopening is fast. That cache lives only on your device and is never transmitted anywhere.
Exports (CSV or copy‑to‑clipboard) are generated locally and saved by you, to your device.

What we do not do

We do not collect, store, or transmit your Jira data, credentials, or personal information off your device.
We do not use analytics, tracking, advertising, or third-party SDKs.
We do not sell or share any data — we never receive any to begin with.

Permissions and why

storage Cache your loaded backlog locally so reopening the panel is instant. *.atlassian.net Read your Jira data from your own session on Jira Cloud pages. The extension runs only on Jira Cloud sites.

Data retention and removal

The local cache stays until it is refreshed or you remove the extension. Uninstalling the extension deletes all locally stored data.

Changes to this policy

If this policy changes, the “Last updated” date below will change. Material changes will be noted in the extension’s Chrome Web Store listing.

Contact

Questions about privacy? Email ahmedfiazjan2@gmail.com.