Effective: 9 September 2026
Slide Rule: Calculated Fields for Jira ("the app") is published on the Atlassian Marketplace by Two Little Moons Consulting, ABN 49 732 400 198, Penrith, NSW 2750, Australia ("we", "us"). Contact: support@twolittlemoons.com.
This policy is specific on purpose: every category of data the app touches is itemised below.
The app computes the value of a custom field from a formula a Jira administrator writes — from other fields on the same work item, and optionally from its children, its parent or the work items linked to it — and writes that value back into Jira so it appears on boards, in JQL and in exports. It runs entirely on Atlassian's Forge platform and sends data to no server outside Atlassian.
When a work item is created or changed, and when a newly saved formula is applied to existing work items, the app reads:
/myself),
recorded on the definition as who last changed it;/mypermissions), to check they may administer
the site before their change is accepted.Reads that serve a page a person is looking at are made as that person, with their own Jira permissions. The background recompute runs as the app, because it runs on work items nobody is looking at; see "Data visibility" below for what that means and what the app refuses to do because of it.
In Forge storage, inside your own Atlassian site:
Nothing else is stored. There is no copy of your work items, and no history beyond the most recent result per work item.
A computed value is an ordinary Jira field value, so anyone who can see the work item can see it, exactly as they can see its other fields. Because the recompute has no reader to check against, the app refuses to compute a rollup when a contributing work item carries an issue-level security level, or when a child is in a different project from its parent — rather than turn a restricted work item into an aggregate everyone can read. The work item says when this has happened, and how many were involved.
None. The app declares no permissions.external of any kind: no fetch, no egress,
no remote host, no analytics and no runtime AI call. It is not technically capable of
contacting any host other than Atlassian's own APIs.
The app writes operational log lines to Atlassian's Forge logging: work item keys and ids, field ids, counts, and the status of a failed Jira request. It does not log field values, computed values, formulas, or the bodies of Jira's responses.
All data is held in Forge storage inside your Atlassian site and is destroyed when the app is uninstalled. Deleting a field definition deletes the definition; the values it has already written remain on your work items until they are cleared, and can be removed by deleting the field itself in Jira's custom field administration.
Because the app stores everything inside your own Atlassian site and sends nothing elsewhere, requests about personal data — access, correction, erasure — are answered by your own Atlassian administration. Write to support@twolittlemoons.com if you need help identifying what the app holds.
We are a data processor, not a data controller, and a service provider, not a business. We process End-User Data only inside Atlassian apps and services, on your instructions, and we share it with no third party.
Material changes to this policy will be published on this page with a new effective date before they take effect.