Roll-up Reports

Privacy policy

Last updated 24 October 2026

Who we are

Roll-up Reports for Jira is an app for Jira Cloud, made by Stray Anchor Pty Ltd (ABN 22 700 917 111), Perth, Western Australia. It builds pivot tables and roll-up reports over a site's Jira issues, and can keep a daily history of them.

The short version

• Roll-up Reports runs entirely on Atlassian's Forge platform and calls nothing outside Atlassian. No other company handles your Jira data for us.
• Live reports are worked out in your browser from what Jira lets you see, and aren't stored.
• Saved reports and their history are stored by Atlassian for your Jira site, in your site's data residency location.
• We don't sell data, show ads, or use your data to train AI. We can't see your reports or history: they stay in your site's Forge storage.

Who's in charge of the information

Your organisation decides what goes into Jira and which reports to build. For the personal information in it, you're in charge (the "controller"), and the app handles it on your behalf (the "processor"). Our Data Processing Addendum sets out how, including the safeguards for data from Europe, the UK and Switzerland.

What the app handles, and why

• Your Jira issues, when you open a report: the fields the report uses, their status history and worklogs if it shows them, fetched as you (so Jira's permissions apply) and worked out in your browser. They aren't stored.
• Reports: each report's name, where its issues come from (a query, filter, board or project), its groupings, values and filters, and who it's shared with (people and groups). The last 50 saved versions of each report are kept, so changes can be undone.
• Favourites and views: which reports each person marked, and how many times a report was opened each day.
• History, if a report has it turned on: each day's totals per group. Group names can include people's names, issue keys and summaries, and field values. Issues with a security level are never stored. While a very large report's history is built over several runs, the issue data fetched so far is kept, compressed, until it's done (at most two days).
• Atlassian account IDs wherever a report names someone (its owner, sharing, filters on people, history grouped by person), so they can be reported to Atlassian and removed when an account is closed.
• Site settings: the working hours used for time in status, who receives reports when their owner leaves, who may export, and cached Jira information such as field names and the number of users (for the free plan).
• Your Jira site's address and ID, and whether your subscription is active, which Atlassian gives every app.

Who processes data for us

• Atlassian runs Roll-up Reports on its Forge platform and stores its data for your site. That's all the app uses.
• Only if you contact support: Cloudflare hosts this website and receives email sent to support@rollupreports.app; Microsoft Azure (Australia) hosts our support desk, where support conversations are kept; and Amazon Web Services (Sydney, Australia) sends our replies.

How long it's kept

• Reports, until someone deletes them. Saved versions: the last 50 of each report.
• History: 90 days on a paid plan. If a site moves to the free plan, its history is kept but no longer added to.
• Daily view counts: about 13 months.
• Data kept between history runs: until the run finishes, and at most two days.
• When Roll-up Reports is removed from your site, Atlassian keeps its stored data for your site for 28 days, during which it can be recovered on request, and then deletes it. We keep no copy anywhere else.
• Support conversations are kept until you ask us to delete them.

If Roll-up Reports is retired or changes hands

• If we retire Roll-up Reports, we'll tell you at least 90 days before it stops (see the terms of use), so you can export your reports. When it stops, it stops on every site, and Atlassian deletes its stored data within 30 days. We keep no copy. Your Jira issues aren't affected: the app only reads them.
• If another company takes Roll-up Reports over, the data stays where it is, in Atlassian's platform for your site. The new owner must keep to this policy and the Data Processing Addendum, and we'll tell you at least 30 days before.

Closed accounts

Every week the app asks Atlassian which of the accounts it stores have been closed, and removes them: reports pass to the site's chosen owner (or wait for an admin), the person comes off sharing lists, and history shows them as "Former user".

Your choices

Report owners can delete reports, stop sharing them, or turn their history off. Jira admins can do the same for every report on the site, from Jira settings → Apps → Roll-up Reports. To ask what we hold, or to have it deleted, email hello@strayanchor.com.au.

Changes

If we change how Roll-up Reports handles data, we'll update this page and change the date at the top. For a change that matters, we'll tell you in the app or by email first.