Cadence
Last updated: July 2026
Cadence ("the app") is a Forge application that runs on Atlassian's infrastructure inside your Atlassian Cloud site. This policy explains what data the app processes and where.
The app stores, in Atlassian-hosted Forge storage scoped to your installation (i.e. inside your Atlassian tenant): your SaaS subscription records (application name, vendor, category, seats owned, seats used, cost, renewal date), your alert settings (lead time, optional Slack/Discord webhook URL, optional Jira project key), and a record of which renewals have already been alerted. We do not operate a separate database of your data outside Atlassian.
Cadence does not collect end-user personal data. Subscription records are
about software tools, not people. The app requests read:jira-work
only to render inside Jira and write:jira-work only to create the
renewal tasks you enable.
When you use the redundant-tool analysis or generate a renewal-negotiation brief, the relevant subscription metadata (app name, category, seat counts, cost, renewal date) is sent to Anthropic (api.anthropic.com) to generate the result. This data is transmitted to produce the output and is not used by us to build a profile of you. See Anthropic's privacy terms for their handling. No personal data is included in these requests.
If you configure a Slack or Discord webhook, renewal-alert text is sent to that URL. If you set a Jira project key, the app creates renewal tasks in that project. Both are entirely optional and controlled by you.
Your data remains in your Forge storage until you delete it in-app or uninstall the app, after which Atlassian removes installation-scoped storage.
Questions about this policy: see the support page.