Privacy & permissions

Where it runs

URLflows for Jira runs only on Atlassian Jira pages (*.atlassian.net) in your browser. On other sites it does nothing at all.

What it reads

Two things, both on the site you're already signed in to:

• The page in front of you — the board or backlog you've opened, so it knows which issues to attach subtasks to.
• Jira's own REST API, asked as you, on your own site — for the subtask details it displays, and (if you switch the section on) for your own permissions, the project lead and your group memberships.

Because every call is made with the access you already have, the extension can't see anything you couldn't see yourself by clicking around Jira. It doesn't elevate, borrow or store credentials. Subtask lookups are cached for five minutes and access lookups for ten, purely to keep the number of calls down.

No backend, no account

• There's no backend — the extension talks only to your own Jira site.
• There's no sign-in and no account to create.
• There are no analytics and no trackers. Nothing is sold, and nothing is sent to URLflows or any third party. Your Jira data stays between you and Jira.

Your settings and notes stay in your browser

Everything the extension keeps — your settings, your Jira Notes and your Page Guide wording — lives in your browser's extension sync storage. That means they follow you to the other Chrome windows you're signed into, through Google's sync, exactly like your bookmarks do. They are never uploaded to URLflows.

One browser permission

The extension requests a single permission: storage, so it can save your settings and notes. That's the whole list.

Questions about privacy?

If anything here isn't clear, let us know — we're happy to explain exactly what the extension does and doesn't do.

Related guides

Curious how the data on screen becomes subtasks? See What URLflows for Jira does. Want the detail on the permissions read-out? See See your access in a project. Hitting a snag? See Troubleshoot common issues.