Privacy policy – Rule Keeper for Jira
Effective date: 11 October 2026.
This policy explains what the Rule Keeper app ("the app") for Atlassian Jira Cloud, published by NoxDevelopment ("we"), does with data.
Summary
The app runs entirely on Atlassian's Forge platform. It stores its data in your Atlassian site's app storage and sends nothing to us or to any third party. We cannot see the data the app stores.
Data the app stores in your site
| Data | Purpose |
|---|---|
| Automation rule metadata: name, description (first 2,000 characters), state, scope (project IDs), trigger type, component types and counts, logic fingerprint, labels, created and updated dates, error notification and access settings | Inventory, change history, lint and cost forecast |
| JQL of scheduled rules that process issues | Counting matching issues for the cost forecast |
| Atlassian account IDs of rule authors, rule actors and the administrator who uploaded a snapshot | Ownership and actor health checks |
| Whether those accounts are active and whether they are personal accounts | Actor health checks |
| Plan and user counts you enter, cached issue counts | Cost forecast |
| An encrypted sync secret, if you enable the optional sync tool | Verifying signed sync requests |
The app does not store rule bodies, smart values, issue content, comments, names, e-mail addresses or any other profile data.
Where the data lives and for how long
- In Forge hosted storage of your site, which follows your site's data residency settings.
- The 10 most recent snapshots are kept; older ones are deleted automatically. Cached analyses expire after 7 days.
- Uninstalling the app deletes all stored data.
Personal data
The only personal data is Atlassian account IDs. Once a week the app reports them to Atlassian through the Forge Privacy API, and IDs of closed accounts are removed from all stored snapshots and analyses.
Data we receive
None from the app. If you contact support by e-mail, we receive what you send us and use it only to answer your request. We keep support e-mails for up to 24 months.
Optional sync tool
The rule-keeper-sync tool runs on your own computer or CI. It uses your
Atlassian API token to read your Automation rules from Atlassian and sends a
summary directly to the app in your site. The token never leaves the machine
that runs the tool and is never sent to us.
Your rights and contact
Data in the app belongs to your organisation and is managed by your Jira administrators. For questions about this policy, write to support@687.monster.
Data controller for support communication: NoxDevelopment, support@687.monster.