GuardPulse for Jira: privacy policy
Last updated 7 November 2026. Vendor: PuzariCloud (Ritom Puzari), support@puzaricloud.in.
Summary
GuardPulse runs entirely on Atlassian's Forge platform ("Runs on Atlassian"). It sends no data outside Atlassian, has no external servers, no functions, no analytics or tracking, and no storage of its own.
What the app reads
- When a Jira administrator configures the validator: the site's issue link types and statuses, read with the administrator's own permissions.
- When the administrator uses "Would it pass?": the rule is evaluated by Jira on the chosen issue with the administrator's own permissions. Only the result (pass, or the error text) is shown.
- During a transition, Jira itself evaluates the rule against the issue's links, sub-tasks, child issues and attachment count. The app code is not involved and receives nothing.
What is stored, and where
- Validator settings (which checks are on, link type IDs and names, status IDs and names, minimum counts, your messages) are saved by Jira inside the workflow, like any other workflow rule.
- The app stores no user names, account IDs, e-mail addresses or issue content, and keeps no logs.
Personal data
GuardPulse does not store or process personal data.
Sharing
We do not receive, sell or share any of your data. PuzariCloud has no access to your Jira content.
Uninstalling
When the app is uninstalled, Jira treats its validators as failed, so those transitions are blocked. Remove the GuardPulse rules from your workflows before uninstalling. The settings disappear with the rules; nothing else is left behind.
Contact
Questions: support@puzaricloud.in.