Privacy Policy: PivotPulse for Jira

Last updated: 13 November 2026

PivotPulse for Jira ("the app") builds pivot tables, hierarchy roll-ups and worklog reports from Jira issues, on its Reports pages, in a dashboard gadget and through its Rovo agent "Jira report builder". It is published by Ritom Puzari, trading as PuzariCloud, India ("we", "us").

Summary

Data the app processes

DataWhyWhere it is kept
Issue fields used by a report (for example status, assignee, issue type, labels, sprint, story points, estimates, time spent, parent)To build the pivot table, roll-up and chartReports pages and gadget: read from Jira into the user's browser for that session only. Rovo agent: read into the memory of the app's Forge function on Atlassian for that request only. Never stored
Worklogs (author, start date, time spent) of issues in a worklog reportTo total hours per person, project, epic or issue per periodSame as issue fields: the user's browser, or the Forge function's memory for a Rovo agent request. Never stored
Rovo agent requests: the JQL, field names, issue keys and dates that Rovo passes to the app, and the table the app returns (counts, sums and hours; names of people or field values used as row and column labels; in a roll-up also issue keys, shortened summaries, issue types and statuses)To answer a reporting question in Rovo chatProcessed in the app's Forge function on Atlassian and returned to Rovo, which is an Atlassian product. Not stored by the app. What Rovo keeps of a chat is handled by Atlassian
Display names of users shown in a reportTo label rows and columnsRead live from Jira each time a report runs; never stored
Saved report definitions: report name, JQL text or saved filter id and name, field ids, aggregate, date range and display settingsSo reports can be reopened and shared on the siteForge storage (Atlassian) until a user deletes the report or the app is uninstalled
Rating prompt state: how many reports have been run or exported on the Reports page in this browser, the time of the first one, and the answer to the prompt (later, never, or rated). No account ID, name or other identifierTo ask for a Marketplace rating once, after real use, and not ask againOnly in the user's browser (localStorage), per person per browser. Never sent to or stored on a server. It stays until the user clears the browser's site data
Dashboard gadget settings (a copy of the report definition)To show the report on a dashboardStored by Jira with the dashboard gadget
Exported files (CSV, XLSX)Requested by the userSaved to the user's device by the user's browser; never sent to us

A saved JQL query is free text. If someone types an account ID or a name into a query, it is stored as part of that query. We recommend using functions like currentUser() or groups in saved reports.

Who receives data

Atlassian hosts and runs the app (Forge). See Atlassian's privacy policy. Rovo, which shows the agent's answers, is also run by Atlassian. No data is sent anywhere else, and we (the developer) have no access to your Jira data or saved reports. If something fails, the app writes a short technical error message to the Forge log; it does not log report content.

Retention and deletion

Any user who can open PivotPulse can delete a saved report, and it is removed immediately. Atlassian deletes the app's Forge storage (the saved reports) after the app is uninstalled. The rating prompt state exists only in your browser; clearing the browser's site data for Jira removes it. Jira data is never stored by the app, so there is nothing else to delete.

Contact

Ritom Puzari (PuzariCloud), Assam, India. Email: support@puzaricloud.in

PivotPulse help