Commit Span for Bitbucket privacy policy

Last updated November 6, 2026

What it reads

On pages whose address looks like a pull request on a Bitbucket server, it reads, using the session you're already signed in with:

• the page's address, and the labels and commit hashes on the page, to find where to add its controls;
• the pull request's commits: their hashes, messages, authors and dates;
• the pull request's list of changed files, and the code changes in those files, to work out what a span of commits changed.

Its only requests read from that same server, and it never changes anything there. Comments you leave are posted by Bitbucket's own page.

The extension's demo page is an exception: there, the same data comes from made-up files on that page, and nothing is sent anywhere.

What it stores

When you choose a span of commits to review, it saves that span in your browser's session storage for that tab, including the text of the lines those commits changed. It's used to narrow Bitbucket's Diff tab to that span. It's deleted when you close the tab, and removed earlier when you choose to show all changes. Nothing else is stored.

What it shares

Nothing. None of what it reads or stores is sent to the developer or to anyone else. It doesn't sell, transfer or use your data for anything other than showing you the commits you chose.

Site access

Self-hosted Bitbucket servers can have any address, so the extension asks to run on pages on any site whose address looks like a Bitbucket pull request (/repos/.../pull-requests/...). It doesn't load on other addresses. If a site that isn't Bitbucket has addresses of that shape, it runs there too, and its requests stay on that same site.

Open source

The code is public, so you can check all of this yourself: github.com/ignaciofh9/commit-span-for-bitbucket.

Changes

If this policy changes, the new version will be posted here with a new date.

Contact

Questions about this policy: ignaciofh9@gmail.com