Chartmere: Jira Charts and Reports for Confluence: Privacy Policy
Effective date: October 1, 2026 Publisher: Great Work LLC, 651 N Broad St Suite 206, Middletown, DE 19709, USA Contact: hello@greatwork.company
This policy explains what information the Chartmere app for Confluence Cloud and Jira Cloud (the "App") processes, where it is kept, and your rights. It covers only the App, not Atlassian's products, which are governed by Atlassian's own privacy policy.
1. Summary
- The App runs entirely on Atlassian's Forge platform ("Runs on Atlassian"). It has no servers of its own and sends no data to Great Work or to any third party. It uses no AI service.
- To draw a live chart, the App reads from Jira the work items a page's JQL query matches, keeps only the ones the person viewing the page can browse, and counts them. It reads only the fields the chart uses.
- A short-lived copy of each viewer's chart data is cached in your site's app storage for that viewer only. Snapshots, which page editors take on purpose, are kept until deleted.
- Great Work LLC cannot see your charts, your Jira data or your settings.
2. What the App processes
| Data | Why | Where it lives |
|---|---|---|
| Chart settings: title, JQL, chart type, field ids, measure, date range, reader filter fields, display options | To draw the chart | Inside the macro on the Confluence page (macro configuration), like any page content |
| Per-viewer cache: for one viewer and one chart, the work item ids and keys and the values of the fields the chart uses (status, priority, labels, dates, numbers, and for people fields the account id and display name, never an email address) | So reopening the page within a few minutes does not read Jira again | Forge app storage for your site, for the minutes your admin sets (default 5, can be turned off); only ever read back for the same viewer |
| Snapshots: the same values for the work items the page editor could browse when they took it, with the time and the editor's account id | To show a frozen chart on the page | Forge app storage, until an editor replaces or deletes it, or the App is uninstalled |
| Jira field list (field ids, names, types) | For the settings panel pickers | Forge app storage, refreshed every 10 minutes |
| Site settings: most work items per chart, cache minutes, snapshots on or off; a marker that the install is a development install | To apply your admins' choices | Forge app storage |
The App does not collect email addresses, IP addresses, passwords, API tokens, payment information or analytics. It sets no cookies and loads no third-party scripts.
3. What the App reads but does not store
To decide what each viewer may see, the App asks Jira which work items that person can browse (including issue security levels). To decide who may take a snapshot, it asks Confluence whether the person can edit the page. These answers are not stored.
4. Where data is stored
All App data is stored by Atlassian in Forge app storage for your site, subject to Atlassian's data residency settings. Confluence is the App's required product, so its data is stored in your Confluence site's data residency location, per Atlassian's multi-app rules. Atlassian is the hosting provider and acts as a subprocessor under Atlassian's terms. Great Work LLC uses no other subprocessors.
5. Who can see what
- Live charts: each viewer sees counts of only the work items they can browse in Jira. A viewer's cached data is stored under a key that includes their account id and is never shown to anyone else. Anonymous viewers do not see live charts.
- Snapshots: everyone who can view the page sees the frozen values, including people without Jira access. This is the purpose of a snapshot, like a table an author pastes into a page. Only people who can edit the page can take, replace or delete it, and it only contains work items they could browse. Confluence admins can turn snapshots off for the whole site.
- Readers' filter choices are not saved.
- Great Work LLC: no access. If you open a support request, we see only what you send us.
- Atlassian: as the platform operator, under Atlassian's privacy policy.
6. Retention and deletion
Cached chart data expires after the minutes your admin sets and is overwritten on the next read. Snapshots stay until a page editor replaces or deletes them. Uninstalling the App removes its Forge storage according to Atlassian's Forge data deletion process.
7. Support requests
If you contact support through our help desk or by email, we process what you send (name, email, message, attachments) only to answer you, keep it up to 24 months, and delete it sooner on request.
8. Your rights
Depending on where you live (for example EU/UK GDPR or US state privacy laws), you may have the right to access, correct, delete or port personal data and to object to processing. For data in your Atlassian site, your organization (the Atlassian customer) is the controller and Atlassian processes it on your behalf; your admins can delete snapshots, turn off caching or uninstall the App. For support data, Great Work LLC is the controller: email hello@greatwork.company. We respond within 30 days.
9. Security
The App uses only Atlassian-hosted compute and storage, has read-only access to Jira and Confluence, filters every live chart by the viewer's own Jira permissions, checks page edit permission before any snapshot change, and keeps admin settings on an admin-only page. Report vulnerabilities to hello@greatwork.company.
10. Children
The App is a business tool and is not directed to children under 16.
11. Changes
We will post changes here and update the effective date. Material changes will also be announced in the App's Marketplace release notes.
12. Contact
Great Work LLC, 651 N Broad St Suite 206, Middletown, DE 19709, USA. hello@greatwork.company